Why this wireframe works | Usage-based pricing table
People see what they pay for what they use, so starting small is easy
Showing the base fee and the usage it includes first tells people what it costs to get started. Anyone who wants to begin with low usage can estimate the initial cost, and see on the same screen what it costs as usage grows.
With tiered unit prices, it shows how the price per unit falls with volume
When the unit price depends on usage, a table of tiers and unit prices shows which range each price applies to. If the price per unit falls as usage grows, how it falls at higher volumes is clear at a glance. For anyone expecting their usage to grow, that is material for thinking about the long-term cost.
Enter usage and the monthly estimate appears on the spot
With only a tier table, people have to work out calculations that cross tiers themselves. Because entering usage shows the monthly estimate, people can estimate the monthly bill for their own usage without asking.
The breakdown prevents misreading how unit prices apply
Usage-based pricing can apply each tier’s price only to the usage within that tier (graduated) or apply the reached tier’s price to all usage (volume), and the same table produces very different bills. Rather than relying on the name, the table shows the breakdown per tier, such as “9,000 × $0.02”, so people can see which price applied to which usage and check the bill.
On mobile the calculator comes first, with the tier table to check afterward
On mobile the monthly estimate calculator sits right under the base fee, with the tier table after it. People can check their own figure first and read on to the unit prices if they need to.
Common mistakes | Usage-based pricing table
Unit prices listed without saying which range they apply to
A list of tier prices alone does not say whether each applies only to usage within that tier or to all usage. People may estimate with the cheaper reading and be surprised by the actual bill. Explain how prices apply in words, with one worked example.
The usage included in the base fee is not stated
Without knowing how many items the base fee includes, nobody can work out what low usage costs. Write the included usage right beside the base fee.
No statement of when the bill is finalized
With usage-based billing, the figure seen mid-month differs from the actual bill. Write the closing date, the billing timing and how to check usage near the prices.
No explanation of what happens when usage spikes
Not knowing how high the bill can go if usage exceeds expectations is a reason to hesitate. If caps or alerts can be set, say how; if not, say how to check current usage.
Units that are not in the visitor’s language
Units like “requests” or “GB” alone leave some people unable to guess how much they use. Add an example of what the unit means, such as “1 item = 1 email sent”.
FAQ | Usage-based pricing table
How should I explain how tiered unit prices apply?
A worded explanation plus one worked example lands best. Showing the breakdown for a concrete usage, such as “for 25,000 items, 1,001–10,000 are charged at $0.02 and 10,001–25,000 at $0.015”, makes it less likely people assume the cheapest price applies to everything. If the base fee includes some usage, include that range too: “the base fee covers up to 1,000; for 25,000 items, the 9,000 from 1,001 to 10,000 are $0.02 and the 15,000 from 10,001 to 25,000 are $0.015”.
How do I help people who do not know their own usage?
One approach is to add usage guides by size or use case, such as “emailing 1,000 members twice a month is about 2,000 items a month”, so people can picture their usage from their situation. If the guide figures are not based on real data, say they are assumptions.
Should there be a cap on the monthly bill?
That is not decided by the pricing table alone, but an unpredictable bill is a common reason to hesitate, so if caps or alerts can be set, it is worth showing near the table. Even without that, show a way to check usage at any time.
How is this different from the price simulator?
The price simulator produces a rough cost from a combination of several conditions. This pattern handles pricing where the bill depends on one number, usage, and the actual bill is also finalized from usage.





























