U.S. businesses spent $35–40 billion on AI initiatives. MIT’s NANDA initiative found approximately 95% of them report zero measurable returns. In the same period, S&P Global tracked the share of enterprises abandoning most of their AI programmes jumping from 17% to 42% in a single year.
That convergence has a name. Analysts at Astrafy and RT Insights call it “AI pilot purgatory” — the gap between a promising demo and an actual production deployment, where projects are neither cancelled nor shipped. This article is the statistical entry point to the enterprise AI pilot purgatory problem — a complete guide to why enterprise AI pilots fail and what organisations that do ship are doing differently.
The statistics are clear on scale. They’re less clear on mechanism. What keeps a pilot that works as a demo from crossing into production? That question gets addressed — but not fully here.
What does “AI pilot purgatory” actually mean?
AI pilot purgatory is where an AI project lives after it’s cleared initial feasibility testing but before it ever reaches full production. Perpetually extended. Perpetually underfunded. Perpetually at risk of cancellation — without ever formally being cancelled.
Astrafy calls it “costly, enterprise-wide gridlock” where “the critical problem isn’t a lack of trying — it’s a failure to convert a working idea into a reliable, enterprise-grade business asset.” RT Insights puts it in terms most technical leaders will recognise immediately: “That pilot everyone loved in the boardroom? It’s still stuck in staging.”
What it looks like in practice: a team maintaining a working demo for the third quarter in a row. A budget line that keeps getting rolled over. A roadmap slot that never gets prioritised because there’s always something more urgent.
Purgatory is defined by what it’s missing — governance structures, production-grade data, budget commitment beyond the current quarter, and a named owner with actual authority over the production outcome, not just the technical build.
In mid-market companies, purgatory often comes down to single-person ownership. When the technical champion’s attention shifts, the project has no institutional home. McKinsey found nearly two-thirds of organisations remain stuck in “pilot mode,” unable to scale across the enterprise. The full picture of why 88 to 95 percent of enterprise AI pilots never reach production becomes clearer when you look at the research behind that range.
What are the six statistics that define the scale of enterprise AI failure?
The 88% and 95% failure figures are not contradictory estimates from competing research. They measure different points in the same lifecycle.
IDC/Lenovo (88%): The AI CIO Playbook 2025 found that for every 33 AI POCs an enterprise starts, only four reach production. IDC Group VP Ashish Nadkarni: “The high number of AI POCs but low conversion to production indicates the low level of organisational readiness in terms of data, processes and IT infrastructure.”
MIT NANDA (95%): The GenAI Divide report found 95% of generative AI pilots fail to deliver measurable ROI despite $35–40 billion in aggregate spending — not just failure to ship, but failure to return value from what does ship.
McKinsey (88% adoption, limited high performers): 88% of organisations report using AI in at least one business function, but only 39% report any EBIT impact, and most attribute less than 5% of EBIT to AI. Nearly two-thirds haven’t begun scaling AI across the enterprise. Adoption is not value.
PwC (56% of CEOs, no financial impact): PwC’s 29th Global CEO Survey found 56% report no significant financial benefit from AI investments. Only 12% report both cost reduction and revenue growth. The failure is visible right at the top.
S&P Global (17% to 42% abandonment): The share of enterprises abandoning most of their AI initiatives jumped from 17% in 2024 to 42% in 2025. Nearly half of all AI POCs are now scrapped before launch. Purgatory doesn’t persist indefinitely.
Gartner (40%+ agentic cancellation predicted): In June 2025, Gartner predicted over 40% of agentic AI projects will be cancelled by end of 2027 due to rising costs, unclear value, or poor risk controls. The pattern is not historical — it is repeating right now.
These six statistics don’t contradict each other. They measure different failure points — feasibility testing, ROI realisation, executive perception, adoption versus performance, abandonment — and together they describe a systemic problem, not a series of individual project setbacks. The complete guide to AI pilot failure examines how these dynamics play out across different organisational scales.
What is the difference between a POC, a pilot, and a production AI deployment?
The definitional confusion here is not a semantic nuisance. It is itself a cause of purgatory. When an organisation can’t tell the difference between “we have a POC” and “we have a production deployment,” it can’t accurately assess what transition work is actually required. That gap lets projects stall while everyone believes progress is happening.
POC (Proof of Concept): A short, low-resource test of whether an AI capability is technically feasible. Uses synthetic or sample data. Answers one question: can we build something that works at all? Duration: days to weeks.
Pilot: A time-boxed test using real users, real data, and real workflows — bounded scope. Success criterion: evidence of value at limited scale with stakeholder buy-in to expand.
Production Deployment: A fully operationalised AI system running at enterprise scale, integrated into core workflows, with active monitoring, governance, and formal accountability chains. Where only four of every 33 POCs ever arrive.
The most dangerous position is what Agility at Scale calls the “false production” trap: a company can truthfully say “we have AI in production” while operating a system at pilot scale with no governance and no plan to expand. Leadership believes the project has shipped. The engineering team knows it hasn’t. That gap is exactly how purgatory persists invisibly — and how IDC/Lenovo’s 88% and MIT NANDA’s 95% can both be simultaneously true.
Why do pilots succeed as demos but stall before they ship?
The demo works. The stakeholders nod. The brief is positive. And then months pass.
Demo conditions are not production conditions. Pilot data is pre-selected and often synthetic. Production data is owned by multiple teams, governed by compliance rules, and full of edge cases the demo never encountered.
But the structural gap alone doesn’t explain why organisations keep approving pilots without committing to production. IDC’s Ashish Nadkarni put it bluntly: “Most of these gen AI initiatives are born at the board level. These POCs are highly underfunded or not funded at all.” The pilot becomes an institutional hedge — it signals action without committing to the cost or accountability of production. No one explicitly kills the project. It just never moves forward.
At the pilot-to-production boundary, three structural blockers keep showing up. None of them are technology problems.
AI-ready data: Production AI requires governed, accessible, high-quality data that pilot environments never actually test against. Gartner found that 85% of all AI projects fail due to poor data quality, and without AI-ready data, 60% will be abandoned.
AI governance: Production requires accountability structures, monitoring, and compliance integration that pilots skip entirely. In production, someone must own the system’s behaviour and its ongoing costs.
Organisational Change Management: Production requires workflow redesign, training, and stakeholder alignment that pilots never touch. BCG‘s 10–20–70 principle is worth knowing here: AI success is 10% algorithms, 20% data and technology, 70% people, processes, and cultural change.
The absence of any one of these is enough to stall production indefinitely. The organisational root causes are examined in the next article in this series.
What is pilot fatigue and when does it become AI abandonment?
Deloitte’s State of AI in the Enterprise 2026 names the accumulated cost of repeated failed pilot cycles: pilot fatigue. The distinction from purgatory matters. Purgatory is a project state — a specific initiative is frozen. Pilot fatigue is an organisational response — the teams and leadership that have lived through repeated purgatory cycles become progressively less capable of running successful future pilots.
The progression is predictable. First pilot stalls — budget renewed, expectations quietly drop. Second pilot stalls — morale declines, champions disengage. Third pilot — executives stop attending reviews. By the time a fourth pilot is proposed, the organisation has lost the institutional knowledge and cultural appetite needed to make a production transition work.
AI abandonment is where severe pilot fatigue ends up. S&P Global’s 17% to 42% abandonment jump is the downstream expression: organisations that spent 12–24 months cycling through unproductive pilots concluded AI investment wasn’t generating returns and redirected resources elsewhere. PwC and S&P Global are describing the same organisations from two different vantage points — 56% of global CEOs reporting no financial impact, and 42% of enterprises abandoning most of their AI initiatives. Cause and effect.
For mid-market leaders, pilot fatigue is personal. In a 100-person company, the CTO who championed the AI programme and has nothing to show faces a credibility risk visible to every person in the organisation. Companies that walk away fall further behind those that don’t. The widening AI value gap is examined in a companion article. The complete enterprise AI pilot purgatory guide maps how pilot fatigue fits within the broader failure landscape.
Why are agentic AI projects failing at even higher rates than traditional AI pilots?
AI pilot purgatory is not a feature of generative AI specifically. It is a structural pattern that repeats with each wave of new AI capability, as organisations invest in the next generation before resolving the readiness problems that stalled the previous one.
Agentic AI — systems that execute multi-step tasks autonomously — is following the same pilot-heavy, production-light trajectory as generative AI. McKinsey found 62% of organisations are at least experimenting with AI agents. Gartner predicts over 40% of those projects will be cancelled by end of 2027.
The three structural blockers are amplified, not reduced. Agentic systems require more robust data governance because they act on data autonomously. More complex integration architecture because a single user query can trigger dozens of internal AI calls. More demanding change management because the workflows they automate are often more central to operations. Deloitte found that close to three-quarters of companies plan to deploy agentic AI within two years, yet only 21% have mature agent governance.
For a full treatment of agentic AI pilot failure and what separates those who succeed from those who cancel, see agentic AI pilot cancellation rates.
What the statistics do not explain — and where to look next
Here is what this article has established: six independent measurements of enterprise AI failure, a definition of AI pilot purgatory and its lifecycle stages, and evidence that purgatory progresses through pilot fatigue to abandonment at accelerating rates.
What the statistics don’t establish is the mechanism. They describe the scale precisely. They don’t explain why a pilot that succeeds as a demo consistently fails to cross into production.
McKinsey’s analysis of AI high performers found the distinction is not technical: high performers redesign workflows, maintain committed leadership, and invest at larger scale. PwC found companies with strong AI foundations are three times more likely to report meaningful financial returns. That’s an organisational readiness finding, not a technology finding.
The organisational root causes of AI pilot purgatory are examined in the next article — starting with the most commonly misdiagnosed one.
One final note on competitive position: organisations stuck in purgatory are not holding steady. BCG found that AI leaders achieve 1.5x higher revenue growth and 1.6x greater shareholder returns than laggards. The widening AI value gap examines that trajectory in full. For the comprehensive overview covering all failure dimensions, statistical evidence, and the CTO decision framework, see the enterprise AI pilot purgatory statistics and analysis guide.
Frequently Asked Questions
Is an 88% AI pilot failure rate the same as a 95% failure rate — which number is right?
Both are correct — they measure different things. IDC/Lenovo count POCs that never transition to production (88% fail to ship). MIT NANDA count pilots that reach some form of production but fail to generate measurable ROI (95% fail to return value). Complementary, not contradictory.
What exactly is AI pilot purgatory?
AI pilot purgatory is the state in which an AI project has passed initial feasibility testing but never achieves full production deployment — neither cancelled nor shipped, perpetually extended, consuming maintenance effort without delivering production value. The term was coined by Astrafy and RT Insights.
What is pilot fatigue?
Pilot fatigue is Deloitte’s term for the organisational exhaustion that results from repeated AI pilot cycles producing no production outcomes. You see it as declining team morale, budget scepticism, and executive disengagement. Purgatory is a project state — the initiative is frozen. Fatigue is an organisational response — the teams and leadership are exhausted from trying.
Why did AI abandonment jump from 17% to 42% in one year?
S&P Global documented a more-than-doubling in enterprise AI abandonment in a single year. Organisations that spent 12–24 months cycling through unproductive pilots concluded AI investment wasn’t generating returns and redirected resources elsewhere. Nearly half of all AI POCs are now scrapped before launch.
Why are only 6% of companies AI high performers despite 88% claiming AI adoption?
McKinsey defines “high performers” as organisations demonstrating AI deployment at scale with measurable financial returns. The 88% adoption figure includes any AI use — isolated tools, unresolved pilots. Nearly two-thirds of McKinsey respondents haven’t begun scaling AI across the enterprise. The gap between adoption and high performance is the pilot-to-production transition problem, measured.
What does “AI-ready data” mean and why does it block production deployment?
AI-ready data is Gartner’s term for data meeting the quality, governance, and accessibility requirements for AI models to function in production. Pilot environments use pre-cleaned, selected data subsets. Production systems must consume real enterprise data governed by compliance rules and owned by multiple teams. Gartner found that 85% of all AI projects fail due to poor data quality, and without AI-ready data, 60% will be abandoned.
What is the GenAI Divide?
The GenAI Divide is MIT NANDA’s framing for the structural gap between the roughly 5% of organisations achieving measurable ROI from generative AI and the 95% that do not. It’s not a gap in technical access or investment — the divide reflects differences in organisational readiness, data infrastructure, and change management capability.
Why does Gartner predict 40%+ of agentic AI projects will be cancelled by 2027?
Agentic AI faces the same pilot-to-production blockers as generative AI, but at greater complexity. Deloitte found that close to three-quarters of companies plan to deploy agentic AI within two years, yet only 21% have mature agent governance. Organisations investing in agentic AI without resolving their generative AI structural failures are reproducing the same pattern at higher stakes.
