SAAS PAYMENTS
Tiered Pricing for SaaS: Examples and Billing Calculations
Anyway Team
· 8 min read ·
Tiered pricing divides an offer into price bands. For SaaS, it can describe fixed packages or usage-based rates. The crucial question is whether a new rate applies only to the units in its band or to every unit consumed. Those rules produce different bills.
That ambiguity can be expensive. In the example below, a customer who consumes 101 units pays less than a customer who consumes 100 under one pricing model. Under another, the bill rises by eight cents. Both could appear on a pricing page as “tiered pricing.”
Below, we'll calculate the same customer's bill three ways, check the price at each threshold, and turn the chosen formula into a rule your app can enforce.
Which kind of tiered pricing do you mean?
Model | What the customer buys | How the amount is calculated | Main design risk |
|---|---|---|---|
Package tiers | A named plan with defined features and allowances | The selected plan's fixed price | A small usage increase may require a much larger plan |
Graduated usage pricing | Units priced in successive bands | Add the charge for the units in each band | A vague pricing page can make customers expect a discount on all units |
Volume pricing | All units at the rate reached by total quantity | Total units multiplied by the applicable band rate | Crossing a threshold can reduce the total bill |
Payment platforms use these terms differently. Stripe's tiered-pricing documentation distinguishes graduated pricing from volume pricing by whether the new rate applies only to units in that band or to the entire quantity. Check the actual formula in your billing system rather than matching a menu label.
For a quick first choice: use packages to sell different feature sets, graduated rates when the bill should grow with consumption, and volume discounts when the all-unit discount is intentional. An allowance plus overage is another option, but it needs its own formula.
Tiered pricing examples: the same usage, different bills
Consider a fictional document-processing SaaS. The following prices are editorial examples, not Anyway pricing or a customer's results. A unit is one successfully processed document within a stated size limit. Taxes, payment fees, discounts, and mid-cycle changes are excluded.
For package pricing, suppose the plans are:
Starter: $29 per month, including up to 100 documents.
Growth: $59 per month, including up to 500 documents.
Scale: $99 per month, including up to 1,500 documents.
Above 1,500 documents: a separate agreement; no automatic unlimited allowance.
For both usage-pricing alternatives, use these rates:
Band | Rate per document |
|---|---|
Documents 1–100 | $0.10 |
Documents 101–500 | $0.08 |
Documents 501 onward | $0.06 |
Now compare the results. The package column shows the lowest listed plan that covers the quantity; it does not imply that the system may upgrade a customer without their agreement. At zero usage, it assumes an active paid Starter subscription.
Monthly documents | Package price | Graduated charge | Volume charge |
|---|---|---|---|
0 | $29.00 | $0.00 | $0.00 |
100 | $29.00 | $10.00 | $10.00 |
101 | $59.00 | $10.08 | $8.08 |
250 | $59.00 | $22.00 | $20.00 |
500 | $59.00 | $42.00 | $40.00 |
501 | $99.00 | $42.06 | $30.06 |
The alternatives deliberately don't produce the same revenue. They show different offers, not equivalent prices with different labels. Package plans may also include features and support that the usage-only offer doesn't contain.
Calculate graduated pricing one band at a time
At 250 documents, the first 100 cost $10. The remaining 150 cost $12. The total is $22.
For a nonnegative whole-number quantity q, this example is:
The second band contains 400 documents, not 500. It starts after the first 100 have already been counted. That is an easy boundary mistake to miss in a spreadsheet or implementation.
Calculate volume pricing using one rate
At 250 documents, every document uses the $0.08 rate. The total is $20.
At 501 documents, every document uses the $0.06 rate. The total falls to $30.06 from $40 at 500 documents. An extra document reduces the charge by $9.94.
That behavior may be intentional for a negotiated volume commitment. For an automatically measured self-serve product, it deserves a deliberate decision. Customers should not have to discover that generating one unnecessary document lowers their invoice.
Tiered pricing vs volume pricing: check the boundaries first
Graduated pricing applies each band's rate only to the units inside it. Volume pricing applies the reached rate to every unit. For a self-serve usage offer, graduated pricing is often easier to explain when you want the total bill to increase as consumption grows. Volume discounts need extra attention at the thresholds.
Test at least these quantities before publishing: zero, one, 99, 100, 101, 499, 500, and 501. Also test a corrected usage record that moves a customer back across a threshold.
For each result, ask:
Can a customer reproduce the amount from the pricing page?
Does a larger quantity produce a smaller bill? If so, is that intentional?
Does every allowed band cover its expected delivery cost?
Do the checkout, usage dashboard, and invoice describe the same rule?
If you want an allowance plus overage, write that formula separately. For example, “$29 includes 100 documents; each additional document costs $0.08” gives a $41 bill at 250 documents. It is neither the $22 graduated example nor the $20 volume example above.
Choose plan boundaries around a customer's next useful step
A package upgrade needs a reason the customer understands. More seats, a larger document allowance, or access to a collaboration feature can provide one. An arbitrary limit that interrupts a small task feels different.
In the package example, moving from 100 to 101 documents requires a $30 increase if Growth is the only available option. That might be reasonable if Growth adds valuable team features. It may be a poor fit if the buyer only needs one additional document.
Possible responses include a small top-up, a clearly priced overage, or a different allowance. Don't silently change the customer to Growth. State the choice before the extra work begins.
Use support questions and observed usage to revise those boundaries after launch. Until you have that evidence, treat your first plan structure as a testable offer, not a discovered law about your customers.
For the separate decision about collecting payment before or after consumption, see AI credits vs usage-based billing.
Check the cheapest band against delivery cost
Suppose the fictional product costs $0.07 to deliver each document. At 501 documents, variable delivery cost is $35.07. The graduated charge leaves $6.99 before payment fees, support, refunds, and fixed costs. The volume charge loses $5.01 before those costs.
This is a boundary calculation, not a claim about a normal SaaS margin. Your own unit cost may vary with document size or processing requirements. If one unit can represent radically different workloads, define the unit more tightly before trusting the table.
Don't assume a high average margin makes every tier safe. A rate below marginal delivery cost can lose more money as a customer becomes more active. The existing AI SaaS unit-economics guide covers that broader cost analysis; here, the useful test is whether each published band can survive its own allowed workload.
Turn the price into a billing rule your app can enforce
Keep a versioned pricing record. It should identify the unit, boundaries, rates, currency, billing interval, and effective date. Preserve the version used for each invoice so a price change doesn't rewrite the explanation of a previous charge.
Then decide which system owns each job:
Job | Required output |
|---|---|
Product usage measurement | The accepted quantity, with duplicate and failed work handled consistently |
Price calculation | An amount reproducible from quantity and price version |
Payment collection | A confirmed transaction associated with the purchase |
Product access | The features or allowance the customer is entitled to use |
For a fixed Starter or Growth plan, Anyway's hosted payment links let you create the offer and share a checkout link without building the checkout interface yourself. Your app still needs to connect the purchased plan to its allowance. Usage measurement and the graduated calculation above require application logic or a billing engine that explicitly supports them; a payment link alone does not do that work.
After purchase, connect the confirmed order to the correct plan. The SaaS payment webhook guide covers verification and duplicate delivery handling. Avoid granting a plan solely because the browser returned to a success page.
Questions to settle before publishing your pricing page
Is tiered pricing the same as volume pricing?
Sometimes “tiered” is used as an umbrella term that includes volume discounts. For implementation, always spell out the calculation. “Each band is priced separately” and “all units use the rate of the final band” produce different bills.
How many SaaS pricing tiers should you have?
Use as many as you can explain through genuinely different needs. There is no required number. Two understandable plans can be more useful than four plans separated by small, arbitrary restrictions.
Should unused allowance roll over?
Only promise rollover if your entitlement records can preserve it and your economics allow it. State which allowance expires first and what happens after cancellation. Rollover changes the obligation you carry into future periods.
Can I change tiers for existing subscribers?
Define how a new price version applies to existing subscriptions, check the applicable contract and notification requirements, and test the transition. Don't overwrite a price and assume every customer's next charge should change automatically.
Publish the formula before polishing the plan names
Start with the boundary table. If a teammate cannot explain the amount at 101 units, the customer won't have a fair chance either.
If your first release uses fixed plans, Anyway Business gives you a hosted-checkout route to evaluate. Start with one paid plan and verify that a completed purchase unlocks the right allowance. Add overage or usage bands when you can explain the resulting bill just as clearly.