The usage-based / consumption revenue model
Usage-based pricing charges customers per unit consumed — API calls, compute, deliveries — rather than a flat fee, aligning what a customer pays with the value they actually receive.
The basics
Cost aligned with value
A customer who uses very little pays very little, and a customer who scales up pays more automatically — removing the "am I getting my money’s worth" friction that can slow adoption of a flat-fee subscription.
Popular in developer tools and infrastructure
This model is especially common in developer-facing tools and infrastructure software (see our SaaS sector guide for related sub-verticals), where usage naturally scales with a customer’s own growth.
Less predictable revenue
Because revenue depends on customer activity levels, it is inherently less predictable month-to-month than a fixed subscription — customers can also reduce usage in downturns in a way that a locked-in subscription commitment does not allow.
A worked example
A developer-tools company charges $0.01 per API call. Here is the revenue from customers at different usage levels.
| Customer | Monthly API calls | Monthly revenue |
|---|---|---|
| Small customer | 50,000 | $500 |
| Growing customer | 500,000 | $5,000 |
| Large customer | 5,000,000 | $50,000 |
Revenue grows automatically as a customer’s own product scales — no renegotiation needed, unlike a fixed subscription tier that a growing customer might outgrow.
What to check before investing
Ask how concentrated revenue is among a small number of high-usage customers — usage-based businesses can look healthy in aggregate while depending heavily on a few large accounts whose usage (and therefore payments) could drop sharply if their own business slows.
Also ask about revenue predictability and forecasting — usage-based companies typically report "net dollar retention" or similar expansion metrics rather than relying on committed contract value alone, since usage (and revenue) can move up or down within existing accounts.