How do you package SaaS pricing tiers?

Most SaaS pricing pages fail not because the price is wrong but because the tiers are structured in a way that creates confusion rather than guiding a decision. The goal of packaging is to make one plan feel obviously right for your target buyer while using the others as anchors and upsell levers. Get the structure right first, then worry about the numbers.

Start with buyer segments, not feature lists

The most common mistake founders make is organizing tiers around features they happen to have built rather than around the distinct types of buyers they are trying to serve. Before you write a single line of your pricing page, list the two or three meaningfully different customer profiles who buy from you. A solo consultant, a ten-person agency, and an enterprise procurement team have different value drivers, different approval processes, and different price sensitivities. Each tier should map cleanly to one of those profiles — not to a bucket of features.

Once you have your buyer segments, identify the one metric that scales most naturally with the value each segment gets from your product. This is your packaging axis. For a project-management tool it might be seats. For a data pipeline tool it might be rows processed. For a communication tool it might be message volume. Tying tier limits to a value metric means customers upgrade naturally as they grow, rather than hitting an arbitrary feature wall that feels punitive.

If you cannot articulate in a single sentence why a buyer in segment A should be on tier 1 and a buyer in segment B should be on tier 2, your tier structure is not ready. Keep simplifying until that sentence is obvious. Pricing clarity is a product decision, not a marketing one.

Use three tiers, anchor to the middle

Three tiers is the right number for most early-stage SaaS businesses. Fewer than three and you lose the anchoring effect that makes any plan feel like good value. More than three and you introduce decision paralysis — buyers stall, email support, and sometimes leave without subscribing at all.

The middle tier should be your primary revenue target. It should be priced and labeled so it looks like the sensible, grown-up choice for a buyer who is serious but not a large enterprise. The lowest tier exists mainly as a downgrade safety net and acquisition channel — it keeps price-sensitive buyers in your ecosystem rather than losing them entirely. The highest tier exists to make the middle tier feel affordable by comparison and to capture the surplus value from your most demanding customers.

The mechanics of anchoring matter here. Rik Haandrikman's work on paywall design notes that presenting packages side by side with one visually distinguished option uses "classic price anchoring to make the [target plan] the obvious choice." Apply the same logic to your pricing page: use a visual badge, a label like "Most Popular" or "Best for Growing Teams," and slightly more prominent styling on your target tier. Buyers who are uncertain — which is most buyers — will gravititate toward the option that someone else has already validated.

Decide what to gate and what to include everywhere

Feature gating is where founders overthink themselves into a bad outcome. The temptation is to hold back desirable features to force upgrades, but this usually just makes lower tiers feel broken rather than intentionally limited. A better mental model: features that enable the core job to be done should be available on all tiers. Features that make the core job faster, safer, or more scalable for larger teams are what justify upgrades.

A practical heuristic: if withholding a feature causes a user to fail at the basic task your product promises to solve, put it in all tiers. If withholding it means the user succeeds but with more manual effort or lower confidence, that is a legitimate upgrade gate. Examples of good gates include advanced analytics, team permissions and audit logs, API access, priority support, and higher usage limits. Examples of bad gates include the ability to export your own data, basic integrations with common tools, and anything that creates a trust or reliability gap.

Also think carefully about what is free on tier one. If your product has a strong network effect or word-of-mouth component, being generous on the lowest tier accelerates organic distribution. If it does not, a stingy free tier may be more appropriate. There is no universal answer, but you should be deliberate rather than letting the free tier happen by default.

Price the tiers relative to each other, not just to cost

Many founders set prices by calculating their cost of goods sold and adding a margin. This produces prices that feel arbitrary to buyers. Instead, price each tier relative to the value delivered at that tier and relative to the other tiers in your stack.

A common and defensible structure is roughly a 3x to 5x price step between tiers. If your starter tier is $29/month, your growth tier might be $99 and your professional tier $299. This spacing is large enough that the upgrade feels meaningful but not so large that it triggers a different budget approval process. When the gap is too small — say $29 to $49 to $79 — buyers feel the tiers are arbitrary and the cheapest one always wins. When it is too large, you create a cliff that stalls upgrades.

Also consider annual versus monthly pricing from the start. Offering an annual option with a roughly 20% discount on every tier accomplishes two things: it improves your cash flow immediately and it signals to buyers that you intend to be around long-term. For early-stage companies, pushing annual aggressively is often more financially impactful than optimizing the monthly price by a few dollars.

Test conversion, not just signup rate

Once your tiers are live, the metric that matters is not page visits or even trial starts — it is the distribution of paid conversions across tiers. If 90% of paid customers land on your lowest tier, your higher tiers are either priced wrong, packaged wrong, or both. If almost no one takes your lowest tier, you may be leaving acquisition-channel value on the table or your lowest tier may be genuinely useless.

Healthy SaaS businesses typically see their middle tier capture 50-70% of new paid customers by count and their highest tier contribute disproportionately to revenue. If your numbers look very different, treat it as a signal to investigate rather than a benchmark to chase blindly — different product categories vary — but it is a useful starting hypothesis.

Do not wait for statistical significance on large samples before iterating. At early stage, qualitative data is faster and often more useful. Talk to five customers on each tier. Ask them directly: what almost made you choose a different plan? What would have made you upgrade? Their answers will tell you more about your packaging than a month of A/B test data. Use those conversations to tighten the value narrative on each tier before you touch the price numbers.

“Classic price anchoring makes the annual plan with the trial the obvious choice.”

— Rik Haandrikman, source

The one thing to do

Map each tier to a specific buyer segment and a value-metric limit, then run five customer interviews per tier to validate that the packaging matches how buyers actually perceive the value step.

Frequently asked questions

Should I offer a free tier or a free trial?

A free trial is usually better for B2B SaaS because it creates a deadline that drives conversion. A free tier makes sense if your product has strong network effects or if getting users into the product drives organic referrals. Pick one and commit — offering both usually dilutes urgency without meaningfully expanding reach.

How many features should separate each tier?

The gap does not need to be large in feature count — it needs to feel large in value. One or two genuinely high-demand features plus a meaningful usage limit increase is enough to justify a 3x price step. More features do not automatically mean more perceived value.

When should I add a fourth enterprise tier?

Add an enterprise tier when you have enough inbound from buyers who need custom contracts, SSO, SLAs, or security reviews that you cannot fulfill under your standard terms. Do not add it speculatively — it adds sales complexity before you have the process to handle it.

How often should I reprice my tiers?

Revisit pricing every 12 months at minimum, or whenever your conversion data suggests a structural problem. Most early-stage SaaS companies underprice initially and raise prices as they accumulate proof of value. Grandfather existing customers when you raise prices — it costs you little and builds significant goodwill.

Sources

More playbook answers · Growth Prophet home