Teardowns
Teardown

The strategy was right. Nobody could build it.

A top firm just told every PE owner the AI moat is proprietary intelligence — data, encoded workflows, evals that never stop. They're right. The gap is that naming the moat and building it are two different jobs, and only one of them is for sale.

June 25, 2026 · 3 min read

The deck is excellent. You've read it, or one like it: the durable advantage in AI isn't the model — those are commoditizing by the quarter — it's proprietary intelligence. Your own data, your own workflows rebuilt from the core, a learning loop where evals and monitoring are the real work and never stop. Owned in-house. Undelegable. It sits with the CEO. Every line of it is true, and a top-three strategy firm just put it in front of every PE owner you know.

Then the engagement ends, the team rotates off, and you're holding a beautifully argued thesis about a system that still doesn't exist.

The pattern underneath

Naming the moat and building it are two different jobs, and the model that's best at the first is structurally barred from the second. A strategy firm's product is the recommendation — the framework, the board-ready deck. Its economics run on leverage: a senior name sells it, an army of associates produces it, the engagement is priced to grow and built to end. "Rebuild your workflows from the core" becomes a multi-quarter program. "Evals are sixty percent of the work and monitoring never stops" becomes a slide — sold by a team that leaves when the slide ships. "None of this can be delegated" — delivered by the world's largest delegation business. The advice is sound. The delivery contradicts it line by line.

~0 / 60 / 20
build the agent / evals / monitoring-that-never-stops — the real split of the work · illustrative
Strategy & framing (the deck)
30%
Working system, owned in-house
8%
Multi-quarter program overhead
62%
What you bought vs. what the moat needs — illustrative

The deck names the system. It can't be the system. Those were never the same deliverable.

The reframe is simple once you see it: the thing of value is the working intelligence, not the document describing it. And a working system needs the senior hand on the build, not just in the room for the readout — because the judgment that diagnoses the leak is the same judgment that has to be encoded into the agent, tuned through the evals, and wired into the monitoring that keeps it honest. Hand that off to a junior and you get the artifact a junior can produce: a deck. Keep it on the senior, and make AI the leverage instead of an army, and what lands is the moat itself — built, owned, and still running after the invoice clears.

Distance to a working, owned system — deck vs. build, illustrative · weeks

So keep the deck — it's a good map. Just don't confuse it with the moat. The framework is right that the advantage is built, owned, and undelegable. The part it can't say from inside a strategy model is who builds it. That seat — the senior who diagnoses the leak and then ships the fix the team keeps — is the whole job. It's the half the deck can't do.

Rahul Kanda · 24 years in enterprise delivery

The fastest way in is to point at the leak you feel — at whatmovesit. You'll get the honest read: what it is, whether software actually fixes it, and how far it moves.

Point at your leak