How to Set Up Pricing Tiers

Pricing-tier design is one of the few places in a business where small design decisions have large revenue consequences. The same underlying product, priced as three tiers vs. five, or priced per-seat vs. flat-fee, can differ by 30–50% in realised ARR per customer. This is not cosmetic — the tier structure determines how your customers grow with you.

1. Pick a value metric that scales

The value metric is the unit that ties price to customer success. Good value metrics share three properties:

• They scale with customer success. As the customer gets more value, the metric grows. Seats for collaboration tools, API calls for developer tools, transactions processed for payment tools, revenue managed for accounting tools.
• They are easy to measure. Both sides can see and agree on the number without ambiguity.
• They don't penalise usage. A metric that causes customers to restrict their use of the product (e.g., "every notification sent") is worse than a metric aligned with product value.

Flat-fee pricing works for narrow products where the customer's value does not grow much with use (e.g., single-use utilities). For SaaS with expansion potential, a value metric is almost always correct^[1].

Common mistakes: pricing per-seat when usage is primarily asynchronous (penalises organizations that invite broader participation); pricing per-feature in a way that forces artificial unbundling of naturally-grouped capabilities; pricing on metrics customers can't predict, which drives unpredictable invoices and churn.

2. Three tiers, not five

The standard structure: Starter, Growth (or Pro), Enterprise. Three tiers, mapped to three customer segments.

Why three:

• Decision-making theory: more options reduce conversion, especially on high-consideration purchases^[2].
• Three is enough to cover the natural segments (solo/small, growth, enterprise) without creating competition between adjacent tiers.
• With three tiers, the middle tier becomes the anchor for decision-making — most customers who upgrade from Starter go to Growth, not Enterprise.

Five-tier structures are usually a sign of indecision — a company that couldn't commit to three clear customer segments. The result is that customers within a tier are heterogeneous, which complicates everything downstream (packaging, support, sales motion).

Legitimate exceptions: genuinely complex products (data platforms with very different use cases at scale) and regulated industries (where compliance tiers add real cost). Even then, four is usually enough.

3. Anchor high, price the middle

Price anchoring is the most robust finding in behavioral pricing research^[3]. The first price a customer sees meaningfully changes their perception of subsequent prices, even when they explicitly know the effect exists.

Practical implications for tier design:

• Show the premium tier first visually. Order tiers highest-price to lowest-price when the page is scanned, even if the buyer's likely choice is the middle tier.
• Make the middle tier obviously better value than the bottom tier. Bottom tier should feel too restrictive for anyone with real needs. Middle tier should feel like what most legitimate users will need. Top tier should contain enterprise features that occasional buyers genuinely need.
• The 3:1 ratio. A common pattern: bottom $X, middle ~$3X, top ~$10X. Not a rule, but a starting point that creates clear separation.

Willingness-to-pay research (Van Westendorp PSM or similar) can inform price points^[4]. In the typical case, the prices founders set by gut feel end up 20–40% below actual willingness-to-pay.

4. Build clear upgrade triggers

Expansion revenue comes from customers crossing tier boundaries. Every tier boundary should have an obvious trigger — a limit or feature the customer hits that forces the upgrade conversation.

Good upgrade triggers:

• Usage-based limits. "Starter includes up to X seats / API calls / projects." When customer exceeds, they see a clear upgrade path with pricing attached.
• Feature gates tied to customer maturity. Advanced analytics, integrations, SSO, audit logs. Features that genuinely matter to larger/more sophisticated users, gated at the tier those users occupy.
• Support-level tiers. Response-time SLAs, dedicated account management. These are real value for enterprise, useful for mid-market, and largely irrelevant for individual users.

Bad upgrade triggers: arbitrary feature gates that just feel punitive, essential functionality gated behind paywalls (hurts adoption more than it earns), and gates that force customers to contact sales for pricing visibility (mid-market customers often walk away rather than engage).

Communicate upgrades proactively. In-product notifications when a customer approaches a tier limit, with the specific next tier's price visible, convert at materially higher rates than waiting for customers to hit the wall.

