Working pilot in production
A slice of the real process running on live data in front of real users, early enough that feedback changes the design rather than the release notes.
Phase 03, Build
We ship into production, not into a demo folder, with your engineers pairing alongside ours.
Typical duration
6 to 12 weeks
output: a live system with measured accuracy, latency and unit cost
- 6 to 12 wks
- Pilot to production
- Fortnightly
- Releases measured against targets
- In house
- Your engineers ship the last release
Phase 03
Working software on your data, early and often.
Build runs in fortnightly increments, each one measured against the numbers agreed in diagnosis. You see working software early, running on live data, inside your own environment.
The aim is not only a system that works. It is a system your team can read, change and defend after we step back.
What happens
The work inside this phase.
Three workstreams, run in parallel, each with a fixed deliverable you can review.
Evaluation suite and dashboards
A repeatable test set drawn from your own cases, with scoring that runs on every change, so quality and cost become numbers you track rather than opinions you hold.
Engineer pairing sessions
Structured pairing with your technical team throughout, so the knowledge of how the system is built stays in house instead of in a handover document nobody reads.
The method
The other phases.
Next step
Start with phase 03.
A 30 minute call on build, what it would take in your business, and whether the phase after it is worth funding.