How it works
One clear starting point. A plan to make it work.
We start with the work your business needs to move forward. Together, we decide what is worth automating, what success should look like, and what it will cost. Then we build, prove, and manage it.
Start with the process you want to improve.
First, let's see whether there's a fit.
On the discovery call, we'll walk through a real process: what comes in, who handles it, where it waits, and what a better result would mean for your business.
If there is a worthwhile opportunity, the next step is the paid diagnostic. If there isn't, we'll explain why.
The first 90 days
From understanding the work to keeping it running.
Here is the planned path for a standard engagement. We confirm the schedule around your workflow, access, and review requirements.
The planned first 90 days of a standard engagement
Weeks 1-2
Map the opportunity
The $2,000 diagnostic maps the work, estimates its current cost using your figures, and ranks the opportunities. You receive a written report and our recommended starting point.
Week 3
Agree on the result and price
Your proposal names the workflow, success measure, test conditions, and monthly fee. You know what must happen before automation billing begins.
Weeks 4-7
Build and review
We build the automation. Your team explains the process, provides access, and reviews sample results with us. The build is unbilled.
30 days
Prove it on real work
The automation runs against the success test we agreed in writing. The proving period is unbilled.
When the test is met
Start the managed service
Monthly billing starts the day the automation passes. We keep it running, report on performance, and work through approved improvements.
The proving period can pause when required client access or approvals are unavailable, as set out in the proposal. The $2,000 is credited in full against your first month if we start building within 30 days.
Your team brings the knowledge of the work. We bring the build.
We need someone who knows the process, access to the relevant systems, and feedback on real examples. Your team helps us understand the exceptions and decide where a person should stay involved.
We handle the technical implementation, testing, monitoring, and upkeep. The proposal sets out the reviews and decisions needed from your side.
Visible results
Know what ran, how it performed, and what needs attention.
Standard engagements include a weekly report, or monthly if you prefer. What completed successfully, the quality of the results, and what needs attention. Where an agreed baseline exists, we show estimated staff capacity released and its labor-cost equivalent. Other capabilities show useful activity and outcomes without a fabricated dollar figure.
Every automation also comes with documented accuracy testing and a clear explanation of the exceptions that need human review.
Header: Weekly report ยท Example
| Documents handled | 412 |
|---|---|
| Sent to a person for review | 37 |
| Median turnaround | 18 min |
| Agreed success measure | under 60 min |
| Manual hours displaced Calculated | 46.2 |
The next step is defined before it is needed.
If the automation misses its agreed proving test, we can offer one fix cycle of up to 30 additional days at our cost. You can decline that extension. If the workflow never passes, we remove it and do not bill for it.
The diagnostic fee remains payable because it bought your written report.
Before the automation passes, the standard engagement's SubAI fee is the $2,000 diagnostic. There is no implementation fee.
Bring us the process that keeps slowing things down.
An inquiry, a document, a report, or a recurring handoff is enough to start the conversation.
Start with the process you want to improve.