Review tier structure annually. As the customer base matures and the product evolves, what was the right tier structure two years ago rarely still is. Roughly, the businesses that revisit packaging annually grow ARPU 20–30% faster than those that set-and-forget^[1]. Packaging is a lever worth pulling deliberately.

5. Grandfathering existing customers

When you change pricing or tier structure, existing customers need a separate policy. Three common approaches:

• Full grandfather: Existing customers stay on old pricing indefinitely. Protects renewal rates but creates operational complexity and a permanent revenue gap between cohorts.
• Grandfather with sunset: Existing pricing honored for 12–24 months, then migrated. Communicated well in advance. Balances protection with eventual alignment.
• Migrate at renewal: New pricing applies at next annual renewal. Most common for SaaS. Can be softened with a discount against the new rate for the first year on new terms.

The choice depends on the size of the change and the customer relationship depth. A 10% price increase rarely causes meaningful churn if communicated with notice; a 40% restructure aligned to a new value metric typically needs a multi-year transition plan to avoid damaging renewals^[2].

6. Signals that packaging needs to change

When should you revisit the tier structure? Pay attention to these signals:

• One tier dominates (80%+ of revenue). If almost everyone buys the middle tier and nobody upgrades, the upgrade triggers aren't working. The top tier may not solve a real problem the middle tier doesn't.
• Tier-mix hasn't changed in 18+ months. Healthy pricing drives tier progression as customers mature. Static mix suggests expansion paths are broken.
• Sales discounting consistently on specific tiers. If the enterprise tier is routinely discounted 40%+ to close, the list price is probably aspirational rather than reflecting value. Realign.
• Competitor with similar product charges 2x+ your price. Either they have meaningful differentiation you missed or there's unrealised pricing room in your tiers.
• Customer requests for bundled features that don't map to your tiers. Frequent ad-hoc requests for specific feature combinations signal that your tier boundaries don't match buyer segments.

None of these is conclusive on its own; two or more together is usually enough to trigger a packaging review. The worst time to review pricing is when cash is critical — the decisions tend to be reactive. Build annual packaging reviews into the planning cadence instead.

7. Numeric worked example — three-tier economics

A project-management SaaS has 1,200 customers, flat $29/month pricing, and $417k ARR. Switch to tiered pricing with seats as the value metric, reprice, and model the 12-month impact.

Starter   $19/mo   up to 5 seats, core features
Growth    $49/mo   up to 25 seats, integrations + reporting
Business  $149/mo  unlimited seats, SSO + audit log + priority support

Assumed mix after 12 months
  Starter   35%  →   420 customers × $228/yr  = $96k ARR
  Growth    55%  →   660 customers × $588/yr  = $388k ARR
  Business   8%  →    96 customers × $1,788   = $172k ARR
  Churn     2%  →    24 customers lost on repricing friction
  Total                                         = $656k ARR

The move from flat-fee to three tiers drives roughly 57% ARR lift, assuming the mix lands where the packaging design intends. Two-thirds of the lift comes from Business-tier pickup (the anchor effect doing real work); one-third from Growth-tier existing-customer migration. The 2% repricing-churn assumption is conservative — OpenView 2024 data suggests well-communicated repricing events typically run 1–3% incremental annual churn^[1].

8. Failure modes worth naming

• Value metric the customer cannot predict. API-call-based pricing sounds clean until a customer gets a $12k invoice after a debug loop. Tie usage pricing to committed-use plans with alert thresholds, or pick a metric customers can forecast — seats, documents, revenue processed.
• Middle tier as a clone of the bottom tier plus one feature. If the only difference between Starter and Growth is one feature, most customers default to the cheaper tier. The middle tier needs to feel like a category-change for the typical growing user, not a minor unlock.
• Hidden pricing on the enterprise tier when the buyer is still self-serve. "Contact us for pricing" on a tier targeted at mid-market SaaS buyers who research without sales contact loses ~30–50% of qualified pipeline. Publish the price unless the deal genuinely requires negotiation (regulated industries, custom contracts, enterprise procurement)^[2].

As of 2026-Q2, OpenView benchmarks show the majority of fastest-growing SaaS adopt hybrid pricing (platform fee + usage metric) rather than pure per-seat^[1]. Hybrid captures both the predictability customers want and the expansion mechanics that reward customer success.