The Five Phases of AI Adoption — and Where Companies Stall

Ask a hundred companies where they are on AI and nearly all of them will tell you they're "doing it." They're not lying. They're just not measuring the same thing.

The latest large-scale enterprise AI research, surveys covering nearly 2,000 organizations across more than a hundred countries, puts numbers on it. 88% of organizations now use AI in at least one business function. About two-thirds, 62%, are at least experimenting with AI agents. Roughly a third report they've begun to scale AI beyond the experiments. Fewer than a quarter, 23%, are scaling an agentic system anywhere in the enterprise. And about 6%, six in a hundred, qualify as genuine AI high performers: organizations that attribute 5% or more of EBIT to AI, the ones that did the deeper thing and redesigned how they work.

The surveys vary on the exact percentages, but the shape never varies. MIT's GenAI Divide study found that roughly 95% of enterprise GenAI pilots deliver no measurable P&L impact. It's a funnel that collapses brutally between "we spent money on AI" and "AI changed how we operate," and almost every company I talk to is somewhere in that collapse, wondering why the spend isn't showing up in the P&L.

I think about that funnel as five phases, and I've given each one a name, because naming the phase you're in is the first honest act of any transformation. This essay is the opener of a series that takes each phase apart: what it looks like from the inside, why companies stall there, and what the transition to the next phase actually demands. Because the central finding is uncomfortable: each transition fails for a different reason, and companies keep applying the fix for one phase to the problems of another.

The five phases

Phase one — Equip. Copilot seats, a ChatGPT Enterprise contract, an AI line item in the budget. This is where 88% of companies live, and most of them mistake procurement for progress. The tools are real. The change is not. I cover this in Equip: you bought the tools and nothing changed.

Phase two — Experiment. The innovation team has a demo. It's genuinely impressive. It has been genuinely impressive for eleven months, and it has never touched a production workflow or a customer. Two-thirds of companies are here, in what I call pilot purgatory.

Phase three — Operationalize. Something agentic is doing real work in production. This is genuine progress, and it's where a new failure mode appears: the agent works, but it's a fragile one-off that one engineer understands, with no evals, no guardrails, and no plan for what happens when the model underneath it changes. That's Operationalize: you built an agent, now make it an employee.

Phase four — Industrialize. Agents are doing meaningful volumes of work across more than one function. Now the problems are operational: evaluation, observability, cost curves, model churn. This is where AI stops being a project and becomes infrastructure, and infrastructure has rules. That's Industrialize: scaling agents without scaling the chaos.

Phase five — Transform. The 6%. The companies that stopped asking "where can we add AI to what we do" and started asking "given what AI makes cheap, how should we work?" Different processes, different roles, different decision-making, different economics. That's the phase where the returns live, and it's the subject of the final essay in the series.

Why the funnel collapses

Each transition in the funnel fails for a different reason, and that matters, because companies keep applying the Equip-phase fix, buy more, train more, roll out more, to problems that live three phases later.

• Equip → Experiment fails because nobody owns the question "what is this for?" Buying is easy; choosing a workflow to change is a decision someone has to be accountable for.
• Experiment → Operationalize fails because pilots are built to demo, not to ship. No eval harness, no error budget, no owner in the line organization, no definition of done.
• Operationalize → Industrialize fails because the first agent was a heroic artifact, not a pattern. Heroics don't replicate; platforms do.
• Industrialize → Transform fails because it stops being a technology problem entirely. It's an operating-model problem, and the people who must change the model are the people the current model made successful.

Notice the progression. The early failures are about focus, the middle ones are about engineering discipline, and the last one is about leadership. That's why "we hired a great ML team" doesn't get you to Transform, and neither does "we bought the best tools." The bottleneck moves as you advance, and by the end it's sitting in the executive suite.

The dirty secret: the phases are not a maturity ladder

Most maturity models imply you should climb one rung at a time. I want to push back on that, because it's exactly how companies waste two years.

You do not need to perfect Equip before you Experiment. You do not need a hundred pilots before you ship one agent. The companies that reach Transform fastest run the phases concurrently on a narrow front: they pick one workflow that matters, take it all the way from tool to pilot to production agent to redesigned process, and let that one vertical slice teach the organization what the new operating model feels like. Then they widen. The companies that stall do the opposite, they go horizontally, rolling tools out to everyone, piloting everything, and finishing nothing.

This is the same argument I made in when building gets cheap, shaping becomes the job: the scarce skill isn't the building, it's deciding what's worth building and how much it's worth. The phases are a diagnosis, not a curriculum.

How I take companies through this

This series doubles as a map of the work I do as an AI-native development and operations leader, because the engagement is structured around exactly these transitions. It starts with an AI-Native Audit: a clear-eyed read of which phase you're actually in, function by function, and where AI creates real leverage versus where it's a distraction. Most executives think they're a phase ahead of where they are. The audit hurts a little. It's supposed to.

Then it's hands-on. Not a slide deck and a retainer, I architect and ship the production systems with evaluation, observability, and cost control built in, while simultaneously rewiring the workflows and decision-making around them so the change survives my departure. White glove means I'm in the codebase and in the boardroom in the same week, because the phase transitions fail precisely in the gap between those two rooms.

Over the next five essays I'll take each phase apart: the traps, the exit criteria, and what the work looks like when it's done properly. If you already know which phase you're stalled in and you'd rather skip ahead, let's talk →