Seat vs usage-based revenue simulator
Compare seat-based and usage-based pricing across your customer mix to see which model captures more revenue — and which customers win under each.
Set your per-seat and per-unit prices, then define your customer tiers. The simulator shows total revenue under each model and flags which tier pays more or less depending on the model.
Pricing inputs
Pricing
Per user, per month.
Per API call, row, action, etc.
Customer tiers
| Tier | Customers | Avg seats | Avg units / mo | Seat rev | Usage rev |
|---|---|---|---|---|---|
| Total | — | — | — |
Revenue comparison
Seat-based total MRR
—
Usage-based total MRR
—
How the comparison works
Seat-based revenue per tier = customers × average seats × seat price. Usage-based revenue per tier = customers × average monthly units × unit price. The crossover point — the usage level where both models charge the same — is seat price × seats ÷ unit price. Below that usage level, usage-based costs the customer less; above it, usage-based costs more.
This simulator assumes all customers within a tier are identical. In practice, usage varies within tiers, which is why usage-based pricing often yields higher revenue from high-usage outliers who would be capped at a seat-based price that was set for the median customer.
About this tool
This tool compares seat-based and usage-based pricing models across a configurable customer distribution. Inputs: per-seat price, per-unit usage price, and four customer tiers (name, customer count, average seats, average monthly units). Outputs: revenue per tier under each model, total revenue comparison, and a crossover analysis showing which model is more favourable for each customer segment. Helps decide whether to price by seat, by usage, or where the transition between models makes sense.
Frequently asked questions
What is seat-based pricing?
Seat-based pricing charges a fixed amount per user or "seat" who has access to the product, regardless of how much each seat actually uses it. It's simple to understand and predict for both buyer and seller. The risk is that customers with many low-usage users feel they're overpaying, while customers with heavy single-user usage feel they're getting a deal. Common in collaboration tools, CRMs, and project management software.
What is usage-based pricing?
Usage-based pricing (also called consumption pricing) charges based on how much a customer actually uses — API calls, rows processed, emails sent, transactions completed. Revenue scales with customer value delivery, which improves retention and expansion naturally. The downside is revenue unpredictability: customers can dial usage down in response to budget pressure, and forecasting becomes harder. Common in infrastructure, API products, and data platforms.
How do I choose between seat and usage-based pricing?
The right model depends on how value is distributed across your customer base. If most customers use the product similarly regardless of team size, seat-based pricing is simpler and more predictable. If usage varies significantly — some customers using 10× more than others — usage-based pricing captures that value and avoids large customers being subsidised by pricing designed for small ones. Many companies use a hybrid: a per-seat base plus overage charges for high usage, or a usage-based model with a minimum commitment.
What is a pricing crossover point?
The crossover point is the usage level at which a customer pays the same under both pricing models. At usage below the crossover, the seat-based model is cheaper for the customer (and generates less revenue for you). At usage above the crossover, usage-based pricing charges more. Knowing this point helps you identify which customers each model incentivises to stay or upgrade.