H
Glossary
Hybrid Seat and Usage Pricing
Hybrid seat and usage pricing charges a customer a recurring fee per user account and a metered fee for consumption in the same billing period. The seat fee buys access for named people. The meter charges for volume those people generate, and both land on one invoice.
Key Takeaways
The seat fee prices access and the meter prices volume, so any value on both lines charges the customer twice.
Intercom runs this shape in public: Advanced seats at $85 per seat per month paid yearly, plus Fin outcomes from $0.99 each, checked September 2026.
Seats with a separate meter differ from seats with an included allowance: the first bills two products, the second bills one with a ceiling.
A seat added on day 14 prorates against the calendar and a meter reading doesn't, so the two halves of one invoice follow different clocks.
How do you split the seat fee and the usage fee?
Put access on the seat and volume on the meter, and keep any single unit of value off both lines.
What the customer gets | Line that charges for it | Reason |
|---|---|---|
Login, workspace, roles, audit trail | Seat fee | Cost tracks headcount, not throughput |
Inbox, dashboards, admin tools | Seat fee | A second person doubles the need, a busier Tuesday doesn't |
API calls, tokens, documents, AI resolutions | Meter | One person can multiply machine volume |
Storage past an included floor | Meter | The bill follows the data |
Charge a seat for something a script can do and you've priced a human for machine work. Meter something the customer can't influence, like a background sync on your own schedule, and the line reads as a penalty.
A team of two that processes ten million events pays almost nothing on the seat line, so per-seat pricing alone underprices the heavy account. That's why products bolt a meter on instead of raising the seat rate for everyone.
Which products fit seat plus usage pricing?
This shape fits products where people and machines both drive cost and one doesn't predict the other, which is where support software, CRMs, and AI-equipped data tools sit.
Intercom publishes both halves. Seats run $29 (Essential), $85 (Advanced), and $132 (Expert) per seat per month paid yearly, and Fin AI resolutions start at $0.99 per outcome, counted when the customer confirms resolution or Fin completes a workflow. Ten Advanced seats cost $850 a month before a single resolution. Add 400 outcomes and the invoice reads $1,246, with 32% of it moving month to month.
The products that fit share a pattern:
Headcount grows slowly while automated work grows fast and independently.
Buyers want a floor they can budget and a variable line tied to results.
Usage concentrates in a few accounts, so one flat seat rate overcharges the rest.
Where seats and usage move together, the fit breaks. If every new user adds the same predictable volume, the meter is noise on a seat count that already tracks it, and consumption-based pricing reads cleaner.
What goes wrong on the invoice?
The invoice breaks where the two lines disagree about time. A seat is a state that changes on a date, usage is a running total, and reconciling them starts most disputes.
Mid-cycle seat changes. Five seats added on day 14 prorate, the meter doesn't, and the customer asks why only half the bill reacted.
Access removed, usage kept running. An offboarded user's API key keeps firing. The seat disappears, the metered charges don't, and it reads as an error.
Double counting one action. A per-user feature that also emits a billable event charges twice for one click, turning a customer into a churn risk.
Allowance confusion. Buyers read included usage as a discount and a separate meter as a new bill, so moving off bundled overage charges reads as a price rise even when the total drops.
Two invoices instead of one. Systems holding subscriptions and meters separately emit separate documents, and finance reconciles by hand.
Both lines need one customer record, one cycle boundary, and one invoice.
Related terms
Where to go next depends on which half of the model you're working on.
Hybrid Pricing Model is the parent concept, covering every combination of mechanisms rather than seats plus a meter alone.
Per-Seat Pricing explains the seat half alone, including how seat counts get defined and audited.
Consumption-Based Pricing covers the metered half when no seat fee sits underneath it.
Overage Charges covers the alternative to a separate meter: an allowance inside the seat fee, with charges past the line.
Metered Billing is the cycle-close operation turning a usage total into invoice lines.
Consolidated Invoicing lands both charge types on one document instead of two.
FAQ
Is hybrid seat and usage pricing the same as seats with overages?
No. Seats with overages bill one product carrying an included allowance, so charges start only once usage passes that line. Hybrid seat and usage pricing bills two products at independent rates, so the meter charges from the first unit.
What percentage of the bill should be usage?
There's no universal number, but the variable share decides who the model serves. A bill that's 90% seats behaves like a subscription with a rounding error, and one that's 90% usage makes the seat fee look like an access tax.
Does adding a meter on top of seats slow adoption?
It can, when the meter prices something the buyer can't predict. Teams cut that friction with standard moves:
Publish the per-unit rate so procurement can model the cost.
Give the metered line a spending cap or an alert threshold.
Keep collaboration features on the seat fee, so inviting a colleague never raises the variable bill.
How do you count seats when AI agents do the work?
Count only human accounts as seats and push agent activity to the meter. Billing an AI agent as a seat hits a definition problem fast, because one agent does the work of twenty. Per-outcome charges tie the price to work performed.
Back to glossary
