Skip to main content
How Can We Help?Contact

Why did the pilot work but production did not?

Pilots stall on everything around the model.

An AI pilot runs on clean samples, friendly users and a small bill. Production meets real data, a risk committee and real volume. We help you decide whether yours deserves to scale, then build what the demo skipped.

Review your pilot before you fund more How the readiness review works

Asked by CIOs, and by the business owners who funded the pilot.

What the pilot proved, and what the business still needs to know. Illustrative.

DemoProvedThe model does the task on sample data

Four conditions still open before it scales

DataSample onlyReal records, real users, real permissions

EvaluationNot measuredProof it is good enough

ControlsNot designedWhat happens when it is wrong

OperationsNot costedRunning cost and ownership at scale

Decidescale, revise or stop

Demo ready. System not.

Four decisions before it scales.

A pilot answers one question: can the model do it? Production answers four more. They are not taken in turn: a review left to the end is one of the commonest reasons pilots stall. Any one of the four can hold the launch.

  1. Data

    Will it work in our real business?

    The three questions behind it
    Real records
    The gaps, duplicates, personal data and version drift the sample did not have.
    Real users
    The people who will use it, in the process they actually follow, with the permissions they actually have.
    Change
    What happens when the data, the documents or the process change next month.

    Ready when it has run on real records, with real users.

  2. Evaluation

    How will we know it is good enough?

    The three questions behind it
    Labeled answers
    A test set from your own work, scored before anyone says it works.
    The bar
    Agreed in advance by the business owner, and stricter where a mistake costs more.
    Every change retested
    A new prompt, model or data source is tested again before it ships.

    Ready when it clears the bar the business owner agreed.

  3. Controls

    What happens when it gets something wrong?

    The three questions behind it
    Security tests
    Prompt injection, data leakage and jailbreaks, tested before launch.
    Hand-off
    Clear rules for when it passes a case to a person, with the context, and an owner for that queue.
    Sign-off
    The review its risk calls for, signed before it goes live.

    Ready when the risk owner signs against the tests.

  4. Operations

    Will the economics and operations hold at scale?

    The three questions behind it
    Unit cost
    Cost per transaction at real volume, routed to cheaper models where they meet the bar.
    Monitoring
    Quality drift and alerts that someone actually watches.
    Ownership
    A named team that runs it after launch, and a record your legal team will read.

    Ready when cost and quality hold at real volume.

The decision is not whether the pilot works. It is whether it deserves to scale.

Scale
The value is credible, the risks are manageable and the running costs work.
Revise
The opportunity is still attractive, but critical assumptions have to be corrected first.
Stop
The expected value does not justify the investment, the cost or the exposure.

A pilot can work and still not be worth scaling: the benefit is too small, adoption too hard, the running cost too high, or a simpler route gets there for less. Why scale this pilot at all? Start with question 1, Value & Economics

Not sure which of the three yours is? Leaving it undecided costs too: the pilot keeps spending while the people who built it move on. We review one pilot against these four decisions and give you the answer, with the evidence.

Get a scale, revise or stop view

What each decision looks like, answered.

From delivered work, one decision at a time. Each figure is an operating result: a change in the work, as the client reported it.

Data

Will it work in our real business?

A global manufacturer built its first forecasting use case on the real systems, not a cleaned sample, so there was no gap to close later.

+20%

Forecast accuracy, from CRM, ERP and third-party market data of uneven quality, integrated and cleansed rather than sampled. Forecasts refresh as new data arrives, in the dashboards the planners work from.

Operating result Read the case study

Evaluation

How will we know it is good enough?

One wrong answer in a demo is hundreds a day in production. An error rate that looks fine on fifty questions turns into a queue at real volume, and what each error costs depends on what it touches: a clumsy sentence is cheap, a wrong payment or a wrong instruction is not. Change the numbers and see.

Estimated wrong answers reaching people, per day

750

In the demo, at 50 requests a day
1 or 2
Reaching people in 30 days, at the same volume
22,500
Caught and sent to a person, per day
0

About 750 wrong answers a day reach people. In the demo it was 1 or 2, which is why it looked fine.

The numbers

