dassi Recurring Task Retainer (5-7 days)
A productized retainer that teaches dassi 3 to 5 recurring web tasks per client in plain English, then runs them on a schedule with approval rules inside the client's existing Chrome, Edge, or Brave accounts. Built for agencies serving e-commerce, recruiting, and back-office teams that repeat the same browser work every week. Time: 5-7 days.
By InnovaAI ResearchPublished Updated
How do you implement it?
dassi Recurring Task Retainer (5-7 days)
A productized retainer that teaches dassi 3 to 5 recurring web tasks per client in plain English, then runs them on a schedule with approval rules inside the client's existing Chrome, Edge, or Brave accounts. Built for agencies serving e-commerce, recruiting, and back-office teams that repeat the same browser work every week.
- Client signs a written approval policy naming which dassi actions auto-run and which pause for human review
- A named client-side owner who can grant access to the browser accounts dassi will operate inside
- Agency installs the dassi extension in Chrome, Edge, or Brave and completes the vendor onboarding flow before the first client call
- Agency picks its delivery tier: Starter at $25/month, Pro at $100/month, or Max at $300/month, and maps that cost to the retainer fee
- Client supplies one month of historical run data or screenshots for the tasks being automated, so the job definitions match reality
- 1.Run a task inventory call and list every recurring browser job the client performs weekly or monthly
- 2.Score each task against dassi's fit: signed-in web app, repeatable steps, clear pass or fail outcome
- 3.Select 3 to 5 tasks for the first build, capping scope so the pilot ships inside the week
- 1.Install the dassi extension in the client's Chrome, Edge, or Brave profile and confirm the accounts it will use are already signed in
- 2.Teach dassi the first job in plain English, walking it through the task once rather than writing a script
- 3.Capture the run history from that first execution and note every step dassi misread
- 1.Refine the plain-English job definition until the first task passes twice in a row without correction
- 2.Build the remaining 2 to 4 task definitions, one at a time, testing each before moving on
- 3.Record which sites and pages each job touches so the client can review the blast radius
- 1.Set the schedule for each job and align it to the client's actual operating rhythm, not a default daily run
- 2.Configure approval rules so flagged actions pause for a human instead of executing unattended
- 3.Decide which actions auto-run and document that decision in the client's approval policy
- 1.Run a full unattended cycle with the client watching, including at least one paused approval
- 2.Log every pause, failure, and manual override from the cycle into a runbook
- 3.Fix the top two failure modes and re-run the affected jobs
- 1.Train the client's named owner on pausing, editing, and re-teaching a dassi job in plain English
- 2.Hand over the runbook and the approval policy as the client's operating documents
- 3.Agree the support boundary: what the agency fixes inside the retainer and what bills as extra work
- 1.Publish the first monthly run report from dassi's run history, showing hours saved per task
- 2.Set the next month's refinement list based on tasks that failed or needed manual rescue
- 3.Invoice the retainer and schedule the 30-day review call
dassi Starter costs $25/month and Pro costs $100/month, so a single client retainer at $1,800 setup plus a monthly fee covers the tool cost many times over. The margin comes from setup labor, not the license: 16 hours of build at an agency rate of $100-$150 per hour produces $1,600-$2,400 of billable work against a tool bill under $300. Refinement after launch is the recurring revenue line, since each new task the client adds is a small scoped build rather than a new platform deployment.
- A written approval policy naming which dassi actions auto-run and which pause for review
- 3 to 5 plain-English dassi job definitions, each tested twice before handover
- A runbook covering how to pause, edit, and re-teach a job, plus the top failure modes seen in testing
- A monthly run report built from dassi's run history, showing hours saved per task
- A refinement backlog listing tasks that failed or needed manual rescue, priced for the next cycle
The client's 3 to 5 dassi jobs each complete a scheduled cycle with no manual rescue, and the client's named owner can pause and re-teach a job without agency help.
More on dassi
- StrategyWhy dassi Turns Browser Sessions Into Agency Retainers
- Evaluation Ruledassi Rule: Adopt Only When the Client Has 3-5 Repeatable Browser Tasks and a Machine That Stays Awake
- Decision Frameworkdassi: Buy vs Skip (Browser Agent Retainers at $25 to $300 per Month)
- Failure PatternThe dassi Browser-Session Trap: Why Agencies Fail When Client Workflows Depend on an Open Tab
- Operating Proceduredassi Client Workspace Setup (Onboarding)