Emerging 1 companies · First observed March 2024 · Updated June 2026

Outcome-based pricing

Quick answer

Paying only when the AI resolves the job — per outcome, not per token or seat — is the most-discussed and least-adopted model in AI. One corpus company ships it cleanly (Intercom Fin, $0.99 per resolution). We track it as a signal to watch, not a pattern.

1 / 43 companies price on outcomes today

What's happening — and why

What's happening: a few products charge by the result the AI produces — Intercom's Fin bills $0.99 only when its agent actually resolves a support conversation. You pay for the outcome, not the seat or the tokens.

Why it's still rare: outcome pricing needs an outcome that's cleanly measurable and attributable to the AI. Support deflection qualifies (resolved or not); most AI work doesn't yet. As agents take on discrete, checkable tasks, more outcomes become billable — which is why this is the model everyone watches even though almost no one has shipped it.

How it works

request AI agent resolved → $0.99 charged not resolved → $0 pay on the outcome, not the input
The buyer pays only when the agent delivers the result — here, a resolved support conversation.

Evidence over time

1 supporting · 3 counter — hover or tap a point for detail, click to jump to the row.

supports ↑ challenges ↓ 2024 2025 2026
supporting evidence counterexample

Evidence

Company Date What happened
Intercom Mar 2024 Fin AI agent priced per resolution ($0.99) — you pay only when the bot actually resolves a conversation, not per seat or per message. The clearest live outcome-priced product in the corpus.

Counterexamples

  • OpenAI · May 2026 — Prices inputs (per token) and seats, not resolved outcomes.
  • Harvey · May 2026 — Per-seat enterprise pricing — value is billed by access, not by task completed.
  • Anthropic · May 2026 — Pure per-token API + seat subscriptions; no outcome unit.

For buyers

Outcome pricing aligns spend with value — but scrutinise the definition: what counts as a 'resolution', who adjudicates it, and how the per-outcome price compares to your fully-loaded cost to do it another way. A loose definition can bill outcomes you wouldn't have paid a human for.

For vendors

Outcome pricing only works where the result is measurable, attributable and hard to game. You need event instrumentation, a defensible definition and dispute handling. Start with a narrow, checkable outcome (a resolved ticket, a completed task) before generalising.

Outlook — what to watch

The catalyst is agents that complete discrete, verifiable tasks — each one a potential billable outcome. Watch whether agentic vendors (coding, support, research) adopt per-task pricing; if two or three do, this graduates from a single-adopter signal to a genuine trend.

Bottom line

Outcome-based pricing is the field's favourite idea with one live example. It aligns price with value but demands a measurable result — so it stays confined to support deflection until agents make more outcomes countable.

FAQ

What is outcome-based pricing for AI?

Charging for the result the AI delivers — e.g. a resolved support ticket — rather than for seats, messages or tokens. You pay when the job gets done.

Who uses outcome-based pricing?

In the corpus, Intercom's Fin is the clear live example at $0.99 per resolution. It's widely discussed but almost no other vendor has shipped it, because most AI work lacks a cleanly measurable outcome.

Why isn't outcome pricing more common?

It needs an outcome that's measurable, attributable to the AI and hard to dispute. Support deflection fits; open-ended generation doesn't. Agentic products that complete discrete tasks are the most likely next adopters.

All trends