Usage-Based Pricing

Fundamental Analysis
intermediate
6 min read
Updated Jan 1, 2025

What Is Usage-Based Pricing?

Usage-Based Pricing (UBP) is a business model where customers are charged based on their actual consumption or utilization of a product or service, rather than a fixed recurring fee.

Usage-Based Pricing, also known as consumption-based pricing or "pay-as-you-go," represents a paradigm shift away from traditional fixed-price subscriptions. In the old world of perpetual licenses, you bought software once and owned it forever. In the SaaS 1.0 world, you rented software for a flat fee (e.g., $50 per user per month) regardless of how much you used it. In the modern usage-based model, the customer pays strictly for a specific metric of consumption—gigabytes of storage, API calls, hours of compute time, or number of active contacts. This model has gained immense popularity with the rise of cloud infrastructure and data-heavy applications. Companies like Amazon Web Services (AWS), Snowflake, and Twilio have built massive businesses by charging customers only for what they use. This alignment of price and value is attractive to customers because it eliminates shelfware (paying for software that isn't used) and allows startups to access enterprise-grade tools with minimal upfront investment. It democratizes access to technology, allowing a two-person startup to use the same powerful tools as a Fortune 500 company, paying only for the tiny slice they consume. For the provider, UBP creates a powerful dynamic where revenue growth is not solely dependent on sales teams closing new deals. Instead, revenue grows organically as the customer's business grows. If a customer's app goes viral, their usage of the underlying infrastructure spikes, and the provider's revenue scales automatically. This is often referred to as "frictionless upsell."

Key Takeaways

  • Usage-based pricing aligns customer costs directly with the value they receive from the product.
  • It is commonly used by cloud computing providers (AWS, Azure), data platforms (Snowflake), and utility companies.
  • UBP allows for a lower barrier to entry, as customers can start small and scale up as their needs grow.
  • This model often leads to higher Net Revenue Retention (NRR) as successful customers naturally increase spending over time.
  • However, it introduces revenue unpredictability for the provider compared to fixed subscription models.
  • Investors valuing UBP companies focus on consumption trends and expansion revenue rather than just committed ARR.

How Usage-Based Pricing Works

Implementing a usage-based model requires defining a "value metric" that correlates perfectly with customer success. This metric must be easy to measure, track, and understand. Common examples include: - Compute: CPU hours or server instances (e.g., AWS EC2). - Storage: Terabytes of data stored (e.g., Google Cloud Storage). - Throughput: Number of API requests or messages sent (e.g., Twilio, Stripe). - Active Users: Monthly Active Users (MAU) instead of total seats (e.g., Slack's fair billing policy). The billing process involves complex metering technology that tracks usage in real-time. Customers are typically billed in one of two ways: 1. In Arrears: The customer uses the service for a month, and then receives a bill for exactly what they consumed (like a utility bill). 2. Pre-Paid Credits (Drawdown): The customer purchases a block of "credits" upfront (e.g., $50,000 worth). As they use the service, credits are deducted from their balance. This model is popular in enterprise sales because it guarantees revenue for the provider while giving flexibility to the customer. If the customer burns through their credits faster than expected, they simply top up. If they use less, the credits may roll over or expire depending on the contract terms.

Deep Dive: Land and Expand Strategy

The "Land and Expand" strategy is the holy grail of usage-based pricing. The "Land" phase is easy because the barrier to entry is low. A developer can often start using a UBP product with a credit card and zero interaction with a salesperson. They might start with a $50/month experiment. The "Expand" phase happens naturally. As that developer's project succeeds and moves from prototype to production, usage ramps up. The $50/month bill becomes $500, then $5,000, then $50,000. This expansion requires no new contracts, no renegotiations, and no sales calls. It is purely driven by the customer's utility. This contrasts sharply with seat-based models where expanding revenue means convincing the customer to buy more licenses for more employees, which creates friction. In UBP, the product essentially sells itself through its utility.

Hybrid Models and Committed Use

Pure pay-as-you-go models can be volatile. To mitigate this, many mature companies adopt a hybrid approach. They might charge a small platform fee (subscription) plus a variable usage fee. Alternatively, they offer "Committed Use Discounts." In this structure, a customer commits to spending a certain amount (e.g., $1 million/year) in exchange for a significantly lower per-unit price. This gives the provider revenue predictability (the "floor") while still allowing for "overage" revenue if the customer exceeds the commitment. It bridges the gap between the predictability of SaaS subscriptions and the upside of usage pricing. This is standard practice for large enterprise deals in cloud computing.

Revenue Recognition (ASC 606)

For investors, accounting for UBP is tricky. Under the accounting standard ASC 606, revenue recognition must match the delivery of value. - In a subscription model, if a customer pays $12,000 upfront for a year, the company recognizes $1,000 revenue each month (ratably). - In a usage model with pre-paid credits, the $12,000 cash is booked as "Deferred Revenue" (a liability) on the balance sheet. Revenue is only recognized *when the credits are consumed*. This means a company could have massive cash collections (bookings) but low recognized revenue if customers aren't using the product yet. Conversely, they could have high revenue but low cash flow if they bill in arrears. Investors must look at "Remaining Performance Obligations" (RPO) to see the backlog of contracted but unconsumed revenue.

Real-World Example: A Data Warehousing Startup

Consider a company using Snowflake for data analytics. - Month 1: The company loads 1 TB of data and runs a few queries. Bill: $200. - Month 6: The analytics team grows. They now store 50 TB of data and run complex daily reports. Bill: $5,000. - Year 2: The company launches a customer-facing app powered by Snowflake. Data volume hits 500 TB with constant queries. Bill: $40,000/month. The software provider didn't have to upsell the customer three times. The revenue grew 200x simply because the customer's usage grew. This organic compounding is why UBP companies often command higher valuation multiples.

1Step 1: Initial Usage. 1 TB storage + 10 Compute Credits = $200.
2Step 2: Growth Phase. 50 TB storage + 500 Compute Credits = $5,000.
3Step 3: Enterprise Scale. 500 TB storage + 5,000 Compute Credits = $40,000.
4Step 4: NRR Calculation. (Year 2 Revenue / Year 1 Revenue) from same cohort > 150%.
Result: The model captures the full value of the customer's success without sales friction.

Advantages for Investors

Companies with usage-based pricing often trade at a premium because they have "uncapped upside." In a subscription model, revenue is capped at the number of seats sold. In a usage model, a single customer like Netflix or Uber can generate tens of millions of dollars in revenue as their own business grows. This alignment means the provider grows *with* its customers, creating a highly sticky and scalable revenue stream that compounds over time.

Disadvantages and Risks

The flip side is unpredictability. In a recession, customers can cut usage instantly to save money (e.g., storing less data, running fewer reports). A usage-based company might see revenue drop 20% in a quarter if its clients slow down, whereas a subscription company would still collect the fixed fee until the contract expires. Forecasting revenue is much harder for CFOs and analysts, leading to potentially higher stock price volatility around earnings reports. Additionally, customers may experience "bill shock" if they accidentally leave a process running, leading to disputes and churn.

Metrics for Valuing UBP Companies

Key performance indicators (KPIs) unique to this model:

  • Net Revenue Retention (NRR): The percentage of recurring revenue retained from existing customers, including expansion. UBP companies often have NRR > 120%.
  • Consumption Rate: The speed at which customers use their pre-paid credits.
  • Remaining Performance Obligations (RPO): The value of contracted revenue that has not yet been recognized (future usage).
  • Payback Period: How long it takes to recover the cost of acquiring a customer (CAC). In UBP, this can be initially high but drops rapidly as usage scales.

FAQs

It depends on the product. For infrastructure and utility-like services (cloud, payments, APIs), usage-based is generally superior because value correlates perfectly with consumption. For productivity tools (like project management software), a subscription per user is often better because usage doesn't cost the provider much incrementally, and customers prefer predictable bills.

A usage commit is a contract where a customer agrees to spend a minimum amount (e.g., $50,000) over a period (e.g., 1 year) in exchange for a discount. If they use less, they still pay the $50,000. If they use more, they pay the "overage" at the agreed rate. This gives the provider a revenue floor.

Net Revenue Retention (NRR) measures how much a company's revenue would grow if it didn't add a single new customer. An NRR of 120% means the business grows 20% year-over-year just from existing customers spending more. Usage-based companies often have the highest NRR in the industry (sometimes 130%+), signaling incredibly efficient growth.

Technically, it can reduce churn because customers aren't locked into expensive contracts they don't use. They can scale down to near-zero cost without cancelling. However, it also means revenue "churning" (shrinkage) can happen faster than customer churn.

Shelfware refers to software that is purchased but never used—it "sits on the shelf." Traditional enterprise software contracts often resulted in massive amounts of shelfware. Usage-based pricing eliminates this waste, as customers only pay for what they actually use.

The Bottom Line

Usage-Based Pricing is revolutionizing how software and services are sold, moving the industry from "renting seats" to "paying for value." For investors, these companies represent a high-beta bet on the growth of the digital economy. While the model introduces revenue volatility and forecasting challenges, its ability to capture upside from successful customers makes it a potent driver of long-term value creation. As more industries adopt this model, understanding metrics like consumption rates, RPO, and NRR will become as important as understanding P/E ratios. The shift requires a new mindset for valuation, focusing on the potential of the customer base rather than just the current run rate.

At a Glance

Difficultyintermediate
Reading Time6 min

Key Takeaways

  • Usage-based pricing aligns customer costs directly with the value they receive from the product.
  • It is commonly used by cloud computing providers (AWS, Azure), data platforms (Snowflake), and utility companies.
  • UBP allows for a lower barrier to entry, as customers can start small and scale up as their needs grow.
  • This model often leads to higher Net Revenue Retention (NRR) as successful customers naturally increase spending over time.