For the best experience, this project uses the Webflow Input Enhancer extension. We highly recommend installing it. Click here to download (use preview mode to access link)
Resources
Perspectives on AI adoption, operational complexity, and the gapbetween how work is documented and how it actually happens.
AI Strategy
•
January 2, 2026
•
XX
min read
Agents need instructions, not prompts.
Every company wants to adopt AI. Most can't — and the reason isn't what you'd guess from reading the headlines. The MIT NANDA report published earlier this year laid out a number that's been circulating in boardrooms ever since: 95% of enterprise generative AI pilots produce no measurable P&L impact. The instinct is to blame model quality, or vendor selection, or "change management." None of those are wrong, exactly. But none of them are the actual failure mode.Here's what we've seen, working inside dozens of operationally complex businesses: the AI step is almost never where projects fail. The step before it is.
Lorem ipsum dolor sit amet
An AI agent is, in the most literal sense, a system that follows instructions. To do useful work, it needs a precise description of the workflow it's meant to execute — what triggers it, what happens at each step, what the exceptions are, which systems it touches, what counts as success. That's an instruction set. It's what an agent runs on.Almost no company has this. What they have instead are workflows that evolved over years inside inboxes, spreadsheets, and tribal knowledge. The person who knew how the order-intake process really worked left two years ago. The new hire learned it by shadowing someone who learned it by guessing. The Confluence page is from 2019 and it's wrong in ways nobody has time to fix.When you hand that to an agent, the agent fails. Not because the model is bad — because the instructions don't exist.
The three failure paths.
Hand it to the agent. The agent fails — sometimes silently, sometimes catastrophically. The team blames the model. They try a new vendor. The new vendor also fails.
Hand it to the agent. The agent fails — sometimes silently, sometimes catastrophically. The team blames the model. They try a new vendor. The new vendor also fails.
Hand it to the agent. The agent fails — sometimes silently, sometimes catastrophically. The team blames the model. They try a new vendor. The new vendor also fails.
You can't automate a workflow nobody can describe.AI doesn't change that — it makes it worse, because the failure happens faster and at greater scale.
The Bottom Line.
The 95% number is going to keep being cited for years. People will use it to argue against AI investment, or to argue for different vendors, or to argue for slower rollouts. All of those arguments miss the point.
The 95% isn't a problem with AI. It's a problem with the prerequisite to AI. The companies in the 5% aren't using better models — they're operating on better instructions. Until the instructions exist, automation is theater. Once they exist, the rest is execution.
Why 95% of enterprise AI pilots produce zero P&L impact.
A close reading of the MIT NANDA report — and what it actually tells us about the failure mode shared by every stalled AI deployment we've seen.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Latest
AI Strategy
Why 95% of enterprise AI pilots produce zero P&L impact.