4 disciplines · Fixed scopes · No retainers you cannot leave
Scoped, priced, and measured before we write a prompt
Four ways to work with us, from a two week audit to running your agents in production. Each one has a fixed scope, a number attached, and a defined finish line.
The people in the kickoff are the people who build it. No handover to a delivery pod you have never met.
Eval suite
Written before the prompt, run on every change, and handed to you with the workflow. It is how we both know it still works.
Run log and costing
Every run recorded with its duration and cost, in your account, from the first day of the build.
Human gate
A written rule for what an agent may finish alone and what routes to a person, agreed before anything ships.
Your accounts
Prompts, evals, and connectors live in your repositories under your credentials. Leaving takes an afternoon.
Weekly demo
Thursday, thirty minutes, the actual run log on screen. No slides, no status document.
004
/ How an engagement runs
Wk 0 → run
Wk 0–2
Audit
Map the workflows, score hours lost, pick the first three builds.
Wk 2–8
Build
Prompts, evals, and integrations, all shipped behind a human gate.
Wk 8–9
Ship
Cutover with rollback, running side by side with the old process.
Wk 9+
Run
Managed operations: monitoring, cost tuning, a monthly hours ledger.
005
/ Before you ask
The five that come up every time
Do we need an AI strategy first?
No. The audit is the strategy. Two weeks of watching real work beats a quarter of workshops, and you end it holding a costed build plan rather than a slide deck.
What if the agent gets something wrong?
It routes to a person. The handoff rule is written before the prompt, and anything the eval suite has not proven stays behind that gate until it does.
Where does our data go?
Through your accounts, under your credentials, with the run log in your infrastructure. We hold no copy of your customer data.
Can we run this ourselves afterwards?
Yes, and some clients do. The prompts, evals, and connectors are yours. Managed operations exists because most teams would rather not staff it, not because you cannot.
How fast is the first agent live?
Six weeks is our average from the end of the audit, and nine from the first conversation. Simple workflows have gone live in three.