Usage-based billing recipes/Outcome-based pricing

Build a revenue model that grows when your customers succeed

Every resolved ticket, every qualified lead, every delivered outcome becomes a billing event. Configure outcome-based pricing end to end in Chargebee: define the metric, meter the delivery, invoice per result, and track which accounts are driving the most value.

Model
Per-outcome
Complexity
Low
Building blocks
3
Reference
Intercom Fin
The model

Price the outcome,
not the access

Fin with your current helpdesk Fin AI Agent works seamlessly with any helpdesk, including Salesforce, HubSpot, and more. $0.99 PER OUTCOME i 50 OUTCOMES PER MONTH MINIMUM Contact Sales
Reference Intercom Fin's published pricing. We model it throughout this recipe as a real-world reference. The customer, invoice, and dashboards below are an illustrative worked example, not a real Fin account.

Outcome-based pricing means a customer is billed only when you deliver a defined unit of value. Not per attempt, not per minute, not per seat.

Best suited when:

  • The outcome is discrete and measurable, like a resolved support conversation.
  • Your customers can verify what counts and what does not.
  • The unit price reflects the value actually delivered.

It is especially powerful for agentic products, where the line between success and failure is clear and repeatable.

Fin's published rate, used as our reference: $0.99 per resolution. One billable outcome. That single unit is what this whole recipe is built around.

The recipe

Here's what you need

Three objects in the Chargebee catalog. Set them up once and the outcome is priced. There is nothing else to wire up, which is what keeps this model simple to run.

1
PlanThe anchor
$29/seat/mo

The Fin helpdesk seat the customer subscribes to. Recurring monthly.

2
Metered featureValue metric
Total resolutions

Counts resolution events and sums them for each billing cycle.

3
Metered add-onPrice per outcome
$0.99/resolution

Holds the rate or list price for each successful outcome. This is the protagonist of the recipe.

01 Set up

Price the outcome in the Product Catalog

Fin's structure is a plan plus a metered add-on: a helpdesk seat plan the customer subscribes to, and a Resolution add-on priced at $0.99 per outcome. The add-on meters resolution events to calculate the charge each cycle.

Configure these through the Product Catalog and Metered Features.

Product Catalog Fin planLive
FinHelpdesk plan with a metered outcome add-on
EditAdd charge
ItemsTypePriceStatus
Fin helpdesk seatplan_fin_seat
Recurring
$29.00 /seat/mo
Active
Resolutionaddon_resolution
Metered, per unit
$0.99 /resolution
Active

Need to bill another outcome later? Model it the same way, as another metered feature with its own add-on.

02 Sell

Selling it starts with a quote

Outcome pricing usually rides on a negotiated deal. The agent has to be embedded in the customer's helpdesk and data before it can deliver an outcome, and the rate, commitments, and terms get worked out with the buyer. In Chargebee that runs through CPQ:

  • Selling rules enforce the non-negotiables at quote time, as no-code or AI-configured guardrails.
  • A discount that exceeds a guardrail routes automatically to the right approver, a multi-level four-eyes approval.
  • Native e-signature: the customer signs inside the flow, and the signed quote becomes the subscription automatically, with no re-keying.
Fin
From Intercom, Inc.
Prepared for Northwind Labs, Inc.
Quote
Q-2026-0188
May 28, 2026
Approved Signed
ItemQuantityRate
Fin helpdesk seatRecurring, monthly
25 seats
$29.00 $25.00
$25.00
ResolutionMetered, per resolution
Metered
$0.99
Term
12 months
Usage billing
Monthly
Start date
Jun 1, 2026
Seat discount appliedby Sales · list $29 to $25/seat
Routed to VP Salesexceeded the discount guardrail
Approvedby VP Sales
Sent for signatureto Northwind Labs
Signedby Northwind Labs
Subscription createdautomatically
Before you commit to billing

Track every outcome. Bill the one that earns it.

The hardest part of outcome-based pricing is choosing the right value metric. With Chargebee's schema-flexible usage architecture, you don't have to guess. Send events for all your outcome types with no billing logic attached. Let adoption data show you which metric has revenue potential before you commit.

Fin emits four outcome signals with every conversation. Chargebee ingests all four. Each one gets its own metered feature, kept billing-inactive until you're ready. Flip one on and the meter has already been running.

Metered features30-day view  ·  1 active  ·  3 inactive
Outcome typeEvents (30d)TrendBilling
Resolutionoutcome_type: resolution
31,476
+18%
Active
Procedure Handoffoutcome_type: handoff
4,821
+6%
Inactive
Qualificationoutcome_type: qualification
2,104
+31%
Inactive
Disqualificationoutcome_type: disqualification
9,332
-2%
Inactive
03 Track

From raw event to billed charge

Every resolution your product confirms becomes a number Chargebee can bill. Once your product is connected to Chargebee, resolution events flow in automatically. From there, three things happen.

