Why most AI pilots stall
and how to choose one that scales.

A COO at a mid-market manufacturer gave MIT researchers the most honest summary of corporate AI I have read. “The hype on LinkedIn says everything has changed, but in our operations, nothing fundamental has shifted. We’re processing some contracts faster, but that’s all that has changed.” The quote sits on page five of The GenAI Divide, the July 2025 report from MIT’s Project NANDA that gave the world its favorite AI statistic: 95% of organizations getting zero return.

That number traveled further than the report did. Fortune ran it as 95% of generative AI pilots failing, and it has been on conference slides ever since. I think the pattern behind it is real. The number itself needs a careful reading, and once you read it carefully, the more useful question is what the surviving pilots had in common.

5%

Organizations whose task-specific gen AI tools reached production with sustained impact, per MIT NANDA, 2025.

42%

Companies abandoning most of their AI initiatives before production, up from 17%, per S&P Global.

46%

Average share of projects scrapped between proof of concept and broad adoption, same survey.

6%

Share of companies getting at least 5% of EBIT from AI, flat for a year, per McKinsey, 2026.

The 95% figure measures less than the headline says

The MIT team drew on three sources: a review of more than 300 publicly disclosed AI initiatives, structured interviews with people from 52 organizations, and a survey of 153 senior leaders collected at four industry conferences, all between January and June 2025. That is a small, self-selected sample, and the authors say so. Their own limitations section warns that organizations willing to talk about AI may differ from those that declined, and that a six-month observation window may understate success for complex systems.

The definition of success matters more. A task-specific tool counted as “successfully implemented” when users or executives remarked that it caused “a marked and sustained productivity and/or P&L impact.” That is a high bar measured by recollection. Next to the key chart, the authors call the figures “directionally accurate based on individual interviews rather than official company reporting.”

The funnel behind the number also tells a different story from the headline. Of the organizations studied, 60% evaluated custom or vendor-sold AI tools, 20% reached a pilot, and 5% reached production. My arithmetic on their numbers: roughly one in four organizations that ran a pilot got it into production with lasting impact. Most of the loss happens before anyone pilots anything. For general-purpose tools such as ChatGPT and Copilot, the report puts pilot-to-implementation at around 83%, though it adds that those tools mostly help individuals and rarely show up in the P&L.

So the honest reading is narrower. In a small 2025 sample, very few companies could point to custom AI that changed their numbers within months. That is still a bad result. It just measures something different from 95% of pilots failing.

Larger surveys land in the same place

The reason I still take the pattern seriously is that bigger samples with different methods agree. In its 2025 Voice of the Enterprise survey of 1,006 IT and line-of-business managers in North America and Europe, S&P Global Market Intelligence found that the share of companies abandoning most of their AI initiatives before production rose from 17% to 42% in one year. On average, respondents scrapped 46% of projects between proof of concept and broad adoption.

Gartner saw it coming. In July 2024 it predicted that at least 30% of gen AI projects would be abandoned after proof of concept by the end of 2025, citing poor data quality, inadequate risk controls, escalating costs or unclear business value. In June 2025 it added that over 40% of agentic AI projects will be canceled by the end of 2027, and estimated that only about 130 of the thousands of vendors selling agentic AI offer the real thing. These are forecasts, so treat them as informed expectation.

The 2026 data has not changed the picture much. In McKinsey’s State of AI 2026, fielded in May and June with 1,719 respondents, 37% say AI has contributed to EBIT at all, essentially unchanged from 2025, even as more companies report scaling. The share of high performers stayed at about 6%. More deployment has not yet turned into more profit for most companies.

Most pilots are picked because they demo well

The first structural reason is how pilots get chosen. A pilot has to win approval, and approval goes to what looks impressive in a meeting. MIT’s respondents put about half of their hypothetical AI budget into sales and marketing, and the authors explain why: outcomes there are easy to measure and map to board-level KPIs. The back office, where they found faster payback from cutting outsourcing and agency spend, gets less money because its gains are harder to show.

One CIO in the report described the result: “We’ve seen dozens of demos this year. Maybe one or two are genuinely useful.” A demo proves the model can do the task once, on clean inputs, in front of an audience. Production asks whether it can do the task ten thousand times inside a process that people already run. A pilot chosen for the first test tells you little about the second.

Nobody in the business owns the result

