The Second Invoice

Somewhere this quarter, one of your clients signed two contracts.

The first was with a software vendor. It's priced on outcomes — the client pays when the software resolves a customer's problem, and nothing when it doesn't. No resolution, no charge.

The second was with the firm hired to make that software work. It's priced by the day: a rate, a number of people, a number of weeks.

One desk. Two invoices. Two completely different answers to the same question — what am I actually paying for?

Keep the three parties straight, because the whole story turns on them: the client who buys, the vendor whose software does the work, and you — the firm that makes it work. This piece is about the third one. Because your client is now holding both invoices side by side, and the comparison does not flatter the one with your name on it.

The software you implement is now priced on the value it creates. You're still priced on the hours you spend implementing it. That gap is about to become the most expensive thing in your business.

For most of the history of professional services, the day rate was honest. The scarce thing was the work itself — hard problems that genuinely took time to solve, and skilled people giving everything they had to solve them. Billing for time was a fair stand-in for billing for value, because time was the bottleneck. Three consultants for six weeks meant something. Everyone understood the deal.

AI quietly removed the bottleneck.

When a smaller team with the right tools does in two weeks what used to take six, the day stops standing in for value. And it gets worse on its own, because the logic is a spiral: the faster your people work, the fewer days you bill — so the better you get at your job, the less you earn, and the harder your client pushes to pay for even fewer days next time. You've built a business that fines you for improving.

This isn't a forecast. The market is already pricing it in. The largest IT-services firm in the world has lost more than a third of its value in a year — while booking record work — because investors have decided that what it sells, people billed by the day, is quietly being eaten. Record bookings and a falling share price at the same time: that's the market saying the unit itself is the problem.

Most firms feel this and reach for the safe move: keep pricing the days, because days are familiar and outcomes are frightening. The safety is a story. It hides the bill for one more quarter.

You don't have to take any of this on faith. Look at the software you implement — the product you build your work on top of. It has already moved.

The new generation of enterprise software is priced on what it achieves, not on who logs in. AI support agents that charge per resolved case — escalations to a human cost nothing. AI sales agents priced like a commission: the vendor gets paid when the deal actually happens, not before. The companies that invented the per-seat licence are walking away from it — because when the software does the work, charging for seats means revenue falls as the product gets better, and nobody signs up to be punished for being good. How a company charges has become a statement of what it believes it's worth.

So look at where that leaves you. The product underneath you is priced on outcome. You, the firm standing it up, are still priced on effort. That's not an industry trend to watch from the touchline. It's a contradiction inside a single purchase order — and your client signs both lines.

Here's where most firms reach for the wrong tool. They read this as a pricing problem and go looking for a cleverer rate card. It isn't a pricing problem. It's a category problem.

The day rate was never really a way of pricing. It was a way of measuring what an engagement cost to run, quietly promoted into a way of charging — and it says nothing about what the work is worth to the buyer. Move off it and you're not changing a number. You're changing what kind of firm you are: from one that sells skilled people to one that sells a result. Different category, different proof, different competition.

In that category, the proof works differently too. A promise nobody has tested earns nothing — what convinces a buyer is your willingness to put something of your own at risk on the result. That doesn't mean betting the whole engagement on day one. It starts smaller: a slice of the fee tied to a target, a pilot priced on what it delivers, a shared definition of success with consequences attached. The willingness is the signal. The amount can grow with the evidence. Either way, the price stops being a way to bill and becomes a way to be believed.

This cuts deeper for you than for any software vendor, and it's worth being honest about why. The vendor has a product to point at. You don't. Strip out the hours and what's left to sell is the argument itself — what you're for, what you change, what that's worth to the person paying. Call it what it is: a value argument, one you can prove and stand behind. The pricing model is just its visible edge. Built deliberately, it's a position. Inherited, it's a confession.

Which raises the question this whole shift turns on: who owns the outcome?

Think about what happens today when a transformation succeeds. Success has a thousand fathers: the vendor points to its platform, the integrator to its delivery, your client's own team to its adoption. Everyone claims the win — which is precisely why nobody can price it. And when it fails? Failure is an orphan. The vendor's software performed to spec. The integrator delivered the agreed scope. Everyone is contractually innocent, and the client eats the miss.

