Let’s talk about the invoice that only arrives once the work is done — and why the company sending it now wants a say in how the work gets decided.
Picture a support desk on a Tuesday afternoon. The dashboard says seventy-one percent resolved by the bot. The number is true, in the only sense the system can check: the customer stopped replying. Some of them stopped because it was fixed. Some stopped because they gave up, or went to a competitor, or phoned the one friend who understands computers. All of them look identical in the report. Nobody lied. The metric just doesn’t have a field for “walked away.”
That’s the shape of the new software deal.
For twenty years, software was paid for like a building. You rented the space, you paid per seat, and whether the work inside it went well was your problem. The vendor got paid either way. Misaligned, but at least honest — you knew what you were buying. A tool.
Then the tool started doing the work. And the invoice changed with it.
Per resolution. Per conversation. Per ticket closed. Per claim processed. Per agent action. The pitch is genuinely beautiful: we only get paid when it works. Alignment. Skin in the game. And the CFO loves it, because the cost looks variable and the pilot looks free.
Here’s what’s actually being sold. Not access. Authority.
Think about what a vendor needs in order to promise an outcome. It needs to be allowed to act, not just advise. It needs the definition of done. It needs the data to prove it did the thing. And it needs the workflow arranged so the meter can see the work. Four things, and every one of them is a piece of your business you used to hold.
The definition is the first door, and it’s the one nobody reads. “Resolved” is not a fact about the world. It’s a sentence somebody wrote. In most contracts, it’s written by the party that gets paid when the number goes up. And a metric under pressure doesn’t get gamed by villains. It gets gamed by ordinary people doing their job. The agent offers a refund the policy didn’t authorise. The ticket gets closed as a duplicate. The customer gets transferred to a queue that resolves things by never answering. All of it inside the definition. All of it billable.
The second door is the workflow. Once you’re paying per resolution, every process gets redrawn around what the meter can count. The messy case that needs a human, three calls, and a favour from the warehouse — that case becomes a cost centre. Nobody bans it. It just stops getting staffed.
The third door is the record. The evidence of what happened lives in their system, in their format, under their retention policy. So when the number is wrong, and it will be wrong, you’re arguing about your own business using their receipts.
And the fourth thing is the quiet one: the price. Outcome pricing looks cheap at pilot volume, because the hard cases are still being handled by your people. Then the easy volume migrates, the vendor’s per-unit cost falls, and the rate card doesn’t. You end up paying a fixed fee per unit of work that gets easier every quarter. That isn’t alignment. That’s a toll with a progress bar.
Why now? Because per-seat pricing dies the moment the software does the work. If one agent replaces four licences, the vendor’s revenue falls exactly as the product gets better. So every AI company is being pushed off seats and onto something that scales with the volume of work rather than the headcount. That’s a rational answer to a real problem — theirs. The consequence is that their revenue now grows with the number of decisions they touch, and the cheapest way to grow that number is to widen what counts as done.
I’m not saying outcome pricing is a con. It’s better than paying for seats nobody uses. If a vendor will genuinely put a slice of its fee at risk on a result you defined, take the meeting, because that costs them something real.
The problem is who writes the result.
Watch it happen in a company of forty people. The ops lead signs a per-resolution deal for the support desk. Six months later the board wants to know why headcount didn’t drop and the software line tripled. The answer is that the machine handles the easy sixty percent, and the humans handle the rest, plus the cleanup, plus the escalations the machine created. Nobody can prove it, because the reporting belongs to the vendor. The ops lead isn’t lying. She’s reading the only dashboard she has.
So here’s the operator lesson this week, four lines.
One. Write the outcome definition yourself, in your language, with the failure case named. Resolved means the customer’s problem is gone and they said so. Not that they went quiet. Put it in the contract with a worked example, and the right to audit against it.
Two. Keep the record. Every transaction, every decision, every handoff, exported to your system on your schedule, in a format you can query without them. If leaving takes a project, you don’t have a record. You have a hostage.
Three. Price the failure. What do you pay when a resolution gets reopened? If the answer is “nothing, we just pay again,” you’ve bought a meter, not a result.
Four. Keep one human path that isn’t metered. Not for sentiment. For signal. The escalation queue is the only place your customer tells you the truth about the machine, and the moment it bills per touch, somebody will make it disappear.
The bigger pattern isn’t about support desks. Every AI vendor in every category is walking the same road: from selling you a tool, to selling you the work, to quietly becoming the party that decides whether the work was done. It’s the move the cloud made when it went from hosting to identity to the whole stack. It’s the move the app store made when it went from distribution to payment to policy. The interface changed. The incentive didn’t.
And there’s a human thing underneath it that gets lost in the procurement deck. A business is a set of promises made by people who can be asked about them later. When the promise gets automated, and the meter decides whether it was kept, the person who made it stops being reachable. Not maliciously. Structurally. There’s no name on the resolution.
The principle worth keeping is simple, and it isn’t anti-AI. A service should be measured by the human’s result, not the vendor’s metric. And the authority to decide what counts has to sit with whoever carries the consequence when it’s wrong. If that’s you, you write the definition, you hold the record, and you keep the exit.
If it isn’t you, you didn’t buy a service. You rented the right to be told you were served.
You’ve got this. But read the definition first.