Per seat: simple, predictable, and exposed
Seat pricing is easy to buy, easy to forecast, and the finance team already understands it. The catch with AI is that a seat's cost is no longer near zero — a heavy seat can consume 10× the median, and under flat seat pricing that user is pure loss. It works when usage is naturally bounded by human working hours.
Pure usage: aligned, but hard to sell
Usage pricing perfectly aligns cost and revenue and scales with customer value. It also makes budgeting impossible for the buyer, invites bill shock, and makes revenue forecasting harder for you. Procurement teams frequently reject it outright. Best for developer tools and infrastructure where the buyer is already used to metered billing.
Hybrid: the default for AI products
A seat price with a generous included allowance and metered overage gives the buyer a predictable floor while capping your downside. Set the allowance so 80–90% of seats never see an overage line — those users get the simplicity of seat pricing, and only the heavy tail pays more.
- • Set the included allowance around the 80th percentile of usage.
- • Price overage below your list rate so it feels fair, not punitive.
- • Alert customers before they hit the cap — surprise bills cause churn.
- • Report usage in the dashboard; invisible metering breeds distrust.
Related guides
Long-form playbooks on the same topic, written by the RevenueLab editorial team.
SaaS Pricing Strategy: Per-Seat, Usage, Tiers, and the Hybrid Future
A framework for choosing a SaaS pricing model — when per-seat caps your growth, when usage-based makes revenue volatile, and how hybrid models stitch the two together.
Read the guideLLM Token Costs in 2026: Pricing Every Model, Hidden Multipliers, and Margin Math
Input vs output token pricing across GPT, Claude, and Gemini, the context-window cost trap, how caching and batching cut bills 40–80%, and the real per-user margin most AI apps miss.
Read the guideRevenue Model Glossary: 40 Terms Every Operator Should Know (CPM, RPM, ARPU, LTV, CAC, ROAS…)
Plain-English definitions for the 40 revenue-modeling terms that show up across creator, SaaS, ecommerce, and ads — with the exact formula, a worked example, and the most common misuse for each.
Read the guideFAQ
Should AI products use seat or usage pricing?
Hybrid, in most cases: a seat price with included usage and metered overage. Pure seats leave you exposed to heavy users; pure usage is hard for buyers to budget and frequently blocked by procurement.
How much usage should I include in a seat?
Enough that roughly 80–90% of seats never generate an overage charge — usually around the 80th percentile of usage. That keeps the pricing simple for most customers while capturing the tail.
How do I price overage?
Typically 20–40% below your standalone list rate, while staying comfortably above your cost. Overage priced above list feels like a penalty and drives customers to negotiate or churn.
Will usage pricing suppress adoption?
It can. Users ration metered features, which reduces engagement and the habit-forming behaviour you need. That's a strong argument for a generous included allowance rather than metering from the first unit.
How do I migrate existing customers to a new model?
Grandfather existing plans, launch the new model for new customers, then migrate on renewal with a comparison showing what they'd pay. Forced mid-contract migrations are the classic way to trigger a churn spike.
What unit should I meter?
Something the customer recognises as value — a document processed, a call analysed, a workflow completed — not tokens. Metering tokens exposes you to model changes and means nothing to the buyer.
How this calculator is built
Independently maintained
Written by Sam Doshi and the RevenueLab editorial team. We don't sell the data feeds this tool is built on.
Sourced from primary data
Benchmarks come from public AdSense / Stripe / IRS disclosures and reader-submitted data — never third-party "$X per view" claims. Full methodology.
Last editorial review
Reviewed on a rolling quarterly cycle. Dated reviews are published on the methodology record for each calculator.
Editorial standards
See our editorial policy and disclaimer. Results are estimates, not advice.