The Teams Asking for AI Aren’t Generating the Revenue
When AI effort flows to whoever is most excited, you can ship for a year and never touch the part of the business that pays for it.
The teams that raise their hands for AI are almost never the teams that generate the revenue. That gap is easy to miss, because enthusiasm looks like traction. Most of the time it isn’t.
Enthusiasm Is a Real Signal
Building for the excited teams first is the obvious move, and for good reason. When a group asks for an AI workflow, they’ve already done half of the change-management work on your behalf. They tolerate a rough first version. Feedback comes back as a note, not a complaint. They volunteer as pilots, forgive the bugs, and — when something finally works — turn into the internal reference you point every skeptic toward.
None of that is a mistake. Friction is the tax on every internal tool, and a willing team pays it without being chased. If you’re standing up an AI practice from nothing, the enthusiasts are how you get a first win on the board before the budget conversation turns hostile. Following demand is a defensible way to start, and anyone who tells you to ignore your most eager users has never had to earn credibility inside an organization that didn’t ask to be changed.
But Enthusiasm and Revenue Aren’t Correlated
The problem surfaces a quarter or two later, when you look at where the effort actually went. In most firms — ours included — a small number of practice groups generate a disproportionate share of the revenue. The litigation teams, the corporate groups, the ones running the largest matters against the tightest deadlines. Those are rarely the people sending the eager Friday-afternoon note about a tool they just read about.
So the work flows one way and the money sits in the other. You can ship six workflows to the teams that asked, run clean pilots, post healthy adoption numbers, and still not have touched the part of the business that pays for all of it. That’s the trap. Every one of those workflows is genuine effort. None of it is evidence that you moved the number that matters.
This is the difference between activity and value, and it’s the easiest distinction to lose when the activity feels good. Adoption dashboards count seats, sessions, and logins — motion. They don’t ask whether the motion is pointed at anything. A number that goes up is not the same as a number that matters, and most AI programs are measured almost entirely on the first kind.
Measuring value would mean asking a harder question: did this workflow change the economics of work that actually bills? Hours returned to a partner on a live matter. Cycle time cut on the review that was holding up a deal. A junior freed from the mechanical first pass so the expensive judgment happens sooner. Those numbers are harder to collect and easier to argue with, which is exactly why programs quietly settle for seat counts instead. The metric you can gather in an afternoon wins over the metric that would tell you the truth.
The Path of Least Resistance Has an Org Chart
Effort doesn’t drift at random. It follows inbound. The teams that email you become the teams you build for, and the teams that email you are the ones already sold on the premise — which means your roadmap gets quietly authored by whoever is most curious, not whoever is most valuable. Nobody decides this in a meeting. It’s the default that takes over when no one sets a different one.
There’s a compounding effect, too. The enthusiast team you served becomes your best case study, so the next enthusiast team hears about it and comes to you, and the flywheel spins entirely inside the low-stakes tier of the business. Each turn feels like momentum. From the inside, a roadmap driven purely by inbound is almost indistinguishable from one driven by strategy — right up until someone asks what it did for the P&L, and the honest answer is a list of teams that were already going to be fine.
The Honest Version of the Other Side
There’s a real counterargument here, and it deserves its full weight rather than a quick takedown. Maybe building for the enthusiasts first isn’t misallocation at all. Maybe it’s sequencing.
You don’t want your first agentic workflow to fail inside the litigation group three days before a filing. The high-revenue teams are precisely the ones who can least afford a broken tool, a hallucinated citation, or a process that quietly drops a step — the stakes that turn a rough pilot into a client problem. Testing on the small, willing groups is how you surface those failures somewhere cheap. You build the muscle, harden the process, and earn the right to walk into the room where the work is unforgiving. Under that reading, the enthusiasts aren’t a distraction — they’re the rehearsal.
That argument is genuinely persuasive. It’s the strongest defense of enthusiasm-led rollout there is, and in a regulated environment it’s often the correct call. Which is exactly what makes it dangerous, because it’s also the perfect cover for never getting to the hard rooms at all.
The Line Between Sequencing and Drift
Sequencing and drift look identical for the first two quarters. Both have you shipping to willing teams and posting good numbers. The only thing that separates them is whether you can name the crossover.
If it’s really sequencing, you can answer three questions today: which revenue group you’re piloting toward, what has to be true before you bring the workflow to them, and roughly when. If those answers don’t exist — if the enthusiasts are simply where the work keeps landing because that’s where the work is easy — then “we’re de-risking first” isn’t a strategy. It’s the story you tell about drift after the fact.
Naming the crossover forces a second, uncomfortable admission: some of the enthusiast pilots you’re proudest of were never going to move the P&L, and were worth doing only as practice. That’s a fine reason to build something. It’s a poor reason to keep building in the same place once the muscle is there.
The discipline is almost embarrassingly plain. Before a pilot starts, write down who it’s for and what graduation looks like. A pilot with a named destination is a sequencing plan. A pilot without one is a hobby that happens to have a roadmap attached. AI without operations is just a demo — and a rollout that only ever serves the people who asked is just enthusiasm with a dashboard.
Enthusiasm tells you where it’s safe to begin. Never let it decide where you stop.
New here? Subscribe for field notes on making AI actually operational inside a real organization. If this one landed, forward it to whoever owns your AI roadmap — the person deciding which team gets built for next.