Design SaaS tiers in this order: identify the customer value that grows with use, choose a pricing model that makes that value easy to see, group customers into a small number of plans, and then measure whether the plans move people up. If you keep rearranging plan boxes without settling on a structure, the problem is usually the order of decisions rather than the number of plans.
Start with the value metric, not the plan boxes
Stripe’s SaaS pricing guidance (updated April 7, 2026) sequences the work as value metric, pricing model, tier structure, then measurement. The value metric is the unit a customer pays for as their use or results grow. As Stripe puts it in its pricing and packaging strategy guide: “Your value metric is what customers pay for as they grow.”
As an Amazon Associate I earn from qualifying purchases.
Stripe lists four tests for a usable metric. It should grow with customer value, be understandable before purchase, resist gaming, and align with the budgets buyers already control. Candidate units vary by product:
- Users who collaborate in the product
- Records or items processed
- Data stored
- Workflows completed
- Another observable unit that tracks a successful customer outcome
These are examples of observable units, not a menu to choose from by convenience. A metric that is easy to count but does not track value produces plans that feel arbitrary to buyers, and it is hard to defend when a customer asks why their bill changed.
Choose a pricing model that fits the value pattern
Once the metric is clear, pick the model that makes it legible. Stripe distinguishes flat-rate tiers from per-seat, tiered-unit, and usage-based models in its Stripe Docs guide on recurring pricing models. The table below summarizes the trade-offs Stripe describes in its SaaS pricing guidance.
| Model | Fits when | Main risk |
|---|---|---|
| Tiered flat rate | Customer segments have substantially different needs | If tiers do not match real segments, some customers overpay while others get more than they pay for |
| Per seat | More users create more organizational value in a collaboration product | Can undercharge a small, high-intensity team if value does not scale with seats |
| Usage-based | Consumption tracks customer value, as with infrastructure, APIs, communications, or data products | Bills are less predictable; the metric should be one customers can understand and control |
| Hybrid base plus usage | The product has a baseline platform value plus variable consumption | More complex to explain and to bill |
| Single flat-rate plan | Buyer needs do not justify a complicated ladder | Gives up segment-specific packaging; Stripe’s guidance does not name a separate risk for this option |
Evaluate each option against the same questions: how well it aligns with value, whether customers can predict their bill, how easily the unit is explained, whether it fits buyer budgets, how exposed it is to gaming or avoidance, how predictable revenue will be, and whether it separates distinct segments. Competitor prices and your cost base are useful constraints, but they do not by themselves show what customers are willing to pay.
Rank #2
For context on adoption, Stripe’s SaaS pricing models guide (updated August 17, 2026) reports that 11% of SaaS companies took a value-based approach to pricing and 15% a usage-based approach. Those figures come from a 2025 survey attributed to Maxio and reported by Stripe in 2026, so they describe what Stripe reports about that survey, not the survey’s full methodology.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteBuild a small, legible tier ladder
Stripe recommends two to four tiers, with each plan representing a real customer type with real needs. Treat this as vendor guidance rather than a universal rule. Start with the fewest plans that express clearly different value, then check whether customers in each plan behave as you expected.
Name the customer each tier serves
Write one sentence for every tier that describes who it is for. If you cannot write that sentence without listing features, the tier probably does not represent a distinct customer need yet.
Identify the event that justifies moving up
For each step on the ladder, name the customer event that makes the upgrade sensible. Stripe’s examples include:
- Adding a team
- Needing collaboration across people or accounts
- Requiring governance controls
- Reaching a volume boundary
An upgrade trigger is something the customer’s own growth causes. Arbitrary feature withholding is different: it blocks a capability the customer needs to get the product’s core value. Keep the first and avoid the second.
Gate features and limits carefully
Reserve capabilities that match more demanding buyer needs for higher tiers. Stripe gives single sign-on, audit logs, and advanced permissions as examples. Avoid placing any feature essential to first realizing product value behind an upgrade gate. Limits should track the value metric and leave room for customers to reach meaningful value early. A capability that only a minority of customers need can be sold as an add-on instead of being built into every plan.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Make plans easy to compare
Show prices, included limits, overage terms, and plan differences side by side on one page. If usage is billed, state exactly what is counted and give customers a way to estimate their bill, such as a worked example for a hypothetical account. A customer who cannot predict the bill will read a usage plan as a risk, regardless of how fair the metric is.
Test the ladder and measure it
Stripe recommends researching customer needs, competitors, costs, and market position, then adjusting as the product and customer feedback change. Its guidance supports structured experimentation in general. It does not prescribe a specific test design or predict how much a change will lift revenue, so set expectations accordingly.
When you change a live pricing model, plan for how existing customers will be affected and how you will communicate the change. Those decisions depend on your contracts and customer base, so treat them as a planning step rather than a fixed migration procedure.
Metrics that show whether the ladder works
- Expansion monthly recurring revenue, to see whether existing customers grow into higher value over time
- Plan distribution, to see how customers spread across tiers
- Time from signup to upgrade, to see whether upgrade triggers fire at a sensible point
- Churn by plan, to see whether a specific tier loses customers at a higher rate
- Self-serve upgrade rate, meaning the share of upgrades completed without a sales call
Reading the signals
- If most customers sit on the lowest plan with little movement, upgrade triggers may be weak, or the higher plans may not match what customers need.
- If churn is disproportionately high on one plan, the plan may have a fit or value problem.
These patterns are diagnostic signals, not proof of cause. Use them to decide what to examine next.
Implementing the structure
If you implement the model in software, Stripe Billing supports recurring, tiered, hybrid, and usage-based pricing, according to Stripe’s pricing models guidance. Choose the model and tier structure first; the billing configuration should follow the decisions described above, not drive them.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
