Offering · Pilot to production
The demo worked. Now make it something you can release.
For a pilot stuck between demonstration and release. We find what is missing, agree the evidence a release needs, and prove a working slice on your data and controls.
Call when
- The demo works, but weeks later there is still no path to production, or nobody uses it.
- No one can say who answers for the result if it goes wrong.
- Risk, security, a customer or an investor has asked for evidence you cannot yet produce.
- Two teams get different numbers from the same AI.
You get
- A gap and dependency register for the workflow.
- A target architecture that separates meaning, sources, calculations and authority to act.
- A release-evidence plan: permissions, evaluation, operating ownership and rollback.
- A working slice tested by real users, with the evidence for a go or no-go.
How it runs
- Length
- 2 to 3 weeks to review readiness, then 4 to 6 weeks to prove.
- You bring
- The workflow sponsor, technical lead and control owners, the current architecture and the review obligations you know of.
- It ends with your decision
- Agree the release gate and build, fix a named gap first, or stop.
- Fee
- Fixed fee per phase, stated in a written proposal before you commit.
Why pilots stall
In our experience, the model is rarely the only problem.
A stalled pilot is usually also stuck on ownership, data, access or evidence: questions a demonstration never has to answer. So the review tests model quality, sources, workflow, controls and ownership separately, and names which one is blocking release.
A pilot proves the model can answer. Production needs evidence it meets agreed quality, control, usability and cost criteria, and an accountable owner.
Where the effort goes
Most teams queue in the wrong lane.
Read next:
Next step
Bring the pilot that should already be in production.
A free sixty-minute session with Richard to examine one workflow, what is blocking it and whether there is a useful next step.