How Outcome-Based Pricing Changes Revenue Recognition for SaaS and AI Companies

Today, some AI-native software companies charge customers when an agent delivers a defined result, such as a resolved support conversation. In contracts like these, three dates can differ: the day an outcome appears in the product dashboard, the day the invoice goes out, and the day the revenue is recognized. The gaps between them can result in close delays, revenue adjustments, and diligence questions.

ASC 606 can accommodate outcome-based fees, and several of its provisions fit these contracts well. Applying them requires finance teams to pass judgment on four points: what the contract promises the customer, whether customer acceptance affects timing, how expected credits are estimated and constrained, and how recurring revenue is defined for investors.

Outcome, Task, and Hybrid Pricing Models

The label "outcome-based" covers several contract designs, and each behaves differently under ASC 606:

• Per-outcome pricing: The customer pays when a defined result occurs, such as a resolved ticket or a qualified lead.
• Per-task or per-hour pricing: The customer pays for units of agent work or agent time. Vendors can measure the activity independently, so the accounting tends to resemble usage-based pricing.
• Hybrid pricing: A platform fee or monthly minimum is paired with a variable outcome fee, combining fixed and variable consideration in one contract.

Per-outcome contracts can require substantial judgment because the trigger depends on success criteria that can sit partly outside the vendor's control. The rest of this article focuses on that structure.

Identify What You’re Actually Selling

In a subscription, the billing period usually matches the service period, which is why SaaS revenue recognition is straightforward for standard monthly or annual plans. Outcome contracts separate the two. A per-ticket price describes how you bill, and the contract decides what you have promised, which in turn drives when revenue counts. Two descriptions come up most often:

• Ongoing Capability: You promise an AI agent that works for the customer over a period, and the per-result fee is the price of that service. Revenue builds as the service is delivered each month.
• Individual Results: You promise specific results the customer can use on their own, and revenue follows each result.

A continuous service that produces many results often fits the first description. The contract wording, the product design, and how you actually deliver all inform the answer, and an auditor will want that reasoning written down.

Customer sign-off adds another layer. A genuine right to accept or reject a result can affect when revenue counts. A confirmation click on an objectively measurable result, such as a ticket that stays closed for the contractually specified period, generally functions differently. The contract terms, and whether you can show the agreed specifications were met, decide which one applies.

Three moments deserve separate tracking: delivering the service, confirming that the contract's success criteria were met, and settling any later billing dispute. Each can fall on a different date.

Worked Example: A Month of Outcome-Based Revenue

Let’s take a look at a hypothetical example to further illustrate this point.

An AI support customer support platform charges $2.00 per resolved ticket, with a $10,000 monthly minimum and a 30-day dispute window. Assume the contract qualifies for recording revenue as results occur each month, the customer pays March's $13,000 invoice before month-end, disputed amounts are refundable, and past dispute data is representative of current customers.

• March results: Customers confirm 6,500 resolutions, producing $13,000 in fees. The $10,000 minimum is satisfied because fees exceed it.
• Expected credits: Over the prior six months, 3% of billed resolutions were later disputed and credited. Management uses that history to estimate $390 in credits (195 resolutions at $2.00), then separately concludes it is probable that $12,610 of revenue will hold up without a significant reversal.
• March entry: The company records $12,610 in revenue and sets aside the expected $390 as a refund liability.
• Actual disputes: By the end of the window, disputes total 260 resolutions, or $520. The company reduces revenue and increases the refund liability by the additional $130 in April.
• April estimate: Management weighs March's 4.0% actual rate alongside the earlier six months of history and any change in customer mix.

Revenue is recorded as results occur, the reserve for credits comes from historic data, and the true-up lands in the following month. The reserve is an estimate that gets refined, and a written method makes each step repeatable.

Where Contract Terms Change the Answer

When a contract delivers a continuous service and each fee relates to a specific month of that service, ASC 606 can allow revenue to be recorded in that month without forecasting the whole contract. Expected credits and disputes still require an estimate, and auditors test the conditions closely. Specific contract terms then shape the outcome:

The strength of an estimate depends on the data behind it. A company with several years of outcome history has firmer support than a company with a few months, and early estimates generally deserve a more conservative reserve.

How Outcome Revenue Shows Up in ARR

Recognized revenue is a GAAP metric that shows what a company earned in an accounting period. Investors also want to know how much of it will recur, and ARR is the metric that answers that.

ARR is not a GAAP metric, and outcome-based pricing can make defining ARR harder because of month to month variations. Creating separate lines for committed and variable amounts give investors a clearer picture:

• Contracted ARR: The annualized value of fixed platform fees and monthly minimums under active contracts.
• Annualized Revenue Above Commitments: Annualized outcome fees that exceed the minimums, based on a stated lookback period such as a trailing average. However, not all investors would assess your business based on this number; some will only include the minimum level of ARR. That’s what makes it so important to clearly define how the ARR figure is calculated.
• Total Annualized Run Rate: The sum of the two lines, calculated with a consistent annualization method. Each period counts the greater of the minimum and actual outcome fees, plus any platform fee charged separately from the minimum, so nothing is counted twice.

Investors also look at commitment length, because it shows how much of the run rate a customer is obligated to pay. A monthly minimum under a contract cancellable on 30 days' notice supports a far shorter commitment than the same minimum under a twelve-month term. Presenting the lines separately keeps variable usage from looking like committed recurring revenue. Investors evaluating ARR quality look for a written definition and consistent application.

Five Things to Do Before Your Next Audit or Raise

Auditors, quality of earnings providers, and diligence teams reviewing an outcome-based model for the first time commonly request documentation that the company has yet to produce. By taking these five steps, finance leaders can lay the groundwork for a smoother process:

• Write down what each pricing term promises the customer and how revenue follows, including how sign-off clauses were read.
• Document how you estimate credits and disputes, including data sources and how management judges the risk of a significant reversal. Review the estimate at each reporting date, with monitoring built into the monthly close.
• Have the product record when each result occurred and when it was confirmed.
• Give finance a look at new contract terms before sales signs them.
• Reconcile outcome data, invoices, and recognized revenue each month.

Companies that build these habits early shorten the request list at audit time and give investors and acquirers a clearer view of the revenue base during diligence.

How G-Squared Partners Can Help

Outcome-based pricing comes down to four decisions: what the contract promises the customer, whether sign-off affects timing, how much revenue to hold in reserve for expected credits, and how to report recurring revenue to investors. Each decision benefits from written support that holds up under audit and diligence.

At G-Squared Partners, our outsourced SaaS accountants draft revenue recognition policies, design the estimates for credits and disputes, and set up the month-end close process that keeps outcome data, invoices, and recognized revenue in agreement. We also work alongside your product and sales teams so that new pricing terms get reviewed before they reach a contract.

If your company is launching or scaling outcome-based pricing, our team can review your customer contracts, your outcome data, and your current revenue policy, and tell you where the gaps are. Schedule a consultation to get started.