Some AI vendors are shifting from charging per token to charging per result. It sounds simple: you pay when the agent does its job. But finance teams inherit new questions: what counts as the job, who confirms it, and when revenue is earned.
Let’s walk through the billing and accounting side.
What Outcome-Based Pricing Is
Per-seat pricing charges for people. Per-token pricing charges for model consumption. Per-action pricing charges for each completed task. Outcome-based pricing charges only when a defined result is achieved.
A real example is Intercom’s Fin AI agent, priced at $0.99 per outcome. Its documentation counts a resolution when the customer confirms the answer worked or leaves without asking for more help. It also charges only one outcome per conversation.
That second path, an “assumed” resolution, is where finance should pay attention. Silence counts as success.
Where It Sits Among AI Pricing Models
Zenskar’s token-based pricing guide describes four models: per-token, prepaid credit packs, per-action, and hybrid. Outcome-based pricing is the closest cousin of per-action. The difference is that you bill for a verified result, not a completed step.
Many teams will blend models. A hybrid pairs a base commitment with usage components, which gives vendors a revenue floor and customers a predictable baseline. A platform fee plus an outcome fee fits that pattern.
Billing Challenges
- Defining the outcome. Zenskar’s guide warns that without a precise, auditable definition written into contracts, disputes follow. “Resolved” needs a legal meaning, not a marketing one.
- Verifying it. Did the customer confirm or just go quiet? Your invoice should say which.
- Who confirms. The customer, the system, or a human reviewer? Each choice changes your dispute risk.
- Disputes. If a customer claims an outcome failed, you need event-level evidence, not a summary count.
- Cost-to-serve volatility. A flat per-outcome price can hide a swinging cost base. Zenskar’s guide notes that one action can trigger dozens of model calls, so a hard case costs more than an easy one at the same price.
Revenue Recognition Under ASC 606
ASC 606 doesn’t have an outcome-pricing chapter. You apply the usual five steps to your specific contract. The treatment below is a framework, so confirm it with your auditors before you rely on it.
Identifying the Performance Obligation
The first question is what you promised. If your SaaS billing software includes an agent that stands ready to handle whatever volume arrives, that can be a stand-ready obligation. PwC’s TRG guidance discusses this for usage-based contracts, and some companies account for it as a single series of distinct service periods. If you instead promise discrete results, you may treat each one differently.
Read the contract language closely. The accounting follows the promise, not the price list.
Variable Consideration and the Constraint
Outcome fees are variable by nature. ASC 606-10-32-40 allows a variable amount to be allocated entirely to a distinct period within a series if specific criteria are met.
When that doesn’t apply, you estimate the fee using expected value or the most likely amount (32-8). You then constrain the estimate so you don’t book revenue likely to reverse (32-11 and 32-12).
A hypothetical: you expect 40,000 outcomes at $0.99, or $39,600. If your resolution rate swings widely, the constraint may lower what you recognize.
Timing of Recognition
Recognition generally follows the confirmed outcome, as your contract defines it. If your terms use a waiting window, such as a 24-hour silence rule, outcomes late in the month need a cut-off policy. Decide it before your first close, not during it.
Data and Metering Requirements
Every billable outcome should be an event with evidence attached. Capture a conversation ID, customer ID, timestamp, outcome type, how it was confirmed (explicit or assumed), and any reversal flag.
That record becomes your audit trail. It also settles disputes in minutes, not days.
Pricing Risk: Caps, Floors and Minimums
Outcome pricing puts revenue on a seesaw. Caps protect customer budgets, and floors protect your margin.
A hypothetical structure is a $5,000 monthly minimum with a $20,000 cap. Threshold alerts help on both sides. Customers shouldn’t learn about a spike from their invoice.
Questions for the CFO Before Launch
- What’s the exact written definition of an outcome, and who can change it?
- Do we bill assumed outcomes, and what’s our dispute window?
- Is our promise stand-ready or per-result, and has our auditor agreed?
- How will we estimate and constrain variable fees at each close?
- Does the margin hold if cost per outcome doubles on difficult cases?
Billing Infrastructure for AI Pricing
Whatever you charge, your systems must meter it accurately. Zenskar’s AI solutions support usage-based, token, credit, hybrid, and prepaid-with-overage pricing through a no-code contract builder and ingest usage via APIs.
On the finance side, the page explains how Billing usage metrics, rating tables, and invoice calculations help reduce disputes. It also covers revenue recognition rules for usage-based and hybrid models, including journal entries for revenue, deferred revenue, and receivables under ASC 606 and IFRS 15. See the revenue recognition page for schedules and ERP-synced entries.
The AI page doesn’t mention outcome-based pricing. If that’s your model, ask Zenskar how your outcome definition would map to billable events.
Conclusion
Outcome-based pricing is easy to say and hard to account for. Define the outcome tightly, keep evidence for every event, agree the accounting early, and cap the swings. Which of your outcomes would be hardest to defend in a dispute?
Key Takeaways:
- Outcome-based pricing charges for a verified result, not tokens or steps.
- Intercom’s Fin shows the model: $0.99 per outcome, with assumed resolutions counted.
- Define, verify, and document every outcome. Vague definitions cause disputes.
- Under ASC 606, performance obligations, variable consideration, and constraints depend on your contract. Confirm with auditors.
- Capture event-level evidence for your audit trail.
- Use caps, floors and alerts to manage margin and customer budgets.
