Six stages. Four to six weeks. One fixed fee.
Every commission runs through the same six stages, in sequence. You see where we are at every one, and you can stop at the end of any stage.
No engagement starts without the diagnosis. No engagement begins without a working prototype. And no engagement ends without a clean handoff. Those three rules determine everything else about how we work.
The full cycle is four to six weeks for most commissions. It is sequential, not parallel, we don't run multiple builds at once, and nothing is farmed out. Below, the stages in detail.
We meet, usually on video. You describe the operation. We locate the two line items and sketch the fix on the spot. You leave with a written memo, whether or not we proceed. No deck. No follow-up calls for upsell.Stage ⅠOf six
We build a working version of the proposed system using a slice of your real data. You operate it. If it doesn't hold, we haven't earned the engagement. Most do.Stage ⅡOf six
If the demo holds, we write a commission: scope, deliverables, handoff criteria, and one fixed fee. No hourly. No retainers. You sign it or you don't.Stage ⅢOf six
We ship end-to-end. Weekly review meetings, a live build-log you can read any time, and a soft internal launch at the midpoint. You watch the system come online as it happens, not at the end.Stage ⅣOf six
We train your team, transfer every asset, and document every moving part. You own the system the day it ships. No runtime we control. No licensing.Stage ⅤOf six
Optional quarterly retainer for tuning, monitoring, and new feature work. Fixed, transparent, and cancellable with 30 days' notice. Most clients keep us for a year and then don't need us.Stage ⅥOf six
Everything that ships with the system.
Every deliverable is transferred to you at handoff. There's no "premium" version, no seat upsell, no asset we keep.
Full source code
Repo transferred to your GitHub org. Clean, documented, reviewed. Readable by any competent engineer.
Prompt & model library
Every prompt, every tuning, every eval set, versioned and documented. You can retune without us.
Architecture document
A 15-30 page written explanation of every moving part. Written for your CTO and a future engineer.
Training sessions
Two live sessions with your team. Recorded. The second one is always after they've used it for two weeks.
Runbook & alerts
What to do when something breaks, wired into your Slack or PagerDuty. No guesswork for your ops lead.
The house guarantee
Any shortfall against the commission, we fix it on our time. In writing, signed with the scope.
Book the 45-minute diagnosis.
No pitch. No fee. A written map of the two line items bleeding your business, yours to keep whether or not we work together.