The second reason is ownership. Many pilots are run by an innovation team, an IT group or a vendor, and handed to the business at the end. The business never asked for it, so the business has no reason to change anything to make it work. MIT found that the strongest deployments were sourced from frontline managers and budget holders, with executive accountability on top. Lack of executive sponsorship was among the top barriers its respondents named.

The buy-versus-build data points the same way once you look closely. MIT reports that pilots built with external partners reached deployment about 67% of the time against about 33% for internal builds, while noting the figures are self-reported and may reflect differences between the companies. In September 2026, Gartner predicted that by 2028, 70% of enterprises will abandon agentic AI built by vendor forward-deployed engineers, “trapped by soaring costs and unable to evolve it on their own.” I read the two together: outside help can speed up the first deployment, and the company still has to own what gets built.

Identify an executive sponsor who is accountable for business outcomes, not simply the implementation budget.

The money stops when the pilot ends

The third reason is budget. Pilots are often paid from an innovation or IT discretionary line with a fixed end date. Running the thing in production needs a different line: licenses at full volume, integration work, monitoring, someone to fix it when the vendor changes a model. If nobody approved that line before the pilot started, a successful pilot arrives at budget season as a new cost with no owner, competing against everything else.

Gartner’s Rita Sallam made the related point in 2024: gen AI costs “aren’t as predictable as other technologies,” and many CFOs have not been comfortable investing today for indirect value later. A pilot that cannot show its full running cost and its payback in the owner’s own budget will usually lose that argument.

The data was good enough for a demo

The fourth reason is data. A pilot runs on a sample someone cleaned by hand. Production runs on whatever sits in the ERP, the CRM and the shared drive. In a July 2024 survey of 1,203 data management leaders, Gartner found that 63% of organizations either lack or are unsure they have the right data management practices for AI. It predicts that through 2026, organizations will abandon 60% of AI projects unsupported by AI-ready data. The gap rarely shows during the pilot, and usually surfaces in the first month of real volume.

The process around the tool stayed the same

The fifth reason is the one I see most often. The company adds AI to a step and leaves the rest of the process untouched: the same approvals, the same handoffs, the same people checking the same things. The time saved disappears into the queue at the next step. MIT’s explanation for failed tools was “brittle workflows, lack of contextual learning, and misalignment with day-to-day operations.”

McKinsey’s 2026 high performers do the opposite. They “fundamentally redesign workflows that are enabled by AI rather than insert AI into existing ones,” and they are twice as likely as others to report that senior leaders show commitment and that the company has defined processes to measure impact. Gartner’s agentic AI release makes the same recommendation: in many cases, rethinking the workflow from the ground up is the better path.

Choose a pilot that has an owner before it has a demo

This is the rule we use. Before a pilot starts, five things must be true. If any one is missing, fix it first or pick a different pilot.

1. A named owner who will run it. One person in the business, with the P&L or the KPI it will move, who agrees in writing to operate it after the pilot. An IT lead or a vendor does not count.

2. A run budget approved up front. The full annual cost at production volume, in the owner’s budget, signed before kickoff. The pilot money and the run money are approved in the same meeting.

3. A baseline measured today. One process metric, such as cycle time, cost per case, error rate or outside spend, measured on current work before anything changes. Without it, nobody can show the result later.

4. Real data, tested early. In week one, run the tool on a hundred real cases pulled from production systems, unedited. If it fails there, you have learned what the pilot would have taught you in month six.

5. The new process written down. One page that says which steps disappear, who reviews what, and what the people freed up will do next. If nobody can write that page, the pilot will save time that nobody captures.

Add a fixed decision date. MIT found that the top mid-market performers took about 90 days from pilot to full implementation, against nine months or longer for large enterprises. I set the date at 90 days: scale it, fix one named problem, or stop. Within those rules, I would favor back-office work with outside spend attached, such as outsourced document processing or agency fees, because the saving is visible in an invoice.

What to do this quarter

Ask for a list of every AI pilot running in the company, with its owner, its cost so far and its intended production date. Put the five questions next to each one. Many companies will find that few pilots have a business owner and fewer still have a run budget.

Then make three calls. Stop the pilots that fail more than two of the questions, and say so openly so the teams can move on. Give the rest 30 days to fill the gaps, with the COO checking. And approve no new pilot until its owner can answer all five in one meeting, with the CFO in the room for the second one.