Packaging and Tiers: Designing Plans People Understand

Most teams think their pricing problem is a number problem. They argue about whether the plan should be 29 or 39, they run a survey on willingness to pay, they benchmark competitors, and they walk away convinced they have solved something. Then the pricing page ships and the same thing happens it always does: visitors land, scan, squint, and leave. The number was never the issue. The packaging was.

Packaging is what sits inside each plan, how the plans are named, how they relate to each other, and what a customer has to do to move from one to the next. Pricing is the price tag. Packaging is the product decision that determines whether that price tag makes any sense to the person reading it. I have spent a lot of time on the packaging side, and I am convinced it is the higher-return work by a wide margin. You can fix a price in an afternoon. Fixing packaging that does not map to how people actually buy takes months, because you are effectively re-teaching the market what your product is.

At Chegg I designed monetization models, plan structures, and the pricing pages that presented them, and I ran the conversion optimization on top. The lesson that stuck with me across all of it is simple. Good packaging is not about extracting the most money per visitor. It is about helping the right person recognize the right plan in a few seconds and see a clear reason to grow into the next one later. Everything below follows from that.

Pricing is the number, packaging is the meaning

Say the price out loud and it means almost nothing on its own. Forty dollars a month is expensive for a note-taking app and absurdly cheap for a tool a sales team runs their quota on. The number only carries meaning once it sits next to what you get, who else is on that plan, and what the plan above it offers. That surrounding context is packaging, and it does most of the persuading.

This is why I push back when a team wants to A/B test price points before they have settled packaging. You end up optimizing the label on a box whose contents nobody understands. Get the contents and the structure right first, then the number has something to anchor to. When packaging is clear, a small price change moves the needle predictably. When packaging is muddled, price tests produce noise, because different visitors are reacting to entirely different mental models of what they are buying.

Packaging is also the part customers carry with them. Six months after signing up, nobody remembers whether they paid 29 or 34. They remember that they are on the “Team” plan and that “Business” is the one with the audit logs they will need when they hit fifty people. That memory is the upgrade path, and you designed it, or you did not.

The job good packaging actually does

I hold packaging to two jobs, and I judge every plan structure against them. First, help the right customer self-select the right plan quickly. Second, create a natural upgrade path so growth on the plan produces growth in what they pay. If a packaging design does not obviously serve both, it is decoration.

Self-selection is worth dwelling on because it is where most pricing pages fail. A prospect should be able to look at your plans and think “that one is me” within a few seconds. Not because they read every feature, but because the plans are built around recognizable versions of the customer: the solo user, the small team, the company with compliance requirements. When people cannot place themselves, they do the safe thing and pick the cheapest plan, or they do the paralyzed thing and pick nothing. Both are losses, and the second is the worse one because you never even see it in your revenue, only in a conversion rate you cannot explain.

The upgrade path is the other half. The best packaging makes the next plan feel inevitable rather than upsold. The customer grows, bumps into a limit or wants a capability, and the plan above is sitting there waiting for exactly that moment. When expansion is designed into the structure, you spend far less energy on aggressive upsell motions, and the revenue that arrives feels earned rather than extracted. I have written more about designing that kind of growth-aligned monetization in the pricing and monetization pillar, because it is the throughline behind almost every good packaging decision.

Choose the value metric before anything else

Before you draw a single plan, decide what your tiers scale on. This is the value metric, and it is the most consequential choice in the whole exercise. It is the axis along which a customer gets more value and, not coincidentally, pays more. Get it right and pricing feels fair, because paying more lines up with getting more. Get it wrong and every plan boundary feels arbitrary.

The common metrics are seats, usage, features, and outcomes. Seats work when value grows with the number of people collaborating, which is why so much team software is priced per user. Usage works when consumption tracks value directly, like API calls, messages sent, or gigabytes processed, and it is the natural fit for the consumption models I unpack in usage-based pricing. Features work when different customer segments genuinely need different capabilities rather than different volume. Outcomes, such as charging per conversion or per closed deal, sound ideal because they align perfectly with value, but they are hard to attribute cleanly and often hard for the customer to predict, which makes them a difficult primary axis for most products.

