Packaging

First PublishedMay 24, 2026Last UpdatedMay 25, 2026ByAtif Alam

The decision this page enables: how features get bundled, named, and gated into the tiers a customer chooses between on your pricing page or in a sales conversation.

Looking for the strategic packaging chapter (tier-architecture frameworks, value-based decomposition)? That lives at Strategy: Pricing & Packaging. This page covers the marketing-execution side: tier-naming, fence design, the pricing-page UX, and the operating cadence around packaging changes.

What packaging is

In the 4 Ps, packaging means the way you bundle your product’s features into 2–4 named offers — the rows on your pricing page, the editions on your sales deck, the SKUs on the shelf. It does three jobs at once:

Sorts customers into the right tier without a sales conversation (mostly true for self-serve; partially true for sales-led).
Communicates the upgrade path so a customer who outgrows the entry tier knows where to go next.
Anchors your price by giving the buyer something to compare to — the “good / better / best” trio is more persuasive than any single price.

For physical products, packaging also means the literal carton, label, and shelf presence — covered briefly later. The bulk of this page is digital / SaaS packaging, where the decisions are made about features in tiers, not paperboard.

The three packaging models

Almost every successful B2B and B2C packaging structure is one of these three (or a hybrid):

1. Good / Better / Best

The classic. Three tiers, each strictly more inclusive than the last. Works when customers vary mostly in willingness-to-pay and feature appetite, and the same feature set can serve everyone with more or less of it.

Free  →  Plus  →  Premium
 5 mb     50 mb     unlimited
 1 user   10 users  unlimited
 (none)   (chat)    (live coach + chat)

Strengths: easy to understand, well-suited to anchoring, decoy-effect-friendly.

Weaknesses: forces you to admit the “Good” tier exists (which some sales teams resist), and can starve the Better tier if Best becomes the obvious enterprise upsell.

2. Role-based (Starter / Team / Business)

Tiers map to who the customer is, not how much they consume. The “Team” plan is meaningful even at low usage because it has team-management features the solo plan doesn’t. Works when the buyer’s identity changes between tiers (individual → team lead → org admin).

Solo      Team         Business
single    multi-user   admin + audit + SSO
my docs   shared docs  org-wide governance

Strengths: tier-name is self-targeting (a 5-person team knows they’re “Team”); fences feel natural; upgrade paths align to organizational milestones.

Weaknesses: doesn’t scale beyond ~3 identities cleanly; some customers don’t see their identity in your tier names (and bounce).

3. Use-case-based (modular add-ons)

A single core product plus modular add-ons priced separately. Works when buyers genuinely want different sub-features and you don’t want to gate someone out of the core product just because they want one extra capability.

Core platform        $X / month
+ Analytics module   $Y / month
+ Compliance pack    $Z / month
+ Premium support    $W / month

Strengths: lets enterprise customers pay only for what they need; reduces “feature shoving” pressure on the core.

Weaknesses: pricing-page math gets confusing fast; the lowest-priced configuration sometimes wins by default; harder to anchor.

When to use which

Choose…	When…
Good / Better / Best	The same feature set scales linearly with usage or scope. (Most consumer SaaS, most freemium.)
Role-based	The buyer’s identity changes between tiers. (Most B2B productivity, collab, ops tools.)
Modular add-ons	Sub-features are genuinely independent and the buyer mix is heterogeneous. (Most enterprise platforms; analytics suites; CRM ecosystems.)
Hybrid	Almost all mature companies end up with a role-based 3-tier core + a couple of paid add-ons.

The fence: what gates an upgrade

A fence is the rule for what’s in vs. out of each tier — which feature, usage limit, or capability moves a customer from one tier to the next. The fence is the single most important packaging decision you’ll make.

flowchart LR
    Starter["Starter<br/>3 users<br/>basic editing"] -->|"team-mgmt features"| Team["Team<br/>50 users<br/>real-time collab"]
    Team -->|"admin + governance"| Business["Business<br/>unlimited<br/>SSO + audit + SCIM"]
    Business -->|"custom + dedicated"| Enterprise["Enterprise<br/>custom<br/>dedicated support"]

Three rules for a good fence

Value-correlated. The fence has to gate a feature the customer’s willingness to pay actually correlates with. Gating “the export button” behind Business is annoying because export isn’t where the value lives; gating “single sign-on and audit logs” is fair because that’s exactly the capability enterprise IT pays for.
Unambiguous. A customer should be able to look at the pricing page and instantly know which tier they need. Fences that require a calculator (“you need Pro if you make >12,000 API calls per month”) are predictable; fences that require a calculator the customer can’t run themselves (“you need Pro if you have advanced workflow needs”) are bad fences.
Fair-feeling. The fence has to make customers feel they’re getting more value at the higher tier, not punished for being on the lower one. Removing a feature that used to be free is the highest-risk fence change you can make; new features locked into a new tier is the lowest-risk.

Common fence dimensions (pick 1–2 per tier transition)

