Start here
One workflow. Four to six weeks. Fixed fee.
$6,000
credited in full against month one of any retainer started within 30 days
A monthly retainer is an open-ended commitment to a firm you met three weeks ago. This isn't. It's one bounded outcome with a number attached, and if we miss it we keep working.
Before you talk to us
Run the arithmetic yourself. If it comes out small, do not call us.
Every number here is yours, not ours. We are not asking you to believe a statistic — we are asking you to spend four minutes on a calculation we have no way to influence.
____ people × ____ hours a day × 250 days × $____ an hour
= $________ a year
Three people, two hours a day, at $35 fully loaded: 1,500 hours and more than $52,000 a year — for work nobody was actually hired to do.
Use loaded cost, not salary. The number you want is what the hour actually costs you.
- Orders or requests retyped out of email and PDFs
- 3–6
- Recurring reports built from exports, then cleaned by hand
- 4–8
- The same information keyed into two systems, or reconciled between them
- 3–6
- Chasing people for confirmations, status or lead times
- 2–5
- Approvals and handoffs sitting in somebody’s inbox
- 1–3
- Hunting folders and old email for specs, certificates or past orders
- 2–4
- A report only one person knows how to build
- 2–4
Hours a week, per task, from what we typically see when we sit down with a team. Most recognise four or five of the seven — which is the whole problem. The cost is never in one place, so nobody has ever had a reason to fix it.
The guarantee
Before we start, we agree in writing the number the build has to hit. If it does not hit it, we keep working at no additional cost until it does.
The KPI, the baseline it is measured against, and the method of measurement are all written into the SOW before any work starts. The guarantee is against that agreed number, not against a general impression of whether it went well.
What happens
Four to six weeks, start to production
Week 0
Pick the workflow
A 45-minute call. We look at what your team repeats, and pick the one process where being wrong is cheap and the time saved is obvious. We write down the number we are aiming at and how it will be measured.
Weeks 1-2
Build
We build inside your Microsoft tenant, on the documents and mailboxes you already have. No new licences, no vendor approvals, nothing for your IT person to host.
Weeks 3-4
Run it alongside
The system runs in parallel with however you do it today. You compare outputs. Nothing is switched over until you are satisfied it is right.
Weeks 4-6
Hand over, or keep going
It goes into production and you own it. If you want us to keep building, the fee is credited against month one. If not, it is yours and we are done.
The record
Every one of these was bigger than a proof build.
If we do not believe the build will pay for itself, we will tell you before you spend anything.
These are first production deployments on work we delivered — and not one of them was a single-workflow proof build. Each was a larger first engagement, and they still landed between six and twelve weeks. A proof build is deliberately smaller than any of them. If yours turns out not to be, we will say so before you sign rather than in month three.
- Invoice automation
- MVP in 6 weeks
- Digital load confirmations and e-signatures
- MVP in 6 weeks
- Census reconciliation and variance detection
- 8 weeks to production
- Claims data integration and quality platform
- 12 weeks to first deployment
Every one then continued with ongoing enhancements. That continuation is the retainer, which is the whole point of starting small.
Choosing the workflow
Start where being wrong is cheap
We never make finance the first build. It is the most common way these projects fail, and the sequencing is deliberate — buyers themselves report trusting AI far more for reading documents than for calculating numbers. We build in that order.
01
Start where being wrong is cheap
Document reading, internal reporting, draft generation. High volume, forgiving of error, immediate to verify.
02
Then the operational workflows
Reconciliation, alerting, approvals — the processes with a human still in the loop.
03
Finance-grade last, and only once trust exists
Payment, pricing, coverage, anything a regulator or a client sees. The accuracy bar is far higher and a wrong number early destroys everything after it.
Good and bad candidates
- Reading documents and pulling out the data
- Reconciling files that arrive from several outside parties
- Assembling a report someone rebuilds by hand every month
- Drafting something a person will review before it goes out
- Anything that calculates a number a client or regulator sees
- Payment, pricing, or coverage decisions
- Anything that writes to a machine on a production line
The bottom three are not permanently off the table. They are simply the wrong place to start, because a wrong number in the first engagement costs more than it saves.
What you get, and what you own
- One process, chosen together, that pays for itself on its own
- Working software in production — not a report or a roadmap
- The measured before and after, in writing
- Built in your Microsoft tenant. You own the code.
Or skip it and start on a retainer.
If you already know you want an ongoing team rather than one build, the plans start at $2,500/month, month to month, 30 days’ notice.