The test I apply is whether the metric grows with the value the customer receives and whether the customer can predict their bill. A metric that scales with value but produces a scary, unpredictable invoice will suppress adoption. A metric that is predictable but disconnected from value will cap your expansion. You want the one that satisfies both, and you usually pick a primary metric to structure the tiers and let a secondary one handle overage or add-ons.

How many tiers, and why roughly three

Almost every durable pricing page lands on three core tiers, and there is a real reason for it rather than convention. Too many tiers create decision paralysis. Every option you add multiplies the comparisons the visitor has to make, and past three or four the effort of choosing overwhelms the marginal benefit of a more precise fit. People do not respond to that by choosing carefully. They respond by not choosing.

Too few tiers has the opposite failure. A single plan cannot serve a hobbyist and an enterprise, and forcing them onto the same terms means you either price out the small user or leave money on the table with the large one. Two plans are sometimes enough for a young product, but you usually discover a middle segment you were flattening.

Three works because it maps to a story people already understand: an entry option, a main option, and a premium option. It gives you room to place a recommended plan in the middle, which is where most of your target customers should land. I say “roughly three” deliberately. Some products need a free tier plus three paid, or three paid plus an enterprise conversation. The point is not the exact count. It is that each tier must correspond to a real, distinct segment you can name. If you cannot say who a tier is for in one sentence, it should not exist.

Good-better-best, and using anchoring honestly

The three-tier layout is the good-better-best pattern, and it works partly because of how people evaluate options in context. A middle option looks reasonable when it sits between a bare entry plan and a loaded premium one. The premium plan does real work even for customers who never buy it, because it anchors the range and makes the middle feel like the sensible, grown-up choice rather than the expensive one.

This is where price anchoring and the decoy effect live, and this is also where I want to be careful. These are genuine features of how humans judge value, and you can use them without manipulating anyone. The honest version looks like this: the premium plan is a real plan that real customers buy, priced to reflect the genuine value it delivers. Its presence happens to make the middle plan look attractive, and that is fine, because the middle plan is attractive. The dishonest version is inventing a plan nobody is meant to buy, stuffed with hollow features, purely to distort the comparison. Customers eventually feel the difference, and the trust you lose costs more than the conversions you borrowed.

Anchoring done right is just giving people a reference point so they can judge value. Show the higher number first, let the recommended plan sit comfortably below it, and make sure every plan in the lineup is one you would be happy for a customer to choose. If a plan only exists to make another look good, cut it.

Name plans for the customer, not your org chart

Plan names are packaging in miniature, and teams routinely waste them. Names drawn from internal jargon, feature codenames, or metal tiers like Bronze and Silver tell the visitor nothing about which plan is theirs. Bronze does not describe a customer. It describes a medal.

The names that work describe the buyer or their situation. “Starter,” “Team,” “Business,” “Enterprise” let people place themselves instantly, because they are reading a word that matches how they already think about their own company. A three-person startup sees “Team” and knows. A five-hundred-person company sees “Enterprise” and knows. The name is doing self-selection work before the visitor has read a single feature, which is exactly what you want on a page people scan rather than study.

Avoid cute names that require decoding, and avoid names that overlap in meaning. If a visitor cannot tell whether “Pro” or “Premium” is the bigger plan, you have added friction for no reason. Names should create an obvious ladder, and each rung should say who stands on it.

Decide what gates a tier, and do not gate the wrong thing

Once you have your tiers, you have to decide what separates them. There are three levers: features, limits, and support. Features gate on capability, so a plan unlocks single sign-on or advanced reporting. Limits gate on volume, so a plan raises the cap on seats, projects, or usage. Support gates on service, so a plan adds priority response or a dedicated contact. Most good packaging uses a blend, but the mix has to match your value metric.

The classic mistake is gating on the wrong axis, and it usually means putting a core capability behind a paywall where it does not belong. If a feature is essential to getting any value from the product, hiding it in a higher tier does not drive upgrades. It drives churn on the lower tier, because those customers never reach the point where the product proves itself. I have seen teams gate the very thing that makes their product worth using, then wonder why the entry plan does not convert or retain. This is the same discipline behind good paywall optimization: the paywall should sit where value has already been demonstrated, not in front of it.

