Usage-based pricing, also called pay-as-you-go or metered pricing, bills customers for the amount they actually use: API requests, gigabytes stored, messages sent, minutes of compute and so on, instead of a flat fee.
Why it matters
It lowers the barrier to starting, because small customers pay little, and revenue grows automatically as customers grow. Cloud infrastructure, communications APIs and AI services commonly use it. The trade-offs are less predictable revenue for the seller and less predictable bills for the buyer, so many products combine a base subscription with included usage and overage charges.
Example
Included: 10,000 requests per month
Overage: 0.40 per 1,000 extra requests
Month with 25,000 requests:
15,000 extra -> 15 x 0.40 = 6.00 overageBilling needs accurate metering, usage dashboards and alerts so customers are not surprised.
Common mistakes
- Choosing a usage metric that does not track the value customers receive.
- Offering no spending caps or alerts, which causes bill shock.
- Ignoring how hard forecasting becomes for finance teams.
- Assuming it always beats per-seat pricing; the better model depends on the product.
Related
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.