Outcome-Based AI Pricing Still Lets the Vendor Keep the Count

← Back · ACT II · Chapter 14: Who Controls Value Engagement?

Outcome pricing now lets the buyer pick what it pays for, but the count still lives in the vendor’s platform, and the event on the invoice is rarely the result the purchase was approved to produce.

A new pitch has started showing up in software pricing. The customer decides what success looks like and pays only when it happens. It usually arrives with outcome-based billing for AI agents: the customer picks an event, such as a qualified lead, a completed transfer or a resolved case, and the invoice counts those events instead of seats or usage.

That is a better place to start than paying for activity, and I would rather see vendors make the offer than not. It also sounds close to what I have been arguing for, that the buyer should write down what a purchase has to produce, and close enough that the difference is easy to miss. That difference decides what the buyer ends up paying for.

The Menu Comes From the Platform

The outcomes on offer are the ones the vendor’s platform can see. A lead marked qualified, a call handed to a person and a closed ticket all happen inside the vendor’s software, so the vendor can count them and bill for them.

The result the purchase was approved for usually happens somewhere else. More of those leads turn into revenue, fewer customers leave, or each case costs less to handle. Those show up in the buyer’s CRM, billing system and ledger, often weeks later, and the vendor’s platform usually does not see them.

The Count Stays Where It Was

The other thing that has not moved is the count. The vendor tracks each outcome in its own system, and that count becomes the invoice. A TechTarget report in October on outcome-based AI pricing among customer experience vendors described customers working through contract language that defines outcomes and how they are measured, “and the vendors have set the terms.”

None of this needs bad faith. We built business cases on the vendor side, and a vendor works from the data its own product produces. The trouble starts when the vendor’s count is the only one. Then the only evidence of value the buyer has is the invoice, written by the vendor it is paying. An earlier post on who holds that number sets out what it takes for the buyer to keep it instead.

Where the Two Drift Apart

Take a purchase approved to grow revenue from inbound inquiries, as an illustration. The billable outcome is a qualified lead. In the first months the count climbs, the invoices climb with it, and everyone is pleased. Whether closed revenue moved is a separate question, answered in the sales system, and nobody was asked to answer it.

Vendors put effort into whatever the contract pays for. A lead qualified a little more loosely still counts, and so does a transfer to the wrong team. Over a year, the billable count and the business result can drift apart without anyone noticing, because only one of them is being reported.

Usage Pricing Has the Same Gap

A lot of AI is still bought by usage rather than by outcome, and finance is feeling it. In Pigment’s third-quarter survey of 2,000 finance executives, published in October, 83 percent said consumption-based AI costs had pushed spending above what they expected. One way to read that spend is cost per run: what each invoice, case or forecast costs once compute and review time are counted.

That is worth knowing, and it answers half the question. Cost per run tells you what each use of the tool costs, but not whether those uses produced what the purchase was approved for. A team can push the cost per case down all year while the cases being handled are not the ones the business needed handled. Finance gets the most from the unit cost when it reads it against the result the business wrote down before signing.

Write the Result First, Then Pick the Event

The fix is mostly a matter of order. Before choosing anything from the vendor’s list, the buyer writes down what the purchase has to produce in its own terms: closed revenue from inbound, customers lost, cost per case. It notes where that number lives today, in its own systems, and the dates when it will be checked.

Then it picks the billable event, which is what the vendor gets paid on. Paying per qualified lead is fine if the buyer has also written down the conversion it expects from those leads and checks it against its own sales records on the named dates. If the leads keep coming and the revenue does not, the buyer arrives at renewal with a number from its own records, and the vendor has a specific gap it can explain or fix.

The contract can carry both. One line, agreed before signature, states what evidence will show the value arrived, who produces that evidence, from whose records, by when, and what follows if it does not. That line, with sample wording, is on The Verification Line page. The result itself is the first entry on a Request for Value, which the business owner writes before any vendor is asked for anything.

What a Vendor That Delivers Gets

A vendor whose events really do turn into revenue has every reason to want the buyer’s number written down. Today it is paid on its own count, and its renewal often rests on how the year felt to the buyer. With the result recorded in the buyer’s own systems, the renewal rests on evidence the buyer produced, which is the kind a skeptical finance team will accept. The arrangement is less welcome to vendors whose events are easy to produce and hard to connect to anything the buyer measures.

The vendor’s count will tell the buyer what it owes. Whether the purchase worked is a separate number, and only the buyer’s own records can hold it.

The Request for Value template and a Word copy of The Verification Line clause are free to use on the Guides page at valuelattice.com/guides/.

References: Don Fluckinger, TechTarget, October 2, 2026, reporting on outcomes-based AI pricing. Pigment, Q3 2026 CFO Index, press release of October 7, 2026 (2,000 CFOs and finance executives in the US, UK, France and Germany, surveyed August 19 to September 21, 2026).

Keep reading: ACT II · Chapter 14: Who Controls Value Engagement?