Usage-based pricing (UBP) — also called consumption-based pricing, pay-as-you-go pricing, or metered pricing — is a subscription model where customers pay in proportion to how much they use the product, rather than a fixed fee regardless of usage. Twilio charges per message sent. Snowflake charges per compute credit consumed. AWS charges per hour of compute, per GB of storage, per API call. The customer pays for what they use; their bill grows as their usage grows.
How Usage-Based Pricing Works
Usage-based pricing requires a measurable consumption unit — the metric by which usage is counted and billed. Common usage metrics:
- Volume-based: API calls, messages sent, emails delivered, transactions processed, records stored, queries run
- Outcome-based: leads generated, conversions tracked, events processed
- Compute-based: CPU hours, GPU time, memory-hours, data transferred
- User-interaction-based: sessions, active users, form submissions
The billing model then applies a price per unit (or a tiered rate structure where the price per unit decreases as volume increases) and produces a bill that varies based on actual consumption in the billing period.
The Business Case for Usage-Based Pricing
Natural Alignment with Customer Value
Usage-based pricing is the purest alignment between what a customer pays and the value they receive. A company that sends 10 million emails per month is getting more value from an email delivery platform than a company that sends 10,000. Usage-based pricing makes the customer’s bill reflect that value difference automatically. This eliminates the pricing resentment that flat-rate subscribers often feel when they are paying the same as power users who get far more from the product.
Lower Barrier to Entry
A pay-as-you-go model allows new customers to start with near-zero cost and grow into the product. This removes the “is it worth paying $X/month before I know if this will work for us?” friction that causes potential customers to delay or avoid committing to a flat-rate subscription. Usage-based pricing converts curiosity to trial more efficiently because the initial cost is minimal. The customer begins using the product immediately and the bill appears only after they have received value.
Automatic Revenue Expansion
In a usage-based model, revenue from existing customers naturally grows as those customers grow. A startup that processes 100,000 API calls per month in year one and grows to 5,000,000 per month in year three has generated 50x more revenue for the vendor without a single upsell conversation. This automatic expansion is what drives the extraordinary net dollar retention numbers that usage-based SaaS companies like Snowflake, Datadog, and Twilio have reported. The business grows alongside its customers’ success rather than requiring a separate, active upsell motion to capture that growth.
The Challenges of Usage-Based Pricing
Revenue Unpredictability
The core disadvantage: a customer’s bill varies based on usage, which means the vendor’s revenue varies too. For a pure usage-based model, a customer who cuts their usage in half halves their spend without any formal cancellation or negotiation. This makes revenue forecasting more complex because MRR is not fixed — it is a function of customer usage across thousands of accounts, each of which can change independently. Companies moving from flat-rate to usage-based often find their revenue forecasting processes need significant overhaul.
Customer Anxiety About Unpredictable Bills
Usage-based pricing can make customers hesitant to use the product freely because they are mentally calculating cost with every action. This is the opposite of the desired outcome: you want customers to use the product more, not less. Mitigations include spending dashboards that show current usage and projected cost, billing alerts at thresholds, and spending caps or credit limits that prevent unexpected overages.
Complexity in Sales and Finance
Selling a usage-based product requires sales reps to help prospects estimate their usage before they have used the product, which is genuinely difficult. Enterprise procurement teams often prefer predictable contracted amounts over variable bills. Usage-based vendors often end up offering hybrid models — a committed spend minimum with usage-based pricing above that threshold — to address enterprise finance and procurement preferences.
Hybrid Usage-Based Models
Most successful usage-based companies do not use pure pay-as-you-go. They combine usage-based elements with flat-rate components:
- Committed spend (reserved capacity): a baseline committed usage level (paid at a discounted rate) with usage-based billing above the commitment. This gives the vendor revenue predictability and the customer a discounted rate in exchange for commitment.
- Platform fee + usage: a flat monthly platform fee that covers access, support, and a usage allowance, with consumption-based billing above the included usage. This maintains some revenue floor while providing usage-based upside.
- Freemium + paid usage: a free tier with a usage limit, above which the customer enters a paid consumption model. This is extremely effective for bottom-up enterprise adoption where the free tier seeds usage within an organization and paid usage scales as adoption grows.
Is Usage-Based Pricing Right for Your Product?
Usage-based pricing works well when: usage is clearly measurable, usage directly correlates with value received, customers’ usage scales over time as they grow, and there is a natural “start small and grow” adoption pattern. It works poorly when: usage does not correlate with value (a customer who uses the product intensively to set it up but then barely touches it afterward), switching costs are low enough that variable billing would cause customers to leave during low-usage periods, or the product’s value is primarily in access and availability rather than consumption.