# Usage-based pricing: definition, billing formula and a real example

Source: https://leverprice.com/glossary/usage-based-pricing
Updated: 2026-11-17

> Usage-based pricing charges customers for what they consume, such as API requests, tokens, gigabytes or minutes, instead of a flat fee. A common design is a base fee that includes an allowance, then a unit price for usage above it. Revenue grows with customer usage, but monthly bills become harder for customers to predict.

Usage-based pricing means the bill follows consumption. Cloudflare Workers is a clean example: the paid plan costs $5 a month, includes 10 million requests and then charges $0.30 per additional million, as of November 2026 ([Cloudflare](https://developers.cloudflare.com/workers/platform/pricing/)).

## How it works

```text
bill = base fee + max(0, usage - included) × unit price
```

A Worker that serves 25 million requests in a month pays $5 + (25 - 10) × $0.30 = $9.50 for requests. CPU time is metered separately, with 30 million CPU milliseconds included in the same plan.

Designing usage pricing comes down to four choices:

- The value metric, meaning the unit you charge for. It should grow with the value the customer gets and be easy for them to predict.
- The allowance included in the base fee.
- The unit price, and whether it falls in steps as volume grows.
- Guardrails such as spending caps, usage alerts or prepaid credits.

The cost side matters as soon as each unit costs you real money, as model tokens do: gross margin per unit = unit price - unit cost, and it has to stay positive at every volume step.

## Why it matters for pricing

Usage pricing has several prices to set at once: the base fee, the allowance and the unit price. Cutting the allowance from 10 million to 5 million requests is a price increase even though the headline price stays the same.

It also complicates testing. The first payment often covers only the base fee, while usage revenue arrives in later invoices, so a test that scores only the first payment sees none of the usage. Check later invoices before you call a winner. [Pricing AI apps with credits](https://leverprice.com/blog/ai-app-pricing-credits) deals with the same problem using prepaid units.

## Common mistakes

- A unit customers cannot predict, which makes them hold back usage to control the bill.
- No spending cap or alert, which leaves customers to discover heavy usage on the invoice.
- Volume discounts that push the unit price below your unit cost.
- Comparing your price with a competitor's while ignoring the allowance.

## Related terms

[Tiered pricing](https://leverprice.com/glossary/tiered-pricing) explains how unit prices step down with volume, and [seat-based pricing](https://leverprice.com/glossary/seat-based-pricing) is the main alternative for team products. [Cost-plus pricing](https://leverprice.com/glossary/cost-plus-pricing) sets the floor for each unit, and [ARPU](https://leverprice.com/glossary/arpu) shows whether usage growth is turning into revenue.

## Frequently asked questions

### What is the difference between usage-based pricing and a subscription?

A subscription charges a fixed amount per period. Usage-based pricing charges per unit consumed, often on top of a smaller subscription that includes an allowance.

### What is a value metric?

The unit you charge for, such as requests, messages or active users. A good one grows as the customer gets more value, so your revenue grows with their success.

### Is usage-based pricing a good fit for an early-stage product?

It suits products whose usage varies widely between customers. If most customers use about the same amount, a flat plan is simpler for you and for them.