The other trap is gating on an axis the customer cannot control. If a limit is tied to something a customer cannot influence, hitting the wall feels like a penalty rather than a signal to grow. Gate on the things that increase precisely because the customer is succeeding with your product. More seats, more usage, more advanced needs. When the gate lines up with success, hitting it feels like a graduation, and the upgrade feels like the obvious next step rather than a toll.

The enterprise “contact us” tier, add-ons, and the pricing page

Two structural questions come up constantly, so let me take them together, then talk about the page that presents all of it.

The enterprise “contact us” tier earns its place when deals are genuinely bespoke: custom security reviews, procurement, volume negotiation, contract terms that cannot be self-served. Hiding a price behind “contact us” is right when the price genuinely varies by customer, and wrong when you are just afraid to show a number. If a segment can be served with a published price, publish it. Reserve the sales conversation for the deals that actually require one, because every “contact us” you add is friction you are asking a buyer to accept.

Add-ons versus tiers is a question of who needs what. Put something in a tier when it defines a segment, so most customers at that level want it. Make it an add-on when only some customers in a tier need it, regardless of their size, like an extra integration, additional storage, or a premium support package. Add-ons keep your core tiers clean and let you serve edge needs without inflating every plan with features most buyers will never touch. The failure mode is turning add-ons into a scavenger hunt where the advertised price bears no resemblance to what anyone actually pays.

Then the page has to present all of this without overwhelming anyone. A pricing page is a decision aid, not a spec sheet. A clean comparison table, one visibly recommended plan, a limited set of choices, and clear calls to action do more for conversion than any clever copy. Highlight the plan you want most customers on. Reduce the number of decisions in view. Make the primary action on each plan unmistakable. And write copy that removes hesitation rather than piling on features, which is where the discipline of conversion copywriting pays off, naming the objection in the customer’s head and answering it right there next to the button. Feature-list soup, where every plan is a wall of checkmarks, is the most common way to bury a good packaging structure under noise the visitor cannot parse.

Align packaging with growth, and test changes carefully

The best packaging is designed around how customers actually grow, so expansion happens on its own. If your plans map to the stages a customer passes through as they succeed, they climb the ladder because the product keeps meeting them where they are. That is the whole game: revenue that expands because customers expand, not because you pushed them. When you are choosing between a free tier and a trial as the entry point, the same logic applies, and I have laid out that tradeoff in freemium versus trial.

A word on testing, because packaging is not something you tweak casually. Price tests are relatively contained. Packaging changes ripple through your whole customer base, your billing system, your sales scripts, and the expectations of everyone already on a plan. Move existing customers carefully, usually by grandfathering them rather than forcing a migration, and test structural changes on new visitors before you touch the base. Measure the full funnel, not just the click on the pricing page, because a packaging change can lift signups while quietly hurting the quality of who signs up. The signal you care about is downstream: activation, retention, and expansion, not the top-of-page conversion that is easiest to see.

The mistakes I see most often are the same few, over and over. Feature-list soup that buries the decision. Too many tiers that paralyze the visitor. Gating on the wrong axis, so the paywall blocks value instead of following it. Plans that do not map to any real segment, so nobody can place themselves. And a page so cluttered that even good packaging cannot survive it. Avoid those five and you are already ahead of most pricing pages I have audited.

The short version

• Pricing is the number, packaging is what is in each plan and how it is named and structured, and packaging usually matters more.
• Good packaging does two jobs: help the right customer self-select fast, and create a natural upgrade path.
• Choose your value metric first (seats, usage, features, or outcomes); it should grow with value and stay predictable.
• Aim for roughly three tiers. Too many paralyze, too few miss segments, and every tier must map to a real customer you can name.
• Use good-better-best and anchoring honestly. Every plan should be one you are happy for a customer to pick.
• Name plans for the customer they target, not internal jargon, so people place themselves instantly.
• Gate on features, limits, or support, and never behind the value a customer needs to reach before they will pay.
• Use “contact us” only when price genuinely varies; use add-ons for needs that do not define a segment.
• Design the page as a decision aid: clear comparison, one recommended plan, fewer choices, unmistakable CTAs.
• Align tiers with how customers grow, and test structural changes carefully across the full funnel, not just the click.

---

I am Deepanshu Grover, a Growth Product Manager in Paris. If your pricing page confuses more people than it converts, connect on LinkedIn or get in touch.