Consumption model
kun-SUMP-shun MOD-ul
A pricing structure where revenue scales directly with customer usage. Broader than usage-based pricing, it includes credits and commitments.
A consumption model ties revenue to how much of your product a customer actually uses. It is the umbrella term for any pricing where the bill varies with consumption. Usage-based pricing is one type. Credit-based pricing is another. Committed-spend contracts with overage charges are a third.
Snowflake is the canonical example. Customers buy compute credits upfront (committed spend), then consume them by running queries. If they use more than they committed, they pay overage rates. Revenue scales with data volume and query complexity, not headcount.
The advantage is natural expansion. As a customer's business grows, their consumption grows, and your revenue grows without a sales conversation. The disadvantage is volatility. If a customer's business contracts or they optimize their usage, your revenue drops.
Examples
A data platform sells compute credits.
Snowflake sells credits at roughly $2-3 per credit. A customer commits to $100,000 in annual credits. They use credits whenever they run queries. If they burn through credits faster than expected, they buy more. Revenue directly reflects the customer's analytical workload.
An AI company charges per token.
OpenAI charges per million tokens processed. A startup building an AI feature might spend $500/month in development, then $5,000/month in production as users grow. The bill scales linearly with the number of AI interactions their users have.
A CDN charges per request and bandwidth.
Cloudflare's Workers charge $0.50 per million requests plus $0.045 per GB-second of compute. A small site pays $5/month. A viral app during a traffic spike pays $5,000/month. Same product, price reflects actual consumption.
In practice
Read more on the blog
Frequently asked questions
How is a consumption model different from usage-based pricing?
Usage-based pricing is a type of consumption model. Consumption model is the broader category. It includes pure pay-as-you-go (usage-based), credit-based systems (buy credits upfront, consume over time), and hybrid models (base subscription plus consumption overage). Snowflake and Databricks use credit-based consumption models.
Can you have predictable revenue with a consumption model?
Yes, through committed contracts. Snowflake reports that most of its revenue comes from customers who committed to minimum annual spend. The commitment provides a revenue floor. Actual consumption almost always exceeds the commitment, creating upside. This gives investors the predictability they want.
Related terms
Charging customers based on how much they consume. Pay for what you use. The model behind Snowflake, Twilio, and AWS.
A virtual currency customers buy upfront and spend as they use your product. The bridge between subscriptions and pure usage-based pricing.
Tracking and measuring customer usage in real time for billing purposes. The plumbing that makes usage-based pricing work.
Charges that kick in when a customer exceeds their plan's included usage limits. The bill that surprises people.
A contract where the customer commits to paying for a full year, usually in exchange for a discount. Locks in revenue for the vendor.
Want the complete playbook?
Picks and Shovels is the definitive guide to developer marketing. Amazon #1 bestseller with practical strategies from 30 years of marketing to developers.