Source: https://www.revvly.ai/blog/tiered-pricing-model-how-to-design-saas-tiers Pricing 8 min read Jul 14, 2026 # Tiered pricing model: how to design SaaS *tiers*. A pricing page built for a five-person startup is still gating the same features two years and three product launches later. Nobody notices the *ceiling* on expansion revenue until growth stalls. AR Alain Readman Co-founder, Revvly Most SaaS companies don't have a pricing problem because they picked the wrong number of tiers. They have one because nobody revisited the tiers after the product moved on. A pricing page built for a five-person startup is still gating the same features two years and three product launches later, and the result is a ceiling on expansion revenue that nobody notices until growth stalls. ## Quick answer > A tiered pricing model charges customers different amounts based on which package of features, usage limits, or seats they buy, usually across three packages: a starter tier, a core tier built around your best-fit customer, and a top tier for accounts that need more scale, support, or control. Most SaaS companies do best with three tiers, gate them by the value driver that tracks how the product is actually used (features, seats, or usage), and layer a usage-based or add-on component on top rather than adding a fourth or fifth flat tier. ## What tiered pricing is and why it matters now Tiered pricing means offering a small number of fixed packages, each bundling a set of features, limits, or seats at a fixed price. It's the most common SaaS pricing structure because it lets a buyer self-select into the right plan without a sales conversation, while still letting you charge more to accounts that get more value. The reason this matters more in 2026 than it did a few years ago is that pricing itself has become a growth lever, not a back-office decision. In Kyle Poyar's 2026 State of B2B Monetization survey of more than 230 SaaS and AI companies, the single most commonly cited monetization challenge, across company sizes, was not enough expansion revenue. Three in four of the companies surveyed had changed their pricing or packaging in the past year. A tier structure that was fine at launch is frequently the reason expansion has stalled: if every meaningful feature is already in the tier a customer bought on day one, there's nothing left to sell them as they grow. 37% Share of companies running a hybrid pricing model (tiers plus usage-based consumption), up from 25% a year earlier, per Kyle Poyar's 2026 State of B2B Monetization survey. Tiering also isn't the only lever anymore. The same survey found that 37% of respondents now run a hybrid pricing model, combining tiers with a usage-based or consumption component, up from 25% a year earlier. For [usage-based pricing](https://www.revvly.ai/blog/usage-based-pricing) in particular, tiers and consumption pricing aren't competing approaches, they're complementary: the tier sets the floor and the ceiling, and usage-based billing captures the value in between. ## How to design a tiered pricing model that actually holds up ### Anchor the middle tier to your best-fit customer, not your cheapest one Design the middle tier first, not the entry tier. The middle tier should map to the customer profile you actually want more of, meaning the features in it should reflect what that customer needs to get full value from the product, not a discount version of the top tier. The entry tier exists to get self-serve signups in the door; the top tier exists to capture accounts that outgrow the middle one. If you design bottom-up, you tend to end up with a middle tier that's just "entry plus a few extras," which caps how much a growing account is willing to pay to move up. ### Decide how many tiers you actually need Three tiers is the right starting point for most SaaS products, sometimes four if the customer base genuinely splits into distinct buyer types (for example, individual users, teams, and enterprise accounts with procurement requirements). Each additional tier past four adds a decision a prospective buyer has to make before they can start using the product, and each one is also a plan your team has to maintain, document, and reason about when someone asks a support question. If a fifth "tier" is really just the fourth tier with a different usage cap, that's a signal to make it a usage-based add-on instead of a separate flat plan. ### Choose what gates each tier deliberately Every tier needs a clear value metric that decides who's in it: seats, a specific high-value feature set, a usage ceiling, or some combination. The test for a good gate is whether a customer can explain in one sentence why they'd need to upgrade. "You'll need Team because you have more than 5 users" is a clear gate. "Team gets 'advanced reporting,'" with no explanation of what that means for the buyer's job, isn't. Gate on the thing that scales with the customer's business, not on a feature you'd like more people to pay for. ### Add a hybrid layer instead of a fourth flat tier If you're tempted to add a plan because a small number of accounts use the product far more than everyone else in their tier, that's usually a sign you need a usage-based or overage component, not another flat plan. This is exactly the shift the market is making: hybrid pricing, tiers plus consumption, was the single most common pricing structure in the 2026 State of B2B Monetization data, ahead of pure flat-fee or pure usage-based models. A tier sets the baseline price and the expectations for a customer profile; a usage component on top captures the accounts that outgrow the baseline without forcing them into a whole new plan. ### Plan the migration before you announce a change Existing customers should never be surprised by a pricing change they read about on your changelog. The lowest-friction approach is to grandfather existing customers into their current plan and terms for a defined window (commonly 6-12 months), giving them time to see the new tiers' value before any change hits their invoice, rather than forcing an immediate switch. This is also the point where [pricing experiments](https://www.revvly.ai/blog/pricing-experiment) matter: test the new structure with new signups first, and only migrate existing accounts once you've seen how the market responds. ### Instrument the boundaries between tiers Once tiers are live, the accounts worth watching are the ones sitting right at a tier's usage or seat ceiling. An account that's been bumping against its limit for two months is either about to upgrade or about to feel nickel-and-dimed and start looking at alternatives, and those two outcomes look different in the data well before either one happens. This is where AI-powered churn prediction earns its keep: flagging accounts near a tier boundary that show usage or engagement patterns associated with churn, rather than accounts that show patterns associated with expansion, so customer success can reach out with the right message before the renewal date, not after. ## What this looks like in practice A project management tool with a broad user base typically tiers by seats and a small number of collaboration features, since more people using the product is a clean, easy-to-explain reason to pay more. A developer-facing API product more often tiers by a base plan plus metered usage, since the value a customer gets scales with calls or data processed, not headcount. A finance or ops tool serving both small teams and larger companies usually needs a third, enterprise-facing tier gated on things a small team doesn't need yet: SSO, custom roles, or a dedicated account manager, rather than more of the core feature set. The common thread across all three: the gate matches how value actually scales for that specific product, and the tiers stay few enough that a prospective buyer can pick one without calling sales. ## Tiered pricing design checklist | Question | What a "yes" looks like | | --- | --- | | Does each tier have a value metric a customer could state back to you? | "I need Team because we have 12 users," not "Team has more stuff" | | Is the middle tier designed around your best-fit customer? | Middle tier features map to what that customer actually needs, not a discounted top tier | | Do you have 3-4 tiers, not 5+? | Anything that would be a 5th tier is a usage-based add-on or overage instead | | Is there a usage or hybrid layer for high-usage accounts? | Power users pay more through usage, not through a bespoke plan | | Do existing customers get a grandfathering window before any pricing change? | A defined transition period, not an immediate forced switch | | Are tier-boundary accounts tracked as a distinct signal? | Accounts near a seat or usage ceiling are flagged separately from general churn risk | ## Why tiered pricing breaks down in spreadsheets and generic billing tools Tiers, usage-based add-ons, proration for mid-cycle upgrades, and regional pricing variants are each individually simple. Running all of them at once, by hand, in a spreadsheet next to a Stripe account and a CRM, is where most RevOps teams lose the thread: a customer upgrades mid-cycle, the proration has to be calculated and applied correctly, the CRM has to reflect the new plan, and the revenue dashboard has to catch up, often across three disconnected systems that don't talk to each other. Revvly's modular pricing architecture is built to run tiered, usage-based, and bundle pricing from one system, with automated proration for mid-cycle plan changes and [NRR tracking](https://www.revvly.ai/blog/nrr-compounds) that reflects tier upgrades and expansion in real time rather than at the end of the month. Revvly's [plans](https://www.revvly.ai/pricing) start at $29/mo, with pricing scaling by the modules a company actually uses, a detail worth understanding before assuming a startup-first billing platform can't also structure enterprise-grade tiers; the [pricing models guide](https://www.revvly.ai/docs/guides/pricing-models) covers how modular tiers are configured in more depth. ## Frequently asked questions ### How many pricing tiers should a SaaS company have? Three tiers is the right default for most SaaS products: an entry tier, a middle tier built around your best-fit customer, and a top tier for larger or more complex accounts. A fourth, enterprise-only tier makes sense when procurement, security, or support requirements genuinely differ from the rest of the customer base. Beyond four, consider a usage-based add-on instead of another flat plan. ### What's the difference between tiered pricing and usage-based pricing? Tiered pricing charges a fixed amount for a fixed package of features, seats, or limits. Usage-based pricing charges based on actual consumption, like API calls, seats used, or data processed. Most SaaS companies today combine the two: a tier sets the baseline, and usage-based billing captures value from customers whose consumption exceeds that baseline. ### Should you gate tiers by feature, by seats, or by usage? Gate by whichever value metric scales the same way your customer's business scales. A collaboration tool usually gates by seats because more users is a clear sign of more value delivered. A developer or API product usually gates by usage because calls or data volume track value better than headcount. The wrong gate is one a customer can't explain in a sentence. ### Will changing our pricing tiers churn existing customers? It can, if the change is announced without warning or applied retroactively. Grandfathering existing customers into their current terms for a defined transition window, and testing the new structure with new signups first, meaningfully lowers that risk. The riskiest move is an immediate, unannounced switch on an existing customer's next invoice. ### Can Stripe alone handle tiered plus usage-based pricing? Stripe Billing can meter usage and apply tiered prices, but combining tiers, usage overages, proration for mid-cycle changes, and regional variants in one coherent structure typically requires either significant custom engineering on top of Stripe or a subscription platform built to handle all of those pricing types together. ### What is a good example of hybrid pricing? A common hybrid pattern is a flat per-seat tier that includes a set usage allowance, with metered overage billing once an account exceeds that allowance. This gives customers price predictability at the low end while letting the vendor capture more revenue from the heaviest users without needing a separate enterprise negotiation for every high-usage account. ### How do I know if my current tiers are holding back expansion revenue? Look at how often accounts sit at their tier's ceiling (seats, usage, or a specific feature limit) without upgrading. If a meaningful share of accounts have been at the ceiling for more than a billing cycle or two without moving up, either the next tier isn't compelling enough or there's no smaller step, like a usage add-on, between at-the-limit and buy-the-next-full-tier. AR Alain Readman Co-founder, Revvly Alain spent a decade building and scaling subscription businesses before founding Revvly. He writes about the infrastructure gap between what SaaS companies report and what they actually earn. Revvly Orchestrate the flow of revenue. © 2026 AcceleratorApp Limited. All rights reserved.