You Pay Per Outcome. Your Vendor Counts the Outcomes.

A founder I work with switched her support tool to one of the AI agents everyone's buying this year. Priced per resolution. Ninety-nine cents each, pay only when it actually closes a ticket. She liked that she'd only pay for results. Three months in, the invoice was running 40% above the seat plan it replaced. So she asked her ops lead a simple question: how many of those resolutions were real? He didn't have a way to check.

Neither did the vendor's dashboard. Not in the way she meant.

"Resolved" is the vendor's word, not yours

Look at how a resolution gets counted. Intercom's Fin, one of the more popular tools here, bills a resolution when the customer confirms the answer helped, or when the customer exits the conversation without asking for more. That second case has a name: an "assumed resolution." The customer left. Maybe they were satisfied. Maybe they gave up and emailed your competitor. Either way it lands as a charge on your bill.

I want to be fair to these vendors. They aren't running a scam. Intercom will deduct a resolution if the customer comes back to the same thread later, even across billing periods, and that's a genuine refund. But notice who holds the meter. The vendor defines what "resolved" means, counts the resolutions, and decides when one gets clawed back. You receive a number and a total.

AP has nothing to match against

For a decade your software bills were boring to reconcile. A seat is a seat. You bought 50 licenses, you paid for 50, and finance could tie the invoice to a headcount it controlled. Outcome pricing breaks that link. The quantity on the invoice is now a figure only the vendor can produce, generated by a model whose definition of success you didn't write and can't recount on your own.

A seat-based invoice you could verify. An outcome-based invoice you can only believe. The line item is a claim, and the vendor is the only witness.

That's a control gap, not a rounding error. Take a tool billing 4,000 resolutions a month at a dollar apiece. If 15% are assumed resolutions where the customer simply vanished, you're paying about $600 a month for outcomes you have no evidence occurred. Call it $7,200 a year on one tool. Now run that across every product in your stack that repriced to outcomes at its last renewal. The portion of your software spend that nobody can reconcile is growing quietly, one contract at a time.

Get your own count before you sign

The fix isn't to refuse outcome pricing. Sometimes it's the better deal, and paying for results genuinely beats paying for idle seats. The fix is to stop treating the vendor's count as ground truth.

Before you adopt it, pull a week of the vendor's resolution log and sample it against your own records. Check the assumed-resolution share. Reopen rate. A handful of actual transcripts. Then negotiate the definition into the contract and ask for assumed resolutions broken out as their own line. After that, give one person the monthly job of checking the count, the same way you'd check a contractor's hours before approving the invoice.

Pay for outcomes if you want. Just don't let the company billing you be the only one keeping score.