Seats / users — natural for collaboration products; predictable; team-friendly.
Usage / volume — API calls, GB, transactions, contacts. Predictable if exposed in-product.
Feature gating — specific capabilities (SSO, audit, advanced reports). Best for B2B role-based packaging.
Support level — community vs. email vs. SLA-backed. Often a fence by itself.
Integrations — number or class (basic vs. premium connectors). Common in martech.
Compliance — SOC 2 reports, HIPAA, data residency. Almost always behind the top tier.

A fence built on a combination of two dimensions (“up to 10 seats + email support”) is more defensible than a single-dimension fence (“up to 10 seats”), because it removes the gaming pressure on the single dimension.

How to design (or redesign) packaging, step by step

Re-validate the target segments first. Packaging that doesn’t map cleanly to your segments will produce a tier nobody picks (see Targeting).
List your features and tag each with: which segment values it most, willingness-to-pay correlation (high / med / low), and product-team status (table-stakes / differentiator / future).
Pick the model. Good / Better / Best vs Role-based vs Modular. The matrix above is your guide.
Draft 3 tiers (rarely 2, rarely 4 — and almost never 5). For each: name, target segment, headline 3 features, fence to the next tier, target ACV.
Run a value-fence check. For each fence, ask: does the customer’s willingness-to-pay actually jump at this fence? If not, move the fence.
Pressure-test the tier-mix prediction. Healthy SaaS tier mix is roughly 60 / 30 / 10 (lowest paid / mid / top), with maybe 5% custom-enterprise. If your draft would produce 80 / 15 / 5, the middle tier is too thin.
Write the pricing page. One short paragraph per tier, the 3 headline features as bullets, a clear “best for” caption above the tier name.
Test the page with 5 prospects. Show the page, ask “which one would you pick and why?” The 5-test will reveal most of the problems before you ship.
Plan the migration for existing customers, if you’re restructuring. Most repackaging failures are about the migration, not the new design.
Set the kill-switch. What metric will tell you the new packaging is broken? Mix collapse? Downgrade rate >5%? Define the kill before you ship.

Templates

Packaging worksheet

One row per tier. Stop at 3–4 tiers; if you have more, you’re packaging too thin.

| Tier name        | Target segment                          | 3 headline features                                   | Fence to next tier                               | Target ACV | Expected mix | Upgrade trigger                          |
|------------------|-----------------------------------------|-------------------------------------------------------|--------------------------------------------------|------------|--------------|------------------------------------------|
| Starter (Free)   | Solo founders, evaluators               | 1 doc, basic editing, 1 user                          | Need 2nd user / real-time collab                 | $0         | 60%          | Invite a teammate                        |
| Team ($99/team)  | 5–50 person product teams               | Unlimited docs, real-time collab, team workspaces     | Need SSO / audit / >50 users                     | $1,188     | 30%          | First admin asks "who has access?"       |
| Business ($299)  | 50+ person companies, security-conscious| Everything in Team + SSO + audit log + admin controls | Need custom contract / SOC 2 attestation         | $3,588     | 9%           | IT-driven procurement, security review   |
| Enterprise (custom)| Regulated industries, large orgs     | Custom contract, dedicated support, data residency    | (top tier)                                       | $25k+      | 1%           | Procurement-led, RFP                     |

Fence pressure-test

For each fence, score 1–5 on the three rules, then average:

| Fence (Tier-A → Tier-B)        | Value-correlated (1–5) | Unambiguous (1–5) | Fair-feeling (1–5) | Avg | Verdict       |
|--------------------------------|------------------------|--------------------|--------------------|-----|---------------|
| Starter → Team: 2nd user       | 5                      | 5                  | 5                  | 5.0 | Ship          |
| Team → Business: SSO + audit   | 5                      | 5                  | 4                  | 4.7 | Ship          |
| Team → Business: > 50 users    | 4                      | 5                  | 3                  | 4.0 | Ship w/ caveat|
| Team → Business: "advanced"    | 2                      | 1                  | 2                  | 1.7 | Redesign      |

A fence below 3.5 average needs redesign before launch. Anything below 3.0 will visibly damage trust if shipped.

Metrics to track

Tier mix — share of customers in each tier. Targets vary by stage; healthy growth-stage SaaS is roughly 60 / 30 / 9 / 1 across Free / Mid / High / Enterprise. Drift in this mix is the leading indicator of a fence problem.
Upgrade rate — % of lower-tier customers who upgrade within 90 / 180 / 365 days. Target ≥10% at 90 days for a healthy fence; below 3% means the fence isn’t triggering.
Downgrade rate — % of higher-tier customers who downgrade within 90 days of a packaging change. Target ≤2%. Above 5% means the new tier is mis-fitted to its segment.
“Tier-fit” score in win/loss interviews — qualitative measure (“did you pick the right tier?”). A high “wrong tier” signal in lost-deal interviews points to either fence ambiguity or sales-led mis-recommendation.
Pricing-page → trial conversion — leading indicator of whether the packaging reads clearly. Should be ≥10% for self-serve SaaS; rebuilds usually move this number first.
Churn by tier — high churn concentrated in one tier is a packaging signal, not a product signal. Investigate before changing the product roadmap.
Expansion revenue rate (NRR contribution) — fences should produce predictable expansion. Top-quartile SaaS sees 110–130% NRR primarily from upgrade-driven expansion, not just seat growth.

