Strategy · 7 min read
Why 95% of AI pilots never reach production.
It’s rarely the model. It’s the data, the owner and the missing number. Here’s what the ones that ship do differently.
In 2025, MIT’s NANDA initiative looked at how companies were using generative AI and found that about 95% of enterprise pilots delivered no measurable impact on the P&L.1 Billions spent, demos applauded, and almost nothing changed in how the business actually ran.
We’ve seen the same pattern from the inside. Most of the companies that call us have already run a pilot. It worked in the demo. It never went live.
The number everyone quotes
The headline is easy to misread. It doesn’t say AI doesn’t work. It says pilots don’t turn into production. The same report found that projects built with specialised external partners reached deployment about twice as often as internal builds, and that the biggest returns came from unglamorous back-office work, not from customer-facing chatbots.1
The model is rarely the problem. The plumbing is.
It’s not the model
When we look at why a pilot stalled, the answer is almost never “the AI wasn’t smart enough”. It is one of three things:
- No live data. The pilot ran on an export. Connecting it to the real ERP, inbox or helpdesk was “phase two”, and phase two never came.
- No owner. The innovation team built it. The team whose work it would take never asked for it, and never adopted it.
- No number. Success was “a good demo”. Nobody agreed what had to move, so nobody could say it had worked.
Four things the 5% do
The projects that ship look different from day one. They connect to live systems in week one, not month six. The metric is agreed before a line of code is written, and it belongs to the team whose work changes. People approve the decisions that carry risk, so nobody has to trust the agent blindly. And there is a date: production in weeks, not a roadmap.
| A PILOT | A SYSTEM IN PRODUCTION | |
|---|---|---|
| Data | A sample export | Your live systems |
| Success | A good demo | A number agreed on day one |
| Owner | The innovation team | The team whose work it takes |
| Humans | Watching | Approving what matters |
| Timeline | Open-ended | Weeks |
A checklist before you start
Before you approve the next AI project, ask
- Which live system does it read and write, in week one?
- Which number moves, and who owns it?
- Which decisions stay with a person?
- What happens on day 30?
- Who owns the code, the prompts and the data?
What this means for you
If your last pilot is gathering dust, it probably wasn’t a bad idea. It was missing the boring parts. Start from one process that hurts, connect it to the real systems, agree the number and put a date on it. That’s the whole method. It isn’t magic; it’s engineering.
¹ MIT NANDA, “The GenAI Divide: State of AI in Business 2025”.
Got a pilot gathering dust?
In 30 minutes we’ll tell you what it would take to put it live.
André is the founder and CTO of WizardingCode. Eight years building the software companies run on, now putting agents into production.