Design tiers with included usage and overage, test them against a realistic customer mix, and see revenue, margin and a sample invoice before you launch.
Requests, credits, tokens, minutes - anything you meter.
Monthly fee, usage included, and the rate for each extra 1,000 units.
Group your customers by how much they use. Each picks the cheapest plan for their usage.
Updates as you type.
| Segment | Best plan | Bill / customer | Revenue |
|---|
A model, not a forecast: it assumes each customer buys the cheapest plan for their usage and ignores discounts, taxes and churn.
Most successful AI and API products blend a predictable monthly fee with usage. Each tier includes a bucket of usage; anything beyond it is billed at an overage rate. Customers get a predictable bill, and you get paid when heavy users cost you more. Read the glossary entries for overage billing and credit-based pricing for more detail.
If you are unsure what your cost per unit is, start with the AI Pricing & Margin Calculator, then bring that number back here. Not sure whether to bill by tiers, credits or tokens? Compare the models first.
Start from your cost: the included usage on a tier should cost you well under the monthly price (the builder shows your margin per segment). Then space tiers so a typical customer in each segment lands in a different tier, which is what the “customer mix” section tests.
Overage is the rate charged for usage beyond the included amount. Set it above your cost per unit so extra usage is always profitable, and below the effective rate of the next tier’s base fee so heavy customers are nudged to upgrade rather than surprised by the bill.
It models a rational buyer who compares total monthly cost across tiers. If your tiers are well designed, customers sort themselves into the plan intended for them. If a tier is never picked, or a segment pays mostly overage, the warnings tell you to adjust.
Yes. Change the unit label to anything you bill on (credits, tokens, minutes, API calls, images) and enter your cost per 1,000 of that unit.
No. It runs entirely in your browser. The share link keeps your plan in the URL fragment, which is not sent to our servers.