The 12 steps
What we do at each step, and the receipt you get for it. A step is only marked done when its receipt exists and you can open it.
Understand
No building until we agree what ‘better’ means and how your work really runs.
- 1
Outcome before output
Write the result you want — who, what changes, by how much — without naming any technology.
ReceiptA one-page outcome frame you approve.
- 2
Your real workflow
Map how the job is actually done, grading every step as seen, documented, or only reported.
ReceiptA workflow map with the friction and the exceptions marked.
- 3
Assumptions and risk
List what must be true, score each by impact and uncertainty, and test the riskiest first.
ReceiptA ranked risk list and the first test to run.
Prove
The smallest thing that proves value, written down so nobody has to remember it.
- 4
Smallest testable slice
Pick the thinnest end-to-end piece that can prove or disprove the outcome, with a stop rule.
ReceiptA slice plan and the exact proof it must produce.
- 5
Executable spec
Turn rules into checks: normal, edge, failure and forbidden cases, and what stays a human decision.
ReceiptA spec where every rule has a test.
- 6
Answers with sources
When AI answers from your documents, it must cite them — or say it cannot.
ReceiptAnswers you can trace back to your own papers.
- 7
Measured quality
Score the system on enough real cases to trust the number, with its margin of error.
ReceiptA quality report, not an impression.
Ship
Live only through gates that fail closed, with a way back in under a minute.
- 8
Production gate
Check security, reliability, cost and monitoring. Anything unknown counts as a fail.
ReceiptA gate report with every item answered.
- 9
Success metrics
Freeze the pass, fail and ‘not sure yet’ lines before any result comes in.
ReceiptA frozen metric plan nobody can move later.
- 10
The right stage
Decide by evidence whether this is a prototype, a pilot or production — and show it in the system.
ReceiptNo pilot quietly turning into production.
- 11
Careful rollout
Run in the shadow first, then on a small share, with rollback as a single switch.
ReceiptRollback in under 60 seconds, rehearsed.
Improve
It keeps getting better because every signal becomes a fix.
- 12
Feedback ratchet
Every complaint, error or idea becomes an owned fix at the earliest layer that prevents it.
ReceiptA running list of fixes, each with an owner and a check.
Start with one job
Tell us one piece of work your team repeats every week. We will reply with a scoped plan for Discovery — what we would look at, what you would receive, and the fee.