SaaS Packaging Design: The Good-Better-Best Framework
Good-better-best packaging is not just organizing features into three tiers — it is a deliberate system for anchoring price perception, guiding customers to the right tier, and maximizing both conversion and expansion revenue.
Good-better-best is the default packaging structure for most B2B SaaS companies, and it is almost universally executed poorly. The standard approach — split features into three buckets, set prices, and publish a comparison table — generates mediocre conversion rates and leaves expansion revenue on the table because it treats packaging as organization rather than psychology.
Effective GBB packaging is a behavioral design problem. It requires understanding where customers feel friction, what motivates upgrades, and how price anchoring shapes perception of each tier's value. Get this right and the middle tier sells itself. Get it wrong and you end up with 80% of customers on Good, a thin sales pipeline, and no natural upgrade path.
Why Three Tiers Work Better Than Two
The behavioral economics behind good-better-best packaging is well-documented. Dan Ariely's research on the "compromise effect" shows that when people choose between three options, they systematically avoid extremes and select the middle option at higher rates than in a two-option scenario.
In practice, this means: a company offering two tiers (Basic at $50, Pro at $150) will see lower Pro conversion than the same company offering three tiers (Starter at $30, Pro at $100, Enterprise at $250) — even though the Pro tier moved down in absolute price. The Best tier's presence makes Pro feel like the rational, moderate choice rather than the expensive option.
The data from ProfitWell's pricing research across 3,000+ SaaS companies confirms: companies using three-tier packaging achieve 15–25% higher median ACV than companies using two-tier packaging in equivalent market segments. The difference is almost entirely attributable to anchor effects and natural mid-tier selection.
The Architecture of Each Tier
The Good Tier: Converting at the door
The Good tier serves three functions: it is a low-friction entry point, a demonstration of core product value, and a gateway to the upgrade path. It should be designed to satisfy the most basic use case — and only that use case.
Common mistakes in Good tier design:
- Including integrations or API access that power users need (should be in Better/Best)
- Unlimited users when the business model should price on seats
- Advanced reporting when basic reporting suffices for entry-level users
- No visible ceiling — customers don't know what they're missing until they look at the comparison table
The Good tier should create organic upgrade pressure within 90–180 days for healthy customers. If customers on Good are never hitting limits or requesting features from higher tiers, the Good tier is over-serving.
The Better Tier: Where revenue lives
The Better (middle) tier is the core of your business. It should capture 50–60% of customers and generate 40–50% of ARR. The design goal: serve the mainstream use case completely while justifying a 2.5x price premium over Good.
The Better tier premium is justified by:
- Volume unlocks (more users, more records, more API calls)
- Workflow depth (advanced automation, custom fields, workflow logic)
- Integration breadth (connecting to more tools in the customer's stack)
- Administrative control (SSO, audit logs, role permissions)
- Priority support (faster response times, dedicated channels)
The "workflow depth" dimension is the most powerful upgrade driver. Customers who have built workflows on Good and hit a ceiling are pre-qualified for Better — they've demonstrated product stickiness and have a specific, concrete need.
The Best Tier: Anchoring and enterprise capture
The Best tier serves two purposes that are often conflated: it captures your highest-value customers (genuine enterprise or power users), and it anchors perception of Better as a reasonable choice.
As an anchor, Best must be priced high enough to make Better feel like a bargain by comparison. A Best tier priced at only 3x Better loses anchoring power — it looks like a modest upgrade rather than a category difference. Best should be 5–8x Good to function effectively as both a real tier and a price anchor.
As an enterprise tier, Best typically bundles:
- Unlimited (or very high) usage thresholds
- Enterprise security and compliance (SSO, SCIM, SOC 2 documentation access)
- Dedicated customer success or onboarding support
- Custom SLA terms
- Volume discounts and multi-year contract flexibility
Pricing the Tiers: The Ratio Architecture
The most defensible pricing ratio for B2B SaaS is 1x : 2.5x : 6x (Good : Better : Best).
This ratio creates:
- Meaningful jumps between tiers that require justification (not trivial)
- A Best tier priced high enough to serve as an anchor
- A mid-tier perceived as accessible compared to Best
For specific market contexts:
- SMB-focused markets: 1:2:5 (compressed ratios reduce sticker shock)
- Mid-market focus: 1:2.5:6 (standard)
- Enterprise-focused: 1:3:8 (wide ratios, with custom pricing above Best)
The absolute price points matter less than the ratios and the value delivered at each tier. $50:$125:$300 and $200:$500:$1,200 follow the same ratio and will drive similar tier distribution if the value delivered is proportional.
What Gates the Tiers
The packaging gate — what prevents customers from staying on Good forever — is the most consequential design decision in GBB packaging.
Feature gates: Customers on Good can see the feature exists but can't use it. This is the most common gate and often the least effective. Customers resent being blocked from features they can see; it signals value extraction rather than value creation.
Volume gates: Customers on Good can use the feature but hit a usage ceiling (5 users, 10,000 records, 1 integration). When they hit the ceiling, they upgrade. This gate is more effective because the upgrade is triggered by customer growth, which is a positive signal.
Workflow gates: Customers on Good have access to basic workflow capabilities; advanced workflow logic (conditional branching, custom triggers, API webhooks) is in Better/Best. This gate is the most effective because it ties upgrades to sophistication rather than size.
The research-supported recommendation is to combine volume gates and workflow gates. Volume gates capture growing customers; workflow gates capture sophisticated users who may not be growing in team size but are expanding in use-case complexity.
Designing the Upgrade Trigger
Packaging design is only complete when you've defined what happens when a customer hits a tier ceiling. The upgrade trigger — the moment when a customer in Good faces a limit and decides whether to upgrade — is where packaging converts to revenue.
Effective upgrade trigger design:
- Visible limit indicators: Show customers their current usage relative to their tier limit in the product. "You're using 8 of 10 seats" is more effective than blocking them at 10 without warning.
- In-product upgrade prompts: When a customer tries to use a gated feature, show a modal that explains what tier it's in, what they'd get, and the upgrade path — don't just block with an error.
- CSM-triggered conversations: For mid-market and above, set alerts when customers reach 80% of their tier limit. A proactive outreach from CS is dramatically more effective than waiting for them to hit the wall.
- Self-serve upgrade path: For SMB and PLG motion, the upgrade from Good to Better must be completable without a sales call. Every additional friction point in the self-serve upgrade flow costs conversion rate.
The Comparison Table: Showing Differences, Not Lists
The pricing page comparison table is the packaging's external face, and most tables are designed wrong. The standard approach lists every feature in every tier with checkmarks, resulting in a 40-row table that overwhelms rather than guides.
Effective comparison tables:
- Lead with the 3–5 most important differentiators between tiers (not all features)
- Use plain language descriptions of workflow capability, not feature names
- Include a "who this is for" descriptor at the top of each column
- Highlight the recommended tier (visual emphasis on Better)
- Place the Best tier price prominently to anchor Before the customer reads the Better price
The pricing page structure matters: the middle tier should be physically centered, visually distinct (often with a "Most Popular" or "Recommended" label), and the most immediately visible when the user lands on the page.
Common Packaging Anti-Patterns
The Feature Dump: Stuffing the Best tier with every feature in the product. This makes Best feel bloated and undermines the "enterprise" positioning. Best should have more value, not more features.
Symmetric limits: All tiers cap at the same categories but different numbers (3/10/unlimited users; 3/10/unlimited projects). This creates a perception of proportional scaling that makes Better feel overpriced for the number jump. Better should unlock different capabilities, not just more of the same.
Unclear Best tier: Enterprise pricing that requires a "contact sales" conversation with no published price. While custom enterprise pricing is necessary above a threshold, hiding all pricing for Best creates friction for self-qualifying prospects.
Good-tier creep: Adding features to Good based on support requests or competitive pressure until Good is "good enough" for the majority of your target customer. Review the Good tier quarterly and resist feature additions that reduce upgrade pressure.
For more on how packaging connects to your pricing page architecture and conversion rate, see SaaS add-on pricing strategy.
See Your Growth Ceiling Now
Calculate when your SaaS growth will plateau — free, no signup required.
Implementation Checklist
Before publishing your three-tier packaging:
- Tier distribution target: Do you expect Better to capture 50–60% of customers? If not, redesign the Good/Better boundary.
- Pricing ratios: Is Best at least 5x Good? Is Better at approximately 2.5x Good?
- Upgrade triggers: What specific event prompts a Good → Better upgrade? Is it visible in-product?
- Comparison table: Can a customer in your ICP read the table in under 60 seconds and know which tier they belong in?
- Self-serve upgrade: Can SMB/PLG customers upgrade without a sales conversation?
- Enterprise gate: Is there a clear path from Best to custom/enterprise for deals above your published price ceiling?
Packaging is not a one-time design exercise — review tier distribution data quarterly and adjust gates and pricing when the distribution drifts from the target (50–60% Better, 20–30% Good, 10–20% Best).
Frequently Asked Questions
What is good-better-best SaaS packaging?
How should I price each tier in a good-better-best structure?
What should gate the tiers in SaaS packaging?
How many tiers is optimal for SaaS pricing?
What is the most common GBB packaging mistake?
Related Posts
Enterprise SaaS Pricing: Discount Floors and Approval Tiers
A rigorous framework for enterprise SaaS pricing discount floors and approval tiers — covering discount governance, approval workflow design, the financial math of unmanaged discounting, and how best-in-class revenue operations teams protect gross margin.
9 min readAnnual vs Monthly Pricing Test: SaaS Cash Flow Trade-off
Measure the real impact of shifting customers to annual billing — the cash flow benefit, churn reduction, and revenue per customer trade-offs. Includes the annual discount break-even formula and experiment design for testing billing term incentives.
7 min readCohort-Based Pricing Experiments for SaaS
Use cohort analysis to run pricing experiments that isolate causal effects from confounders. Covers cohort design, measurement windows, holdout groups, and interpreting cohort-level pricing signal.
9 min read