We Need to Talk About How Consulting Gets Paid

The hourly model has been challenged on and off for most of my career. I think agentic AI just pulled the plug, and most consulting firms, including plenty I respect, are not ready for what comes next.

Bloomberg's estimate stopped me: subscription pricing drops from 60% of software deals to 30% this decade, while outcome-based pricing climbs from 10% to 60%. Read that twice, because it's not a vendor pricing footnote. It's a consulting delivery story hiding inside a software pricing story. If a client's AI agent is resolving support tickets on its own, nobody is paying a human for the hours it took to babysit that queue anymore. They're paying for the outcome. And once a client gets used to paying for outcomes in one part of their business, they start asking why the rest of their vendor relationships don't work the same way. That includes us.

I've sat in enough scoping conversations to know how uncomfortable this shift is going to be. Hourly billing is safer for both sides. It's predictable. It's also the exact model a client questions the second they see an agent do in six minutes what used to take a team a week. If your pricing model can't explain that gap, the client will explain it for you, usually in a renewal conversation you didn't see coming. You had better be prepared.

The firms that figure out outcome-based delivery now, before a client forces the issue, are going to own the next decade of this work. The ones who wait until they're asked will spend that decade playing catch-up on a field their clients designed without them in the room.