Take a promising pilot live
For a prototype or pilot that works in a demo but isn't reliable or part of day-to-day work yet. It can come out of a Sprint or be one you already have. No Sprint needed first.
Discuss a pilotWhat going live involves
Exit criteria, agreed first
A pilot goes live only when it meets exit criteria agreed before it starts. If it came from a Sprint, the Sprint's exit criteria become its acceptance criteria. If it doesn't meet them, it stops.
An evaluation set it must pass
Examples of the work with the right answers, run again after every change.
Fitted to your systems and policies
The tools, where they run and who can access what are agreed with you before implementation, and built to what your security and privacy reviewers approve.
People stay in the loop
Review steps, refusal paths and hand-offs ship in the first version. A named person owns every decision the system supports.
Monitoring and cost limits
Production includes monitoring, a runbook, cost limits and a switch-off.
An owner on your side
When it's live, a named owner on your side runs it in day-to-day work. We plan the handover with them and agree any ongoing support in the scope.
How it differs from a Sprint
A Sprint finds and tests one opportunity and ends in a decision. Its prototype is deliberately not production code. Pilot to Production builds what goes live, with the evaluation, review and monitoring that needs.
How the Sprint worksYour information and the terms
We treat your information, and how it moves through the workflow, as part of the design. Each phase is scoped and priced in writing; the specific terms, including how your information is handled, are set out in the MSA and SOW for the engagement.
How we approach systems and dataHave a pilot that isn't part of day-to-day work yet?
A 30-minute conversation. No preparation required.