Usage-Based Pricing

Usage-based pricing charges customers for what they actually consume, measured over a billing period and invoiced afterwards. API calls, compute hours, emails sent and gigabytes stored are common units. The customer pays nothing for capacity they do not use, and the bill grows as their usage grows.

Twilio bills per SMS segment and AWS bills per compute hour. A customer who sends 40,000 messages in March and 90,000 in April gets two very different invoices for the same product.

Potio’s take: Usage-based pricing is a tool, not a belief system. Potio implements it for many companies and actively steers others away from it. It aligns revenue with customer growth and makes the first purchase cheap, but it also brings volatility that plenty of businesses and buyers cannot absorb.

How this plays out

Four problems break usage models most often:

• Seasonality. Usage tied to retail campaigns spikes around Black Friday and Christmas and goes quiet in summer. Without the balance sheet to survive the dips, a pure usage model is dangerous.
• No user control. In larger companies the person using the product is not the person paying for it. Figma’s active editor billing let anyone grant edit access, and some bills jumped tenfold before Figma changed the model.
• Fixed budgets. Government tenders and many project-based buyers need a fixed total cost and will decline a usage model outright.
• Uneven value per unit. When one event is worth $1 to one customer and $1 million to another, no single unit price works. See pricing density.

Fundraising adds a fifth. Early-stage investors find unpredictable usage revenue harder to underwrite than seats. By the time a company reaches roughly $5M to $10M ARR, investors care about growth and net retention more than the model.

The common fix is a hybrid: a minimum commitment or platform fee secures the floor, and usage above it keeps the ceiling open. Guardrails such as caps, alerts and budget controls matter as much as the price.

Among venture-backed infrastructure companies, OpenView’s benchmarks put median net revenue retention at 125% for usage-based companies against 115% for subscription peers. Broader samples of mid-market software find the gap narrows, and usage revenue contracts faster in downturns.

Is usage-based pricing the same as consumption-based pricing?

Mostly, yes. Both bill on measured usage. “Consumption-based” is more common in infrastructure and data, and is often used for models where customers commit to a spend and draw it down.

When should you not use usage-based pricing?

When customers need a fixed budget, when usage is outside the buyer’s control, when your revenue would swing with the seasons and you cannot carry the dips, or when the value of a unit varies wildly between customers.

How do you move to usage-based pricing safely?

Track the usage metric in the background first, then model what current customers would have paid under the new system before announcing anything. Add guardrails such as spend caps and alerts before the first usage invoice goes out.

More on this: Usage Based Pricing for SaaS

Related terms

• Hybrid Pricing
• Credit-Based Pricing

Also called: UBP, pay-as-you-go, metered pricing, pay per use.

Updated 29 September 2026