SKU · Implementation
Twelve weeks. One named system in production.
Evals, human review, audit trail, a named owner, SLOs. The scope is fixed before we start — and we do not run two of these overlapping without a contractor on a signed SOW.
How the twelve weeks run
Gates first. Build second. Handover on day 84.
What exists on day 84.
- One named system in production. Not a pilot, not a sandbox, not a slide.
- Evals running on every release and on a schedule in production.
- Human review where the system is unsure, with every override logged.
- An audit trail — model and prompt versions, decisions, exceptions, retained and exportable.
- A named owner on your side, SLOs, and a cost threshold with someone watching it.
- The 02:00 runbook, written and rehearsed.
Commercials
Stated up front, on purpose.
What this is not.
- Time and materials with a fixed-price sticker.
- Agile discovery that bills while it looks for the scope.
- A body shop delivered in weekly increments.
- An open-ended retainer wearing a build's clothes.
Fixed number. Named system. Twelve weeks.
Twenty-five minutes to see whether your workflow fits the shape. If it does not, we will tell you that on the call.