Worked examples

SaaS workspace (B2B — role-based)

Initial packaging (year 1):

Free           Team             Business
1 user free    $99/team/mo      $299/team/mo
basic editing  real-time collab admin + SSO + audit
1 doc          unlimited docs   org-wide governance

The fence between Team and Business is team-wide controls — SSO, audit log, admin-level access management. This passes all three rules: enterprise IT pays for exactly these capabilities, the customer can predict which tier they need (“do we need SSO?”), and Team customers don’t feel they’ve lost anything.

After 18 months, tier mix lands at:

Free      67%
Team      28%
Business  4.5%
Enterprise 0.5%

The Business tier is under-performing the 9% target — interviews reveal the fence (“SSO + audit + admin”) triggers a procurement review (slow), but doesn’t compel the champion to push hard. They add a per-tier capability — “advanced workflows for cross-team approvals” — into the Business fence. That’s a champion-level value (productivity for the buyer themselves), not just an IT value. Six months later Business mix hits 8%.

Consumer fitness app (B2C — good / better / best)

Initial packaging:

Free                         Plus ($9.99/mo)              Premium ($24.99/mo)
3 workouts/week              Unlimited workouts           Everything in Plus +
basic library                Full library + new each week Live human coach chat
no tracking                  Nutrition tracking           Personalized plans

The fence between Plus and Premium is a human coach — a fundamentally different unit of value (a person’s attention, not just software). This is value-correlated (the highest-willingness-to-pay users want accountability), unambiguous (you either get coach chat or you don’t), and fair-feeling (Plus users don’t lose anything; Premium adds a category of value).

The team launches with Premium at $19.99 and watches mix come in at 70 / 28 / 2 — Premium too low. Interviews reveal that $19.99 felt “kind of premium” but “not really premium”; the price didn’t anchor the human-coach value. They raise Premium to $24.99 and add a “Best for: people training for a specific goal” caption above the tier name. Mix moves to 65 / 27 / 8. Same product; clearer packaging.

Physical-product packaging (brief)

For physical SKUs, the same fence-logic applies — what features / sizes / variants are gated into which SKU — plus three additional surfaces:

The carton / label / unboxing — your highest-trust marketing surface (the customer paid to look at it). Treat it as a F-A-B-O surface in its own right (see Features & Benefits).
Shelf presence and SKU strategy — how variants sit next to each other on Amazon, in retail, in the app store. Variant proliferation is the biggest pitfall here; 80% of SKUs typically drive ≤20% of revenue.
Pack size as price-fence — small / medium / family / pro sizes act as a Good / Better / Best on quantity. Same fence rules apply.

For deeper coverage of physical-channel decisions, see Place: Channels.

Common pitfalls

Too many tiers (>4). Choice overload kills conversion. Every additional tier roughly halves the conversion rate of the page.
Naming tiers after sizes — “S / M / L / XL” or “Bronze / Silver / Gold / Platinum.” Generic, gives the customer nothing to self-target on. Name tiers after identities (Solo / Team / Business) or outcomes (Track / Train / Transform).
Fences on metrics customers can’t predict. “Up to 12,000 API calls / month” with no in-product visibility into current usage forces the customer to overbuy or churn.
Changing fences every quarter. Packaging stability builds trust. Aim for one substantive packaging change every 12–18 months, with a clear migration story.
Mixing tier-restructure with a discount in the same launch. You’ll never know which moved the metric. Sequence: restructure → measure for 60 days → run discount.
Hiding the “Free” or “Starter” tier. A pricing page where the cheapest option is not visible above the fold trains buyers to think the page is hostile. Show the entry tier proudly.
“Contact us” as a tier without a price range. Hurts SMB conversion. Either show a starting price (“Custom — from $25k/year”) or move custom out of the public pricing page entirely.
Forgetting the migration plan. Existing customers grandfathered onto old packaging are a long tail of complexity. Plan the migration as carefully as the new packaging.

Tools / further reading

ProfitWell / Maxio (now part of Maxio) — pricing-page A/B testing, packaging analytics.
Stripe Billing — usage-based packaging mechanics; modular add-ons.
Monetizing Innovation (Madhavan Ramanujam) — the canonical pricing-and-packaging book; covers willingness-to-pay studies and value-based fences.
Pricing with Confidence (Holden & Burton) — older but still strong on fence design.
Kyle Poyar’s Growth Unhinged newsletter — practitioner-led examples of B2B SaaS packaging changes.