Let’s talk about the invoice you are about to stop being able to explain.
Picture a small business at the end of the month. One line item on the bill says “1,842 successful customer outcomes.” The owner asks the obvious question — successful according to whom — and gets a dashboard, a smooth answer, and no way to check a single one of those 1,842.
That isn’t a thought experiment. That’s where software pricing is heading, and it’s moving fast.
For thirty years you paid for software by the seat. Ten people, ten licences, one number you could argue about once a year at renewal. Then the models arrived and it became consumption — tokens, calls, minutes. Now the third skin is settling in, and it’s called the outcome. You don’t buy the tool. You pay per resolved ticket. Per booked meeting. Per closed claim. Per completed task.
Sound fair? On paper it is. That’s exactly why it’s worth pulling apart.
All three skins were sold to you as alignment. Seats meant paying for people who might never open the thing. Tokens meant paying only for what you actually consumed. Outcomes mean you only pay when something real happened. Every step sounds like the vendor tied their own hands. Every step also moved one more decision out of your control.
Seats, you controlled — you can count your own staff. Tokens, you could mostly follow — usage logs, a unit you at least recognised. Outcomes are different, because an outcome isn’t a thing. An outcome is a definition. Somebody has to write the rule for what counts as resolved, and the party that writes it is the party that gets paid by it.
Here’s the part nobody says out loud. The moment the vendor’s agent does the work, you lose the two things that made a bill arguable in the first place. You can’t inspect the labour, because there is no labour to watch — there’s a model and a queue. So the only thing left to audit is the meter. And the meter sits inside their system, reads their telemetry, and runs on the same data they use to improve their product.
That’s not a billing detail. That’s the entire relationship.
And we have been here before. Advertising ran on self-reported reach for a century until the people paying stopped believing the numbers, and an entire independent measurement layer had to be invented to referee what the seller was grading themselves. Cloud bills went through the same fight. Every metered market that gets big enough eventually produces a dispute, and the dispute always lands on the same question — whose number is the true number.
Keep an eye on the standards work being done right now around agent payments and agent identity. The metering rules arrive through that same door, because you cannot settle a machine-to-machine transaction without first agreeing what counts as delivered. Whoever gets into that room early shapes what “done” means for the next decade of software.
There’s a second-order effect, and it’s the one that actually hurts. Once outcomes are the unit, the vendor’s incentive shifts from doing the work well to proving the work happened. Anything that can’t be booked as an event goes invisible — the messy, slow, badly-defined job that took twice as long and produced all the value. That same blind spot is already inside your own company. Whatever you can’t count stops being counted, and after a while it stops being done.
And if you sell services, read that twice. Someone is building a wrapper that will bill your client per outcome, using work that looks a lot like yours, with a meter between you and the customer. That meter will not be yours.
So what does a serious operator do about it.
You do it before the meter starts running. Five questions, all in the same meeting:
What exact event increments the count — and what excludes it.
Who computes it, and can I watch the computation happen.
Can I pull the raw event log out of your system, in a form a human can read, on demand.
When we disagree on a line, who decides, and what does the mechanism look like — not the tone, the mechanism.
And if I take that log and recompute the bill myself, do we land on the same number.
If the answer to the last one is anything but yes, you aren’t buying a service. You’re buying an allowance.
The principle underneath all of this is simple, and it isn’t anti-vendor. Outcome pricing can genuinely be the fairest deal on the table — it puts real risk on the seller, and that’s rare. But fairness only holds if the person paying for the work also defines what counts as finished. Otherwise the machine isn’t just doing the job. It’s writing the receipt, reviewing its own performance, and telling you what the work was worth.
Your business is allowed to demand that. Insist on the export. Insist on the definition. Keep the ability to count your own money.
You’ve got this.