1 Ingestion
Events arrive
Via API, CSV, S3, or stream, raw or pre-aggregated. Built-in idempotency on a deduplication_id means a retried event is never counted or billed twice.
2 Metering
Your business logic enters here
The meter definition is a filter rule: SUM of events where ticket_status = resolved AND resolved_by = fin. Only events that pass the filter contribute to the billed total. This is where your definition of a billable outcome becomes a hard constraint in the pipeline.
3 Rating
The rate is applied
Chargebee multiplies the aggregated count by the add-on rate of $0.99. That charge is exactly what lands on the invoice.
Usage Events
Send usage events to track or enable monetization of your product's usage.
Processed events! Failed eventsUpdated 0s ago
Recent30 mins1 hr12 hrs
deduplication_idsubscription_idticket_statusresolved_by
conv_45829-ressub_nw_8841resolvedfin
conv_45912-ressub_nw_8841resolvedfin
conv_45830-hansub_nw_8841handoffagent
conv_45933-nrsub_az_2204not_resolvedfin
conv_45934-dissub_az_2204disqualifiedfin
conv_45940-ressub_mw_0071resolvedfin
conv_45941-hansub_mw_0071handoffhuman
conv_45955-nrsub_nw_8841not_resolvedfin
conv_45960-quasub_az_2204qualifiedfin
conv_45971-ressub_mw_0071resolvedfin
filter
Chargebee  /  Metered Features  /  CreateMeter definition
Enter a name for your metered feature *
AI resolutions
resolutionsi
Usage calculation *Define how usage is calculated in your billing model.
CALCULATE
SUM
OF
ticket_id
#
Filter conditionsYour calculation will be performed on the events filtered by these conditions.
WHERE
ticket_status
Aa
equals
resolved
AND
resolved_by
Aa
equals
fin
+ Add OR condition
Metered, June
31,476
×
Add-on rate
$0.99
=
Rated charge
$31,161.24

To reverse an outcome (e.g., if a resolution was incorrectly flagged), create an offsetting event with negative quantity. This ensures the final quantity is accurate without you having to issue a credit note.

04 Bill

Cycle-end. The outcome charge, itemized.

At the close of the billing term, Chargebee totals the metered resolutions and raises the invoice automatically.

Illustrative example, not a real Fin invoice
Fin
From Intercom, Inc.
Billed to Northwind Labs, Inc.
Invoice
INV-2026-0631
Issued Jul 1, 2026
Period Jun 1 to 30, 2026
Line itemQtyUnitAmount
Resolutionmetered
31,476
$0.99
$31,161.24
Fin helpdesk seatrecurring
25
$25.00
$625.00
Subtotal
$31,786.24
Tax
$0.00
Total due
$31,786.24
Behind the resolution line, a usage summary breaks the count down day by day.
Fin
Usage Summary
Invoice
INV-2026-0631
Date
Jul 1, 2026
Amount
$31,161.24
Billed to
Northwind Labs
PeriodJun 1 to 30, 2026
DateResolutions
Jun 01 · Mon
1,200
Jun 02 · Tue
1,132
Jun 03 · Wed
1,188
Jun 04 · Thu
1,290
Jun 05 · Fri
1,218
Jun 06 · Sat
706
Jun 07 · Sun
774
Jun 08 · Mon
1,274
Jun 09 · Tue
1,080
Jun 10 · Wed
1,292
Jun 11 · Thu
1,111
Jun 12 · Fri
1,107
Jun 13 · Sat
799
Jun 14 · Sun
612
Jun 15 · Mon
1,151
DateResolutions
Jun 16 · Tue
1,070
Jun 17 · Wed
1,080
Jun 18 · Thu
1,219
Jun 19 · Fri
1,277
Jun 20 · Sat
762
Jun 21 · Sun
748
Jun 22 · Mon
1,079
Jun 23 · Tue
1,206
Jun 24 · Wed
1,178
Jun 25 · Thu
1,111
Jun 26 · Fri
1,269
Jun 27 · Sat
614
Jun 28 · Sun
761
Jun 29 · Mon
1,098
Jun 30 · Tue
1,070
Total resolutions30 days, June 2026
31,476× $0.99 = $31,161.24

You can give your own customers this granular usage breakdown inside your product, by reading it back from Chargebee's usage APIs, with no separate metering pipeline to build. See the Invoices API and Usages API.

Step 05 · Report

Zoom out to the whole book

So far we have followed a single customer, Northwind Labs. With a single outcome metric running across your customer base, you can track expansion and contraction patterns. Here's what that aggregate view looks like across all accounts.

Billable resolutions · June
612,840
11% vs. May
Resolutions · last 6 months
2.78M
Jan to Jun
Resolutions over timeJan to Jun 2026
295k
Jan
360k
Feb
432k
Mar
498k
Apr
582k
May
613k
Jun
Top accounts by resolutionsJune
AccountResolutions
NLNorthwind Labs
31,476
BSBrightwave Support
24,118
MHMeridian Health
19,442
CSCobalt Systems
15,607
VRVantage Retail
12,283
Start building

Revenue that grows when your customers succeed

Outcome-based pricing aligns incentives: your customers pay for results, you both win when they succeed. Chargebee's metering layer captures every outcome automatically, applies your logic without code, and invoices transparently. You focus on making customers successful.