What is it
Per-outcome pricing is a billing unit where payment is triggered by verified outcomes delivered — distinct from outcome-based pricing models, this refers specifically to “outcomes” as a countable billing unit.
The distinction is worth drawing against the sibling outcome-based pricing model: that is the broad model linking price to results through milestones, royalties, or savings shares, whereas per-outcome billing is the narrow operational version — the invoice line reads “N outcomes delivered” and a rate applies per unit. The outcome must be defined, observable, and verifiable by both parties before billing begins, or “outcomes” becomes a contractual grey area that generates disputed invoices instead of aligned incentives.
Because the billing unit is a result rather than an input, per-outcome pricing is the model most aligned with buyer value. See how usage-based pricing models work for the broader context on aligning meters with value.
How it works
Per-outcome billing requires three structural elements: a precise outcome definition, a verification mechanism, and a per-outcome rate or percentage. The contract must answer “what counts?” before the meter starts running — ambiguity here is where outcome-billing breaks down in practice.
| Dimension | Description | Example |
|---|---|---|
| Outcome definition | A discrete, verifiable result that both parties agree constitutes “one outcome” | A drug candidate advanced to a milestone gate (Recursion); $1 of cloud savings realized (Usage AI) |
| Verification mechanism | How the outcome is confirmed — who measures it, what data source, what dispute resolution | Clinical milestone gate (pharma contract); cloud-bill diff (Usage AI via cloud marketplace) |
| Rate structure | Either a fixed fee per outcome or a percentage of the value the outcome represents | Milestone payment (deal-dependent, often $300M+ potential per program); ~15–20% of savings delivered |
| Timing of payment | When billing is triggered — typically on verified completion, not on delivery attempt | After the milestone is hit and reported (drug discovery); monthly after savings land on the cloud bill (Usage AI) |
Unit math (cloud savings example): Usage AI charges roughly 15–20% of realized cloud savings with no platform fee and no contract. Its own calculator implies about 15%: on $8,000/month of AWS savings the fee is $1,200/month. If savings drop to $0 one month, the fee is $0 — the meter counts only dollars actually removed from the bill.
Unit math (pharma milestone example): Recursion is paid when a program clears a defined gate. Its Roche/Genentech collaboration carried a $150M upfront with more than $300M of milestone potential per program across up to 40 programs; a $30M microglial whole-genome-map milestone landed as one billing event. Across all deals — including a Sanofi collaboration worth up to $5.2B in aggregate milestones — the potential exceeds $20 billion before royalties, each dollar triggered by a separate verified outcome. Isomorphic Labs uses the same structure: its Eli Lilly deal carries a $45M upfront plus up to $1.7B in milestones, and its Novartis deal a $37.5M upfront plus up to $1.2B in milestones.
The structural challenge is asymmetry of information: whoever delivers the outcome usually has more visibility into whether it occurred than the counterparty does. This is manageable for cloud savings — the data sits in the buyer’s own cloud bill — but harder for drug-discovery milestones, which require joint scientific validation over multi-year gates. Well-structured per-outcome contracts specify exactly who measures what, how often, and what happens when the parties disagree. For practical guidance on structuring metered billing, the usage invoicing and billing cycles guide is a useful starting point.
Companies using this
Four companies in the corpus use “outcomes” as a billing unit. Recursion and Isomorphic Labs meter drug-discovery outcomes via pharma-partnership milestones; Exscientia (now part of Recursion) followed the same model before its November 2024 merger into Recursion; and Usage AI meters cloud cost-savings outcomes via a savings-share percentage billed monthly through cloud marketplace.
| Company | Product | Pricing model | Billing units | Free tier | Verified |
|---|---|---|---|---|---|
| Exscientia (now part of Recursion) | AI-driven drug discovery & design platform | No | 2026-06-16 | ||
| Isomorphic Labs | AI-first drug discovery & design (Isomorphic Drug Design Engine) | No | 2026-06-14 | ||
| Recursion | AI-enabled drug discovery platform (Recursion OS) — pharma partnerships, internal pipeline & NVIDIA-powered compute | No | 2026-06-10 | ||
| Usage AI | Cloud commitment management & savings optimization (AWS / Azure / GCP) | Yes | 2026-07-23 |
Explore this theme in the knowledge graph
FAQ
What is per-outcome pricing?
Per-outcome pricing is a billing model where the vendor charges per verified result delivered — a defined, countable deliverable such as a drug-discovery milestone reached or a dollar of cloud savings realized — rather than per unit of compute, time, or access. Payment is triggered only when the outcome is confirmed, so the vendor shares downside risk with the buyer.
How is per-outcome pricing different from outcome-based pricing?
The distinction is between a billing unit and a pricing model. Outcome-based pricing (the model) is any arrangement where price is tied to business results. Per-outcome pricing (the billing unit) is more specific: 'outcomes' is the literal countable object on the invoice — one verified result, one charge. A company can use outcome-based pricing with milestones or royalties as the mechanism; per-outcome billing means the line item is literally a count of discrete outcomes delivered.
Which companies bill per outcome?
In this corpus, four companies use 'outcomes' as a billing unit: Recursion and Isomorphic Labs meter drug-discovery outcomes via pharma-partnership milestones; Exscientia (now part of Recursion) used the same model before its November 2024 merger; and Usage AI meters cloud cost-savings outcomes as a percentage of the dollars actually removed from a customer's cloud bill.
Why is defining the outcome so important in per-outcome billing?
Because the invoice line item is a count of results, both parties must agree in advance on what constitutes 'one outcome' and how it is verified. Cloud savings are easy to verify — the number is in the customer's own AWS bill. Drug-discovery milestones require joint scientific validation and multi-year gates, which is why those contracts specify exactly who measures what and how disputes are resolved.
Related billing units
- Credit-Based BillingA billing unit where customers pre-purchase or are allocated a pool of credits that deplete as they use the product, often at variable rates per feature.
- Token-Based PricingA billing unit common in LLM and AI products, where customers are charged per input and output token processed.
- Per-Seat PricingA billing unit where the vendor charges a fixed fee per named user, regardless of how much each user consumes.
- Per-Resolution PricingA billing unit unique to AI customer-support products, where the vendor charges only when an AI agent resolves a customer issue without escalation.
- Bandwidth-Based PricingA billing unit where customers are charged per gigabyte of data transferred out of the platform.
- Per-Function-Invocation PricingA billing unit where customers are charged per serverless function invocation, often combined with a separate compute-time charge.
- CPU-Hour PricingA billing unit where customers are charged for the CPU time their workloads consume, typically measured in vCPU-seconds or vCPU-hours.
- GB-Hour PricingA billing unit where customers are charged for the memory their workloads consume over time, measured in gigabyte-hours.
- GPU-Hour PricingA billing unit where customers are charged for GPU time consumed, typically measured per-second or per-hour by GPU type.
- Per-API-Call PricingA billing unit where customers are charged per API request, regardless of payload size or processing time.
- Per-GB Storage PricingA billing unit where customers are charged per gigabyte of data stored on the platform per month.
- Media-Minute PricingA billing unit where customers are charged per minute of audio or video processed — used by speech, voice, and video AI vendors.
- Per-Request PricingA billing unit where customers are charged per request served — the generic meter for inference endpoints, search, scraping, and browser infrastructure.
- Per-Event PricingA billing unit where customers are charged per event ingested — the native meter of observability and billing-infrastructure platforms.
- Vector Storage PricingA billing unit where customers are charged for vectors stored or indexed — the storage dimension of vector database pricing.
- Per-Character PricingA billing unit where customers are charged per character of text processed — the standard meter for text-to-speech and translation.
- Per-Document PricingA billing unit where customers are charged per document processed or generated — common in AI writing, SEO, and document-intelligence tools.
- Per-Page PricingA billing unit where customers are charged per page crawled, parsed, or rendered — the meter for web scraping and document parsing.
- Per-Transaction PricingA billing unit where customers are charged per financial or billing transaction processed — the meter of billing and accounting platforms.
- Active-User PricingA billing unit where customers are charged per monthly or daily active user rather than per provisioned seat.
- Per-Task PricingA billing unit where customers are charged per task an automation or agent executes — Zapier's historical unit, now spreading to AI agents.
- Per-Unit PricingA billing unit used by robotics, hardware AI, and some SaaS companies where the metered object is a physical or abstract 'unit' — a robot deployed, a device sold, or a defined deliverable.
- Workflow Execution PricingA billing unit where each end-to-end workflow or automation run is metered and billed, regardless of the compute steps it contains.
- Per-Message PricingA billing unit where each individual message or reply in a conversation is metered, common in AI chat and voice platforms.
- Per-Invoice PricingA billing unit used by billing infrastructure platforms where each invoice generated or processed is metered as the primary cost driver.
- Per-Action PricingA billing unit where each discrete action taken by an AI agent or automation is metered — common in browser automation and agentic workflow tools.
- Per-Image PricingA billing unit where each AI-generated image is metered, common in image generation APIs and multimodal AI platforms.
- Per-Conversation PricingA billing unit where each complete customer conversation — from first message to resolution — is metered as a single chargeable event.
- Per-Record PricingA billing unit where each data record processed, labeled, or extracted is metered — common in data platforms and web scraping services.
- Per-Word PricingA billing unit common in translation and localization platforms where the metered object is the word count of content processed.
- Per-Video PricingA billing unit where each AI-generated video is metered, common in video generation and synthetic media platforms.
- Milestone-Based PricingA billing unit used in drug discovery and biotech AI where payment is tied to achieving defined research milestones rather than time or compute consumed.
- Per-Datapoint PricingA billing unit where each individual data measurement or signal ingested is metered — common in cloud cost intelligence and ML evaluation platforms.
- Per-Interaction PricingA billing unit where each patient-agent or user-agent interaction is metered, common in healthcare AI and customer engagement platforms.
- Data Licensing PricingA pricing structure where access to proprietary datasets or data assets is licensed separately from the software or services, common in AI training data and clinical data platforms.
- Robot-Hour PricingA billing unit where each hour a robot or autonomous system operates is metered — the robotics equivalent of a GPU-hour.
- Per-Contact PricingA billing unit where each contact or lead in the database is metered, common in AI sales development and outbound automation platforms.
- Per-Mailbox PricingA billing unit where each connected email mailbox or sending account is metered, common in AI outbound sales and email automation platforms.
- Browser-Hour PricingA billing unit where each hour of headless browser compute time is metered, common in web scraping and browser automation platforms.
- Per-Generation PricingA billing unit where each AI-generated creative asset — image, video, or design — is counted as a 'generation' and metered accordingly.
- Per-Ticket PricingA billing unit where each customer support ticket handled by an AI agent is metered — common in AI customer service platforms.
- Per-Log PricingA billing unit where each LLM request log ingested or stored is metered — common in AI observability and evaluation platforms.
- Per-Trace PricingA billing unit where each distributed trace — a complete record of an LLM request chain — is metered, common in AI observability platforms.
- Per-IP PricingA billing unit where each IP address or proxy endpoint allocated is metered — used by web scraping proxy providers.
- Per-Device PricingA billing unit where each hardware device or endpoint connected to the AI platform is metered.
- Per-Case PricingA billing unit used in legal AI platforms where each case or matter processed by the AI is metered.
- Per-Report PricingA billing unit where each AI-generated report or analysis document is metered as a discrete output.