Here's the honest part: that's not anyone's failure. The outcome really is co-produced — the vendor's product, your work, the client's own adoption all genuinely contribute. That's the nature of the work, and no pricing model changes it. But co-production is exactly why outcome pricing can't work as a solo move. Price your slice on the result while the contributions around you stay misaligned, and you've just bought the thousand-fathers problem at your own expense. Outcome-based delivery doesn't need a hero. It needs an aligned triangle — and every aligned triangle needs one party who holds the alignment: who defines the result, makes the contributions line up, and answers for the whole. In success, that party proves who contributed what. In failure, it owns the miss instead of orphaning it.

So who holds that mandate? It depends — and the shift is sorting the industry around exactly that question, along two lines. The first is resolution, and it isn't really a choice: global, multi-country programmes need the mandate held globally, end to end — that's the largest integrators' game, and they're good at it. If your clients' results live in one market, one vendor stack, one management team, your game is there. The second line is the real decision: your posture toward the vendor. Go deep and couple — specialise hard enough on one platform to co-underwrite outcomes alongside the vendor, which is exactly the local partner vendors are now hunting for. Or stay neutral and orchestrate — hold the alignment across whatever mix of vendors your client runs, your independence being the value, because your incentive is the outcome and not any vendor's pull-through. Both are real positions. What doesn't survive is the firm that picks neither: implementing several platforms competently, by the day, holding nothing. That firm is the second invoice with nothing underneath it.

Whichever position you take, holding the mandate is a bigger commitment than it sounds. It means that when the result lands, you can show what actually drove it — and when it misses, you carry real consequences, not a politely regretful invoice. Few firms price that way, and the reason isn't a lack of nerve. It's that the result is co-produced — the vendor's product, your work, the client's own adoption — and accepting accountability for a whole you only partly control feels like a bad trade. It is a bad trade, unless you've done the alignment first. Define the result precisely, line up the three contributions, attach consequences to each — and the risk becomes one you can actually carry. That's the quiet truth of this shift: the alignment work isn't overhead on the way to outcome pricing. It's the thing that makes outcome pricing survivable.

One trap on the way in. The lazy version of this is to bolt a margin onto the vendor's meter — mark up their per-resolution rate and call it outcome-based. Do that and you've made yourself a thin, replaceable layer on someone else's machine. The defensible move is to price the higher-order result the vendor's number merely feeds: they own "tickets resolved," you own "cost-to-serve down, and the customers stayed" — delivered in a form the client can actually run: compliant, sovereign where it must be, adopted by the people who use it. A result that can't be deployed isn't a result yet. That's harder to define, harder to measure, harder to stand behind. The difficulty is the point. An outcome that's hard to own is one your competitors can't cheaply copy and no procurement desk can reduce to a day-rate comparison — you're no longer selling the same unit as anyone else. The hard part is the moat.

One honest caveat, because some of you are already on the far side of this. Outcome pricing isn't new. The corner of marketing where results are easiest to measure — performance media, lead generation — has charged on them for years, and the largest strategy firms now book a meaningful share of fees against outcomes rather than hours. But notice two things. Even where measurement is easiest, most firms stayed on fixed fees — because tying your pay to a result is genuinely hard, which tells you where the real work sits. And the firms that did move often live the mirror image of your problem: paid on the outcome while the platform beneath them still charges by the seat or by usage, carrying the gap whenever the result needs more of the vendor's product. Effort priced under an outcome, or an outcome priced over usage — either way, the chain is realigning one layer at a time, and whoever is out of step with the layer beside them pays for the mismatch. The work was never just fixing your own number. It's holding the alignment across the chain — the one job the vendor can't do and the client won't.

So this was never really a question about pricing.

AI doesn't kill the day rate. It turns the invoice into a test. When the cost of effort collapses, the number on the page has to be carried by something else — and either there's a value underneath it you can prove, or there's only a number. Everyone can now see which.

The firms that come through this won't be the ones with the cleverest pricing table. They'll be the ones that did the harder thing first: decided what outcome they're for, and built the argument for what it's worth. Get that right and the price is almost arithmetic. Get it wrong and no rate card will save you.

That's the whole move — from what you charge to what you're worth. From positioning to the pipeline that follows it.

Your client is already holding both invoices. The only question left is which one yours will look like a year from now.