What is Tiered Usage-based Pricing?

Tiered usage-based pricing charges customers per unit of consumption, with the per-unit rate changing as usage crosses predefined bands. The first block of usage is priced at one rate, the next block at a lower rate, and so on. It combines the metering of usage-based pricing with the band structure of tiered pricing.

This is the dominant structure for API products, data platforms, and communication services, anywhere consumption is measurable and marginal cost falls with scale.

How does the math work in usage-based pricing tiers?

The standard implementation is graduated: each unit is billed at the rate of the tier it falls into, not the rate of the highest tier reached.

An API product prices calls like this:

A customer making 6,000,000 calls in a month pays:

At a flat $1.00 per 1,000, the same customer would pay $6,000.

The graduated structure gives them an effective rate of $0.80, and the discount deepens as they grow. That's the commercial point: the customer's unit economics improve with scale, which removes their main argument for negotiating a custom deal or leaving.

Graduated, volume, or stairstep?

The same 3-tier table can be billed 3 different ways, and the invoice differs each time:

Volume pricing is more aggressive and creates boundary cliffs (crossing into tier 3 suddenly reprices all 6M calls). Stairstep pricing trades precision for predictability. Graduated is the middle path, and the most common.

For a full treatment of designing the bands, rates, and commitments around this model, see the guide to tiered usage-based pricing on the blog.

Why do companies choose tiered usage-based pricing?

For customers, it produces a predictable cost curve. They can model exactly what growth costs, and the effective rate only improves. For vendors, it captures revenue proportional to delivered value while building in the volume incentive that enterprise buyers expect anyway.

It also pairs naturally with commitments. Many contracts combine graduated tiers with a minimum commit: the customer commits to $50,000 a year, consumption draws down against it at graduated rates, and overage charges apply beyond it. At that point you're running a hybrid model, which is where most usage-based companies end up.

What does it demand from billing infrastructure?

Three things, and they're all harder than they look:

Companies that model tiers in spreadsheets or hand-rolled scripts tend to discover errors during their first enterprise audit, not before. Solvimon treats graduated, volume, and stairstep tiers as first-class price configurations on top of native metering. Flexible pricing covers the details.

FAQ

Is tiered usage-based pricing the same as graduated pricing?

Graduated pricing is the most common way to implement it. Tiered usage-based pricing is the model; graduated, volume, and stairstep are the billing methods.

How do free tiers fit in?

A free allowance is just tier 1 at a rate of $0. This is how most API products structure their free usage: first 10,000 calls free, graduated rates beyond.

What unit should the tiers be defined in?

The unit customers can predict and attribute value to. API calls, gigabytes, messages, tokens. If customers can't forecast the unit, they'll experience the model as random, whatever the rates are.

How does this apply to AI products?

Token-based models are usually tiered usage-based pricing with tokens as the unit. See AI token pricing for how model providers structure it.

Related

• The guide to tiered usage-based pricing: the full design walkthrough

• Usage-based pricing: the hub term

• Tiered pricing: the band structure without metering

• Stairstep pricing: flat fees per band