
Most AI pilots stall because they were built to prove the model can do the task. Production needs proof that the task works on your live data and inside your systems. It also has to run at a cost and a level of risk the business accepts. A pilot on a cleaned sample, outside the tools people use and with no agreed pass mark, ends in a good demo and no decision. That is the test an AI pilot should be built to pass. A good AI consulting engagement plans for it from the first week.
The scale of the drop is well documented. S&P Global Market Intelligence surveyed more than 1,000 IT and business professionals in North America and Europe in 2025. Of them, 42% said their companies had abandoned most of their AI initiatives, up from 17% a year earlier. The average company scrapped 46% of its proofs of concept before production. Gartner predicted in July 2024 that by the end of 2025, at least 30% of generative AI projects would be abandoned after proof of concept. It cited poor data quality, inadequate risk controls, escalating costs and unclear business value.
The most quoted figure on AI pilots comes from MIT Project NANDA's report The GenAI Divide: State of AI in Business 2025, published in July 2025. Other publishers are often credited with it. It found that 95% of organizations were getting zero return from generative AI. Only 5% of integrated AI pilots were extracting millions in value.
Its narrower findings are more useful to a team planning a pilot. Across the organizations it studied, 60% evaluated custom or vendor-sold enterprise AI tools, 20% reached a pilot and 5% reached production. The report counts a tool as successfully implemented when users or executives describe a marked and sustained effect on productivity or P&L. That effect is measured six months after the pilot. The report draws on 52 interviews, 153 survey responses and a review of more than 300 public AI initiatives. The authors call the findings preliminary, and the figures directionally accurate rather than official company reporting.
The authors trace the stall to three causes: brittle workflows, tools that do not retain feedback or adapt to context, and poor fit with day-to-day operations. The report says model quality and regulation do not seem to drive the divide. Its interviewees put the same point plainly. Each use needed too much manual context, and the tool could not be customized to their workflows.
A pilot is designed to succeed on its own terms. The data is chosen, the scope is narrow and the people testing it know what it is good at. Each of those choices removes a problem production will bring back.
| Gap | In the pilot | In production |
|---|---|---|
| Data | A cleaned or synthetic sample | Live records with gaps, duplicates and slow APIs |
| Workflow | A separate chat window or notebook | Inside the CRM, ERP, ticketing tool or Teams |
| Security | Reviewed after the demo, if at all | Access, logging and residency approved before go-live |
| Success | Stakeholders liked the demo | A pass mark met on your own records |
| Cost | A few hundred test calls | Token and hosting cost at full monthly volume |
| Ownership | The pilot team | A named owner for changes, monitoring and failures |
Pinkcube's chat agent is a small example of the data gap. The order lookup was planned as one API call. Pinkcube's HubSpot holds master deals with sub-deals beneath them. To reach a tracking code, the agent had to work down that hierarchy first, so the lookup shipped as fifteen steps. The team absorbed the extra work without moving the launch date. Every deep-integration project of ours now asks for a CRM schema export during discovery (Pinkcube case study). A pilot on sample data would never have found it.
Check the pilot you are running or planning against the eight conditions below. Each Not yet names where it is likely to stall.
Run the pilot under production conditions from the first week, on one use case. Decide in advance what result would fund the build. Our AI proof of concept follows the sequence below.
Our pilots take 2 to 6 weeks, depending on how many systems the use case touches. You see the length before you sign. If you are comparing firms, our guide to the best AI consulting firms for enterprise lists the production proof to ask each one for. Pricing is fixed and scoped to the integrations and user flows involved. Most pilots fall between $35,000 and $75,000 for one core use case. If you go ahead, the fee is credited toward the production build. The prototype, the code and the IP are yours either way.
A Dutch Odoo implementation partner shows why the pilot should test the hard part. The partner had spent a full year building appointment scheduling natively in Odoo for a dental care group. Treatment series, role matching and urgency limits across 200 practitioners had outgrown the ERP's data model. We prototyped a layer of n8n workflows on top of Odoo, with an AI agent that picks each slot. It now schedules 1,500 appointments a week. Five sync workflows feed it every night, and every appointment it fails to place produces a report saying why.
A pilot that ends without a decision becomes a permanent pilot. The pass mark set in week one makes the decision mechanical. Either the numbers clear it at a cost the business accepts, or they show what has to change. Set the three results below to see how each combination resolves.
Pivot is often the honest answer, and it is a useful one. A pilot close to its pass mark usually has a fixable cause in retrieval, data quality or scope. In many of those cases the model is fine, and the problem is the information it was given. Our post on context engineering covers how to find them. For the cost side, the AI agent cost estimator projects token spend, the usage fees charged by the model provider, at your volume. The guide on how to measure AI ROI covers the baseline to record before launch.
Passing the pilot proves the use case. The production build adds what keeps it working once real users and real volume arrive.
MIT NANDA's report also looked at who built the tools. In its interview sample, tools built with external partners reached deployment about 67% of the time, against about 33% for internal builds. The authors flag the figures as self-reported and possibly skewed by other factors, so treat them as a pattern rather than a rule. Our build vs buy guide covers how to make that choice for your own use case.
Start with the pilot when you already know the use case and can name its owner and its number. Start with the AI Audit when you need to find and rank use cases first. It is a separate engagement of 4 to 8 weeks that ends in a ranked 90-day roadmap. Its fee is credited toward your first build.
An AI proof of concept is a short, scoped build that tests one AI use case on your own data and systems. It comes before you fund a production build. A useful one ends with results measured against a pass mark set at the start, and a recommendation to scale, pivot or stop.
Most stall after the demo rather than during it. MIT Project NANDA's 2025 report pointed to brittle workflows, tools that do not adapt to context, and poor fit with daily operations. Gartner named data quality, risk controls, cost and unclear business value as the reasons projects are abandoned after proof of concept.
Ours take 2 to 6 weeks, depending on how many systems the use case touches. A pilot with no fixed end date and no pass mark tends to run on without reaching a decision.
Most of our pilots cost between $35,000 and $75,000 for one core use case. The fee is fixed and scoped to the integrations and user flows involved. If you go ahead, the fee is credited toward the production build.
A proof of concept tests whether the task can be done at all, often on sample data. A pilot runs it on your real systems with real users and measures it against a pass mark. Production is the supported system at full volume, with monitoring, approvals and an owner.
Before any code, agree a pass mark the pilot either meets or misses, such as an accuracy threshold on your own records. Then measure accuracy, latency under real load, token cost at expected volume and total cost of ownership. Those four numbers show whether the build is worth funding.
If you have a use case and want a decision in weeks rather than quarters, see how our AI proof of concept works. You can also book a discovery call to set the pass mark with us.