The 5.5% Problem: Why AI Spend Doesn’t Show Up in Profits
The 5.5% Problem: Why Enterprise AI Spend Doesn’t Show Up in Operating Profits — and What Actually Changes That
Eighty-eight percent of organizations are using AI. Five and a half percent are making money from it. The gap between those two numbers is the most important story in enterprise technology right now.
Here is the number that should be hanging on every CFO’s whiteboard: 5.5. That is the percentage of organizations — out of nearly two thousand surveyed across a hundred countries — that can credibly claim AI is moving their EBIT by more than five points and delivering significant value. Not “we ran a successful pilot.” Not “our employees love the tool.” Actual operating profit, attributable to AI, above a threshold that any finance team would call meaningful. Five point five percent.
The uncomfortable corollary is that the other 94.5% are largely spending without earning. They are buying licenses, running proofs of concept, presenting dashboards to their boards, and watching the line item grow in the IT budget — while the P&L stays stubbornly unchanged. This is not a technology failure. The models work. The capabilities are real. Something else is broken, and that something else is almost entirely organizational.
This article is about what separates the 5.5% from everyone else, why the gap exists, and — most importantly — what a business executive can actually do about it before the window for competitive differentiation closes.
Why Function-Level Wins Don’t Compound Into Enterprise Profit
Start with the data that makes this paradox confusing from the inside. If you zoom into individual departments, AI looks like it’s working. Organizations report 10–20% cost reductions in software engineering, manufacturing, and IT. Marketing and sales teams see revenue uplifts above ten percent in a meaningful share of cases. Sixty-four percent of respondents say AI has improved their capacity to innovate. These are not trivial numbers — a ten percent cost reduction in software engineering is significant by any measure.
The problem is that these wins are staying where they started. They are local. A productivity gain in the customer support center doesn’t automatically restructure how the operations team hands off escalations. An AI tool that compresses code review cycles doesn’t, on its own, change how product roadmaps get prioritized. Each function collects its win, files its case study, and moves on — while the enterprise P&L absorbs the tool costs and sees very little of the benefit.
The technical term for this is aggregation failure. The economic term is fragmentation. The business term is: we have a lot of local wins and very little systemic reinforcement. Scattered function-level gains are not the same as a compounding enterprise advantage, and the path between them is not automatic. It requires deliberate design.
This is the distinction the 5.5% have figured out. They are not running better AI pilots than the other 94.5%. They are running a fundamentally different game.
What the 5.5% Actually Do Differently
The separating variable is not technology. It is not budget. It is not even talent, though talent matters. The separating variable is organizational intent expressed as workflow redesign.
High performers are 3.6 times more likely to be pursuing transformational, enterprise-level change rather than incremental improvements. They are not asking “how do we make this process ten percent faster?” They are asking “given that AI can now do X, should this process exist in its current form at all?” That is a categorically different question, and it produces categorically different outcomes.
The workflow redesign data makes this concrete: 55% of high-performing organizations say they fundamentally reworked their processes when deploying AI — nearly three times the rate of everyone else. This is the real cut line between what we might call plug-in thinking and rewiring thinking. Plug-in thinking adds a tool to an existing process and hopes efficiency accrues. Rewiring thinking uses AI as the forcing function to redesign the process itself. The former produces cost savings that get absorbed into the budget. The latter produces structural advantages that show up in operating margins.
PwC’s research adds another dimension: the leaders aren’t just pointing AI at cost reduction. They are pointing it at growth. New revenue streams. Business model expansion. Industry boundary-crossing. Cost reduction through AI is table stakes at this point — the companies pulling away from the pack are the ones treating AI as a reinvention engine, not an optimization tool.
The budget commitment follows the intent. Companies in the top performance cohort are investing upward of 20% of their total digital budget in AI. That is not a marginal line item — it is a structural reallocation. And leadership behavior matches: nearly half of executives at high-performing firms strongly agree that senior leaders show clear ownership and long-term commitment to AI, role-modeling usage, protecting budgets, and repeatedly sponsoring initiatives. Compare that to roughly 16% at other firms. Execution follows from the top, or it doesn’t compound.
The Productivity Paradox, and Why It’s Temporary
The cynical read here is that this is all just a longer way of saying “change management is hard.” Fine. The cynical read is also missing something important, because the mechanism at work is historically specific.
We have been here before. When computers entered the enterprise in the 1970s and 1980s, economists noticed that productivity statistics didn’t move despite massive technology investment. The “productivity paradox” of that era took decades to resolve — not because computers didn’t work, but because the organizational restructuring required to capture their value took time to propagate through the economy. The gains eventually showed up, dramatically. The lag between installation and harvest is a feature of general-purpose technologies, not a bug.
AI is following the same curve. Enterprise surveys consistently find the same pattern: broad adoption, narrow profit impact. The majority of organizations are still in what Stanford economist Erik Brynjolfsson calls the “installation phase” — they have purchased the licenses, stood up the pilots, assigned the innovation leads. They have not yet restructured workflows, retrained employees, or redesigned the underlying processes. That restructuring is what produces the returns.
Goldman Sachs identified where transformation is already happening at scale — and the geography is narrow. Two functions: software development and customer service. In both, organizations that actually measured AI’s impact reported median productivity gains in the range of 30%. That is extraordinary. It is also a signal about what conditions make AI returns measurable: high-volume, well-defined tasks with clear output metrics and workflows that were redesigned — not just augmented — around the new capability.
The Agentic Gap Is the Next Fault Line
Here is where the story gets more urgent for business leaders specifically. The current 5.5% is operating in a world of primarily generative AI — tools that answer questions, draft content, summarize documents, assist developers. The next wave is agentic AI: systems that plan and execute multi-step workflows autonomously, not just respond to prompts.
The gap here is already visible in the data. While the majority of organizations say they are “using generative AI,” fewer than 10% report scaling AI agents in any function. In product development specifically, nearly three-quarters of respondents are not using AI agents at all.
This matters because agentic workflows are where the organizational redesign imperative becomes unavoidable. You cannot bolt an agent onto a broken process — the agent will faithfully execute the broken process, faster. To capture the value of agentic AI, you have to redesign the workflow first. Which means the companies that are already doing workflow redesign for generative AI are building the muscle memory and organizational infrastructure that will let them move quickly on agents. The companies that skipped that step are not just behind — they are falling further behind, because the next capability wave requires the organizational foundation they haven’t built.
The widening that PwC describes — 74% of AI’s economic value captured by 20% of organizations — is not a stable equilibrium. It is an accelerating divergence. The gap between plug-in companies and rewiring companies compounds over time, because the rewirers are building capabilities and infrastructure that make the next round of gains faster and larger, while the plug-in companies keep spending on tools without changing the underlying system.
Where Mid-Market Companies Are Positioned — and the Specific Advantage They Have
For business executives, there is a version of this story that is threatening and a version that is clarifying. The threatening version: mid-market companies have less capital than large enterprises, smaller AI teams, and fewer resources to absorb the organizational disruption that rewiring requires. The McKinsey data does show that companies with over $5 billion in revenue are significantly more likely to have crossed the scaling threshold than smaller firms.
The clarifying version: mid-market companies have structural advantages that large enterprises cannot replicate. Faster decision cycles. Less organizational inertia. Leadership teams that can actually mandate workflow redesign without a two-year change management program. The ability to treat AI as an enterprise-wide initiative rather than a federated collection of departmental projects.
The 5.5% is not exclusively populated by large enterprises. The conditions for membership are behavioral, not dimensional. What the data actually describes is a set of choices: to invest at a level that reflects genuine strategic commitment, to redesign workflows rather than augment them, to target growth alongside cost reduction, and to have senior leadership that owns AI outcomes rather than delegating them to an innovation lab.
Those choices are available to a $200 million manufacturer in the same way they are available to a $5 billion financial services firm. The constraint is not size — it is organizational will.
What Leaders Should Do Before the Window Narrows
The McKinsey, PwC, and Goldman data converge on a single diagnosis: the AI productivity problem is not a technology problem. The technology is delivering in the places where organizations have given it the right conditions. The problem is that most organizations are still structured to run pilots, not to run AI as infrastructure.
Three decisions separate the companies that will join the 5.5% from the ones that will keep spending without earning. First, pick two or three workflows to actually redesign — not augment, redesign — in the next twelve months. Customer service and software development are where the 30% productivity gains are showing up. Start there if you’re early. Move to wherever your highest-volume, clearest-output processes are if you’re not. Second, make the budget commitment that signals real intent. If AI spend is less than a rounding error in your digital budget, you will get rounding-error returns. Third, have leadership own specific outcomes, not vague mandates. “Use AI more” is not a strategy. “Reduce cycle time in this workflow by this amount by this date, with this team accountable” is infrastructure.
The technology will keep getting better. The models will keep improving. But the 5.5% aren’t winning because they have access to better technology — they’re winning because they built organizations capable of absorbing and compounding it. That organizational capability doesn’t materialize from a software subscription. It has to be built deliberately, and it takes time. Every quarter spent in plug-in mode is a quarter the rewirers are widening the gap. The choice between plug-in thinking and rewiring thinking is the only strategic decision that actually matters right now.
The question is not whether to build it. The question is whether you start this quarter or the next one.
Sources
-
McKinsey & Company · November 2025