Flat fees, fixed quotes, and AI costs billed at cost.
No hourly meters. No surprise invoices. You will know every number before we start, and the metered AI usage runs in your own account, never marked up.
Most agencies in this market will not publish a number. We do, because a price you can compare is a price we have to defend.
Thirty minutes against six months of wondering whether any of this applies to you.
A ranked list against guessing which thing to automate first — and it is credited, so a build costs you nothing extra for having checked.
One to three hours a week, back, every week. At the loaded cost of an admin hour that is roughly $1,700 a year per hour returned — and the build is bought once.
Six thousand against committing twenty on a guess. The one rung whose job is to tell you the cheaper answer if there is one.
The lower bound of a Desk. The Blueprint exists to make that number right before you spend it.
A receptionist costs $53,265 a year loaded, and the invoice arrives again every year. A Desk is bought once.
BLS median wage plus the measured benefits load, x5, flat — no raise, the most conservative version of the number.
The only rung that builds a new revenue line instead of protecting an existing one. You own the repository, the infrastructure and the revenue.
A licence you never stop paying — no licence, no revenue share.
No licence, no revenue share, no platform of ours underneath it. If we stopped working tomorrow it keeps selling.
The run that never happens writes no error. This is the line item that notices — and it is the failure we got caught by ourselves.
Billed in your own account at what the provider charges. Every agency that marks this up is taking a margin on your electricity bill.
Most retainers die in month four.
The launch work finishes, the backlog empties, and the agency starts finding work to justify the invoice. That happens because the retainer was priced in hours, and hours are not something you can recognise on a statement.
So ours is not hours. It is three things you can point at, priced separately, reported monthly.
It stays running
The unglamorous work that stops a working system from quietly rotting.
- Failure and absence alerting
- Dependency and security patching
- Log review and uptime monitoring
- Backup verification
- Credential and token rotation
It gets better
A fixed number of build days each month, spent on what you decide is worth doing next.
- You set the priority, we estimate
- Named owner on both sides
- Scheduled in advance, not squeezed in
- One month of carry-over, no more
Someone answers
Published response targets, so escalation is a contract rather than a favour.
- Named escalation path
- Severity targets published below
- Business hours or extended
- Incident write-up after every Sev 1
Every one of these exists so you are never trapped.
Cancel with 30 days, any reason
No annual lock-in and no exit interview. If the system no longer needs us, that is the automation working.
Pause for up to 60 days a year
At 25% of the retainer, monitoring stays on. For slow seasons, so a quiet quarter does not force you to cancel and rebuild.
You own everything
Built in your accounts, your platform, your keys. We hold least-privilege access. Leave whenever you like and nothing breaks.
A handover pack, kept current
Runbooks, architecture notes, and credentials documented and refreshed quarterly. Not written on the way out the door.
One page, every month
Same format each time: what was patched, what shipped, what broke, what it cost, and one recommendation for next month.
We will tell you to stop
If build capacity goes unused three months running, we will propose downsizing you to monitoring and on-call only.