Why 90% of AI Projects Stay in Pilot Mode (And How to Not Be One of Them)

The McKinsey data is brutal. But the fix is simpler than everyone makes it sound.

McKinsey published a stat in June 2025 that should have gotten more attention:

"About eight in ten companies report using gen AI — yet just as many report no significant bottom-line impact. Horizontal copilots have scaled quickly but deliver diffuse, hard-to-measure gains. 90 percent of vertical (function-specific) use cases remain stuck in pilot mode."

Eight in ten companies. Using AI. With no bottom-line impact.

That's not an AI problem. That's a deployment problem.

The Horizontal Trap

Horizontal AI tools are designed for everyone: ChatGPT for knowledge work, Copilot for developers, generic chatbots for customer service. They scale fast because they're easy to adopt.

They also do almost nothing measurable for your business.

Here's why: horizontal AI augments individual productivity. One person uses it to draft an email faster. That's a nice outcome for that person. But it doesn't change revenue, it doesn't reduce headcount, and it can't be attributed to business outcomes.

The result is what McKinsey calls "diffuse, hard-to-measure gains." Everyone has access to AI. Nobody can prove it did anything.

This is why most companies report zero bottom-line impact despite heavy AI investment. They're deploying horizontal tools that make work slightly faster for individual contributors. The people who need to see ROI (executives, finance) can't find it in the usage data.

The Vertical Opportunity

Vertical AI agents solve specific problems for specific industries. A legal document review agent. A sales SDR agent. A medical records extraction agent.

The difference in business impact is stark:

Horizontal: 10% productivity improvement for 100 people → nice
Vertical: 80% automation of one specific job function → transformative

And yet — McKinsey says 90% of vertical AI use cases are stuck in pilot mode.

Why?

Vertical AI requires real implementation work. You can't just buy a license and turn it on. You have to:

Train the agent on domain-specific data
Connect it to existing workflows
Define measurable outcomes
Get buy-in from the people whose jobs it changes

That's hard. Horizontal AI is easy by comparison.

What Actually Gets AI Projects to Production

I've been running AI agents in production for two years. Here's what separates the 10% that ship from the 90% that stall:

1. Start With the Outcome, Not the Tool

Most AI projects start with: "We should use AI for this."

The ones that ship start with: "Our team spends 20 hours/week on X. If AI handles X, we save $Y/month and can redirect those hours to Z."

The outcome-first framing forces you to define what success looks like before you start building. It also makes it easy to get executive buy-in — because you're presenting ROI, not technology.

2. Pick One Job Function, Not One Task

AI that's scoped to "draft emails faster" never gets measured. AI that's scoped to "handle the entire inbound lead follow-up sequence" produces visible results in two weeks.

The job-function scope is specific enough to implement but large enough to matter. You can point to a workflow that went from 40 hours/week to 2 hours/week and say "this is what AI did."

3. Accept That "Good Enough" is the Goal

The enemy of AI deployment is perfectionism.

Teams spend months trying to get an AI agent to handle 100% of cases correctly. They never ship, because 100% accuracy is not the right target.

The goal is not perfect automation. The goal is "materially better than the manual process."

If your AI agent handles 80% of cases correctly and escalates the hard ones to a human, you've automated 80% of the work. That's transformative even if it's not 100%.

4. Measure the Same Thing Your CFO Measures

If you can't tie your AI deployment to a line item your CFO recognizes — revenue, cost, time-to-close — it won't survive the next budget review.

This means picking metrics like:

Cost per acquisition (reduced by AI handling lead follow-up)
Time to resolution (reduced by AI handling ticket first response)
Revenue per employee (increased when AI handles repetitive work)

Not metrics like: "users are happy with the AI assistant" or "AI generated 500 responses this month."

5. Build the Integration Before You Announce the Product

The worst AI launches: build the AI, announce it to the team, then try to get adoption.

The best AI deployments: quietly integrate the AI into the existing workflow, measure it working in production, then announce that it's available.

You're not asking people to change how they work. You're showing them that part of their work is already handled.

The Vertical Playbook

If you want to avoid the pilot trap, here's the sequence:

Week 1-2: Identify the highest-volume, lowest-complexity workflow in your business. Something that eats significant time but doesn't require much judgment.

Week 3-4: Build a narrow AI agent that handles just that one workflow. No extras, no "while we're at it." Scope it down until it's embarrassingly simple.

Month 2: Run the agent in parallel with the manual process. Measure the difference. Fix what's breaking.

Month 3: If it's working, expand scope slightly and promote to production. If it's not working, figure out why before adding complexity.

Month 6: You have one workflow fully automated. You have real data on what AI does and doesn't handle well. Now you can build the second one — with actual production learning informing the build.

This is not exciting. It's not the "AI will replace everything" narrative. It's a business transformation methodology that happens to use AI as the delivery mechanism.

The companies that figure this out will compound the advantage for years. The companies waiting for AI to get "good enough" will still be running pilots.

This is the gap most AI content misses: it's not about the AI, it's about the deployment. If you want more on building AI systems that actually produce measurable results — I write about AI agent systems every week. Free to subscribe. No fluff.

Tags: aiagents production verticalai automation openclaw business