Illustrative arithmetic: volume times error rate, minus what is caught.

Wrong answers reaching people a day750

25,000

From a demo-sized 50 up to 100,000.

3%

The share of answers a careful reviewer would mark wrong.

0%

What checks and tests catch before an answer goes out. The demo caught none.

Estimates, not forecasts: one answer per request and the same volume every day. Real error rates come from testing against labeled answers from your own work. Nothing you set here leaves this page.

15–25%

Of documents routed to a reviewer by rule, the nonstandard ones, for a global financial information provider: a bar that decides what the system handles and what a person sees.

Operating result Read the case study

Controls

What happens when it gets something wrong?

A hand-off that works: when the assistant cannot solve it, a person takes over with everything it already knows, so nobody is asked twice.

37%

Fewer Tier 1 live-agent contacts on the issue types covered, with 28% higher first-contact resolution, for an electronics manufacturer. Cases it cannot solve go to an agent with the full context.

Operating result Read the case study

Operations

Will the economics and operations hold at scale?

A cost per order that falls at full volume, running inside the systems the business already uses.

12%

Fewer delivery miles per fulfilled order, and 18% fewer stockout incidents at key partners, for a food manufacturer and distributor. Built as a layer on the planning system it already ran, not a replacement.

Operating result Read the case study

Where most stalled pilots start

A readiness review of the pilot you have.

A stalled pilot rarely needs another pilot. In two weeks we score the one you have against your systems as it runs, and tell you whether to scale it, revise it or stop. It works the same way for a pilot that disappointed: you learn whether the model, the data or the setup let it down, and whether it deserves another round.

Delivered as the AI & Data Assessment Sprint, pointed at your pilot. Fixed scope, fixed fee agreed in writing first.

What you get

  • The pilot scored against your systems as it runs, not as it was demonstrated
  • What blocks production, ranked by what blocks first
  • What it would cost to run at your volumes, year one and run-rate separated
  • A recommendation to scale, revise or stop, with what to keep and what to rebuild

Other ways in

  • The use case is not proven yet.AI & Agent PilotOne use case on your data in two to four weeks. It proves the case; it is not the production launch.
  • The case is made and it needs building.Production buildFrom the Generative AI & AI Agents practice, handed to a team that can run it.
  • The data underneath is not ready.Data Platform AcceleratorA working data foundation, the first pipelines live, a runbook your team owns.
  • It is live, and models keep changing under it.Ask about AI Change AssuranceYour exposure across model changes, with a replay proof on one live workflow.

The practices behind this page: Generative AI & AI Agents, AI & Machine Learning, Data Engineering & Platforms and AI Security & Cyber Risk.

Questions CIOs ask first.

Why do AI pilots stall before production?

Usually on what surrounds the model. The data was clean in the pilot, nobody could prove it was good enough, the review arrived at the end, and the unit cost was never modeled. Sometimes the model itself is the limit, and an honest evaluation shows that early. None of it is visible in a demo.

Do we need another pilot?

Usually not. If the pilot proved the use case, the next step is a review of what production needs, then the build. A new pilot makes sense when the use case itself is still unproven.

Should we rebuild the pilot or extend it?

Usually keep what proved the use case and rebuild what assumed a demo: the data connections, the tests, the controls and the cost model. We say which is which at the start, before anything is built.

How do you decide it is good enough?

Against labeled answers from your own work, with a bar the business owner agrees before launch, stricter where a mistake costs more, and tested again on every change. “It seems to work” does not clear a risk committee.

Which models do you use?

Whichever clears your bar for quality and security at the lowest unit cost, and we route between models where it pays. We are model-neutral by policy and hold no exclusive vendor incentives.

What if production shows it is not worth it?

Then you hear it with the evidence: scale it, revise it or stop. A pilot stopped on evidence is money saved, not money lost.

Bring us the pilot that worked. We’ll show what production needs.

Thirty minutes with the person who would lead the work: a senior AI and data strategist who has taken programs from strategy to systems running in production, in more than one industry. If it should stop at the pilot, you will hear that first.

Book 30 minutes on your pilot

Pilot stuck? Thirty minutes on what production needs, with the person who would lead the work.