Your Clients Are Learning a New Way to Buy. The Rate Card Is Next.

Outcome-based pricing is arriving in IT services from the top down. The firms that can price it are the ones that can see their own utilization.

There's a story making the rounds that most IT services leaders read as somebody else's news.

About a quarter of McKinsey's global fees now come from outcome-based pricing rather than billable hours, a figure the firm's UK managing partner put on the record at a London briefing last November. Bain says AI- and tech-enabled work is already around 30% of its business and expects it to approach half. BCG has told investors it sees AI-tied work going from roughly 20% of 2024 revenue to about 40%.

Easy to file that under strategy-consulting gossip. Different tier, different clients, different problem.

I don't think it is. And the reason has nothing to do with what McKinsey does.

The detail that matters isn't the pricing. It's the buyer.

Read past the percentage and there's a smaller detail in the reporting that's easy to miss: the shift is client-led. Clients aren't asking what a defined scope will cost. They're arriving with the outcome they want and asking the firm to price against delivering it.

That's not a pricing model. That's a buying habit and buying habits travel.

The CIO who spent last year in a boardroom paying for a result, not a scope, is the same CIO who reviews your rate card next quarter. She doesn't compartmentalize. Once she has learned that a vendor will share the risk of an outcome, a blended day rate stops reading as a price and starts reading as an opening position.

The pressure won't arrive as an industry trend piece. It'll arrive in a procurement conversation, from a client who now expects something your commercial model wasn't built to offer.

Why AI makes this unavoidable rather than optional

There's an obvious objection: consultants have flirted with outcome pricing for thirty years and mostly retreated to hours. Why would this time be different?

Because the productivity gain is now visible to the client.

When AI compresses research, synthesis, code generation, testing, and documentation, the client can see the compression happening. They read the same coverage you do. The hours behind the invoice stop being a credible proxy for the value delivered, and once that proxy is questioned, the party holding the rate card is the one explaining themselves.

Outcome pricing, in that light, is just the polite mechanism for deciding who keeps the productivity dividend. That negotiation is coming to IT services whether or not any individual firm chooses to lead it.

The part that gets skipped

Here's the question I keep coming back to, and it's an operations question, not a pricing one.

The day you quote an outcome instead of an hour, your margin stops depending on how many hours you can justify and starts depending entirely on how efficiently you deploy people against that commitment.

You've just made a fixed-price promise. Your cost to deliver it is a function of one number:

Utilization.

Over-staff the engagement and you eat the difference, there's no timesheet to pass it through on. Under-staff it and you miss the outcome you were paid for.

Get the mix wrong across a portfolio of outcome-based deals and the damage compounds quietly, engagement by engagement.

And at most firms, that number is reconstructed after the fact, from timesheets and spreadsheets and a handful of disconnected systems, weeks after the margin was already made or lost. You learn in April what you needed to know in February.

That lag was tolerable when hours were the unit of sale. The client absorbed the variance. Under outcome pricing, you absorb it.

Which means most firms are being invited into a commercial model they can't yet see well enough to price.

Two decisions, not one

It's worth separating the things that usually get discussed as a single question.

Selling outcomes is a pricing decision. It's a conversation about risk appetite, contract structure, baselines, and who adjudicates whether a target was hit. Most leadership teams are at least having that conversation.

Delivering outcomes profitably is an operations problem. It's a question of whether you can see utilization and margin as they happen, before the SOW closes, not after the quarter does. Far fewer teams are having that one.

The firms that struggle over the next few years won't be the ones that priced outcomes too early. They'll be the ones that priced outcomes while still running their bench on a lagging report.

Worth noting these figures come from the firms' own characterizations at briefings, not audited disclosures, so treat the specifics as reported rather than settled. The direction, though, is corroborated everywhere you look.