iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Design tiered pricing in four steps: choose the value metric, pick a pricing model that makes that metric easy to understand, draw two to four plans around distinct customer types, then check whether the structure converts, expands and retains customers. Founders who feel they are going in circles usually try to draw plan boxes before settling the first two steps. Once the metric is fixed, the plan boundaries tend to follow.
Step 1: Choose the value metric before drawing plans
A value metric is the unit a customer pays for as their use of the product grows. Stripe puts it plainly in its guide to SaaS pricing and packaging: “Your value metric is what customers pay for as they grow” (Stripe, SaaS pricing and packaging strategy, last updated April 7, 2026). Stripe recommends working through four decisions in order: the value metric, the pricing model, the tier structure and the measurements you will track.
What a usable metric looks like
Stripe’s guidance lists four properties a good metric should have:
Recommended Free Tools
- It grows with customer value. Collaboration tools might count users, a data product might count records processed, and an infrastructure product might count requests or stored data. Pick the unit that rises when a customer gets more out of the product, not the unit that is simply easiest to count.
- The buyer can understand it before purchase. If a prospect cannot estimate their bill from the metric, the metric is working against conversion.
- It resists gaming. A metric that customers can reduce by working around the product, for example by sharing one login across a team, invites avoidance.
- It matches buyer budgets. The unit should map onto how the customer’s organisation already plans spending.
Costs and competitor prices are useful constraints, but they do not by themselves show what a customer is willing to pay. That question needs direct feedback from customers, which is covered in the testing step below.
Step 2: Match the pricing model to the value pattern
Once you know what grows with value, choose the model that bills for it. The table below summarises how Stripe describes the common options in its SaaS pricing guides and its Stripe Docs entry on recurring pricing models.
| Model | Fits when | Main risk | Bill predictability for the customer |
|---|---|---|---|
| Tiered flat rate | Segments have substantially different needs | If tiers do not match real segments, some customers overpay while others get more than they pay for | High within a plan |
| Per seat | More users create more organisational value, as in collaboration products | Can undercharge a small, high-intensity team if value does not scale with seats | High; the head count is visible |
| Usage-based | Consumption tracks value, as with infrastructure, APIs, communications or data products | Bills can be hard to predict; metrics should be ones customers understand and can control | Lower, because it depends on consumption |
| Hybrid base plus usage | There is a baseline platform value plus variable consumption | More complex to explain and to bill | Medium: a fixed base with variable charges |
| Single flat-rate subscription | Buyer needs do not justify a ladder | Can leave revenue on the table from larger customers | High |
Stripe reports, citing a 2025 survey attributed to Maxio, that 11% of SaaS companies took a value-based approach to pricing and 15% a usage-based approach (Stripe, SaaS pricing models 101, updated August 17, 2026). Those figures describe the market as a whole, not which model suits your product, and they are Stripe’s reporting of a survey it did not conduct.
Stripe’s guidance is explicit that no single model is universally correct. Model choice depends on product value, buyer segments, usage patterns and operating costs, and it should be revisited as those change.
Rank #2
Step 3: Build a small, legible tier ladder
Stripe recommends two to four tiers, each tied to a real customer type with real needs. This is vendor guidance rather than a rule, but it is a useful default. Start with the fewest plans that clearly express distinct value, then test them.
Write one sentence per tier
For each plan, write one sentence naming the customer it serves. If you cannot finish the sentence without listing features, the tier probably is not based on a distinct customer type. A typical ladder might read: the starter plan serves an individual or a two-person team validating the product; the team plan serves a group that needs shared workspaces; the business plan serves an organisation that needs governance controls.
Identify the upgrade trigger
For each step up the ladder, name the event that makes moving up sensible. Stripe’s examples include adding a team member, needing collaboration features, requiring governance controls and reaching a volume boundary. Upgrade triggers like these are tied to the customer’s situation. Restricting a feature the customer already needs to get value is a different thing, and it tends to produce frustration rather than upgrades.
Use feature gates and limits with care
- Gate enterprise needs at the top. Stripe’s examples are single sign-on, audit logs and advanced permissions. These correspond to demanding buyers, so they belong on higher plans.
- Do not gate first-value features. A capability that a new customer needs to reach meaningful value early should not sit behind an upgrade.
- Tie limits to the value metric. A limit should rise with the unit you chose in step 1 and leave room for customers to reach real value before they are asked to pay more.
- Use add-ons for niche needs. If a capability matters to only a minority of customers, sell it as an add-on rather than putting it in every plan.
Choosing between a single plan and a ladder
A single plan is simpler, and it is the right answer when buyer needs do not vary enough to justify several tiers. Adding tiers that do not correspond to distinct customers adds complexity without adding revenue clarity.
Step 4: Make the offer easy to compare and test it
Show prices, included limits, overage charges and the differences between plans on one comparison view. If usage is billed, tell customers what is counted and give them a way to estimate their charges before they subscribe.
Stripe recommends building the structure on research into customer needs, competitors, costs and market position, then adjusting continuously as the product and customer feedback change (Stripe, SaaS pricing models 101). Its guidance supports structured experimentation and iteration in general. It does not provide a specific experiment design or predict the lift any particular change will produce, so treat tests as ways to learn, not as guarantees.
Changing a live pricing model affects customers who already pay under the old structure. Plan communication and transition for existing customers before you change plan boundaries, rather than assuming a migration approach will carry over from another company.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Step 5: Measure whether the ladder works
Track five measures together rather than one at a time:
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →- Expansion monthly recurring revenue
- Distribution of customers across plans
- Time from signup to upgrade
- Churn by plan
- Share of upgrades completed without a sales call
Read them as a set. The patterns below are diagnostic signals, not proof of cause.
| Pattern | What it may indicate |
|---|---|
| Most customers sit on the lowest plan, and movement between plans is small | Upgrade triggers are weak, or the higher plans do not solve a problem customers have |
| Churn is disproportionately high on one plan | A fit or value problem on that plan, such as a tier that does not match its customers’ needs |
| Long time from signup to upgrade | Customers may not reach the value that makes the next tier worth paying for, or the trigger is not visible to them |
| Upgrades mostly need a sales call | Self-serve comparison may be unclear, or the plan boundaries may need explaining |
If the signals point to a problem, change one element at a time, starting with the upgrade trigger, and measure again before changing the model itself.
Implementation note
Once the model and tiers are settled, the billing system has to enforce them. Stripe Billing supports recurring, tiered, hybrid and usage-based pricing, so it can implement the structures described above. Choosing the model is still the harder decision; the billing tool only executes it.
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.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →
