Build
Fixed-scope builds with a named outcome
Eight to twelve weeks. A named outcome, a measured baseline, and 30% of our fee tied to a metric we agree before we start.
We build in four functions where mid-market economics are proven, and we rescue the pilots that stalled on the way.
- Eight to twelve weeks
- Scoped to a named outcome
- 70% fixed, 30% on the measured metric
Rescue is half the work
Most Build engagements begin as rescues: a pilot that demoed well and died in integration. Week one is always the same: production data, a golden dataset, and a written baseline. Then we rebuild what was actually broken, which is rarely the model.
Scope
Function pods
- Finance: close automation, reconciliations, document processing
- Customer: service assistants measured against the human baseline
- Sales: proposal and RFP drafting, pipeline hygiene
- Knowledge: retrieval over contracts and policies, with citations
Ways in
- Function pod deployment: eight to twelve weeks, named outcome
- Pilot rescue: a stalled initiative taken to production or killed with evidence
- Data foundation: the pipelines and quality gates everything else needs
- Diagnostic: two weeks, fixed fee, the right start if you haven't spent yet