Usage-based pricing
Also known as: consumption-based pricing, pay-as-you-go pricing
In short
Usage-based pricing is a model where the customer pays based on measured consumption of the product, for example per API call, per record enriched, or per gigabyte stored. The bill rises and falls with use.
It ties price to delivered value, which lowers the barrier to start. The trade-off is that revenue and customer budgets become harder to predict than under fixed subscriptions.
Common usage-based structures
- Pure pay-as-you-go: The customer is billed only for what they used in the period.
- Committed use: The customer commits to a minimum spend and pays overages above it, which gives the vendor a revenue floor.
- Tiered or volume pricing: The unit price drops as consumption passes set thresholds.
- Hybrid: A base platform fee plus usage charges, often combined with seats.
Choosing the usage metric
The metric is the most important decision. It should be something the customer understands, can control, and links to the value they get.
Good metrics
Units that scale with outcomes, such as verified contacts delivered or transactions processed.
Weak metrics
Units that grow with no added value, or that customers cannot predict. Surprise bills damage trust quickly.
Pros and cons for GTM teams
- Low-friction start: Buyers can try the product with a small spend, which shortens the sales cycle.
- Built-in expansion: Revenue grows as customers use more, without a new negotiation.
- Forecasting difficulty: Finance and sales need to model consumption, not just count contracts.
- Budget anxiety: Buyers may limit use to control cost, which slows adoption.
Example and common mistakes
Say a data tool charges per enriched record. A customer who enriches a small list this month and a large list next quarter pays accordingly. Offering spend alerts and a committed plan helps them budget.
- No usage visibility: Customers need dashboards and alerts before the invoice arrives.
- Metric mismatch: Charging for something that does not reflect value makes customers feel penalized.
- Compensating reps on signed value only: Reps need credit tied to realized usage, or they undersell expansion.
Usage-based pricing FAQs
What is usage-based pricing?
Usage-based pricing is a model in which customers are charged according to how much of a product they actually use, measured in units such as API calls, records processed, or storage consumed, rather than a flat fee per period or per user.
What is the difference between usage-based pricing and seat-based pricing?
Usage-based pricing charges for consumption, while seat-based pricing charges for the number of users with access. Usage pricing scales with activity and can be less predictable; seat pricing is predictable but ignores how much value each user gets.
What are examples of usage-based pricing in SaaS?
Examples include paying per API request, per email sent, per record enriched, per gigabyte stored, or per transaction processed. Many vendors combine these with a base subscription or a committed minimum spend.
How do you forecast revenue under usage-based pricing?
Model consumption by cohort, using past usage growth, seasonality, and onboarding ramp, and separate committed minimums from variable overage. Review actual usage against forecast monthly and adjust assumptions as customer behavior changes.
