Good, Better, Best: Designing Tiers That Actually Work
Most tiers are built around what was easy to build. They should be built around what the customer values.
Summary
- Every gate between two tiers should answer one question: what changed about this customer that makes the higher tier worth more to them?
- Good gates track how much they use, how complex their situation is, or what they need in order to buy at all. Feature count is the weakest gate there is.
- Design the middle tier to win. People reliably gravitate to the middle of three, so put your target margin there rather than leaving it to chance.
Almost every company eventually ends up with three plans. Basic, Pro, Enterprise. Or Starter, Growth, Scale. The names change and the structure doesn't.
It's the right structure. Your customers genuinely differ in what they'll pay, and a single price means you either lose the ones who can't afford it or leave money with the ones who'd have paid more. Tiers let you serve both.
The problem is how the tiers get drawn. In most companies, someone sat down with the feature list and split it into three groups, putting the newer or harder features higher up, because that felt fair.
That produces a ladder based on what you built, not on what the customer values. And those two things are rarely the same. Packaging is one of the five layers of pricing, and it is the one most often decided by accident.
The question a tier has to answer
Every gate between two tiers should answer one question: what changed about this customer that makes the higher tier worth more to them?
If the answer is they get four more features, that's a weak gate. Features aren't value; they're how value gets delivered. A customer will pay more when they're getting more, not when they're given more.
Good gates usually track one of three things.
How much they use. More transactions, more users, more volume, more sites. The most reliable gate there is, because usage and value usually move together. This is the same decision as what you charge per, applied to packaging.
How complex their situation is. Multiple locations, multiple teams, approval workflows, integrations with their other systems. Bigger customers have more complicated lives, and they'll pay to have that handled.
What they need in order to buy at all. Security certifications, data residency, trails, single sign-on, uptime commitments, a named support contact. These aren't features in the normal sense, they're requirements. A large enterprise customer cannot buy without them, which makes them the strongest gate you have.
That third category is worth dwelling on. It's the cleanest way to separate an enterprise tier from a mid-market one, because it doesn't require you to withhold anything a smaller customer would actually use.
The design rules
Three tiers. Sometimes four. More than four and buyers stop comparing and start postponing. If you think you need five, you probably have two different products.
Price them roughly one to two and a half or three to six or ten. Tiers too close together don't separate anybody, and everyone takes the cheapest. Tiers too far apart leave a gap in the middle where a real segment of your market lives.
Design the middle one to win. People reliably gravitate to the middle option when given three. That's a well-documented pattern in behavioural research, and you should use it honestly: put your target margin in the middle tier and make it the one you'd genuinely recommend.
Use the top tier as an anchor. A high enterprise tier makes the middle look reasonable, even if very few people buy it. Contact us pricing does this while keeping your negotiating room.
Every tier has to be genuinely usable. A deliberately broken entry tier designed only to push people upward reads as manipulation, and customers notice. If nobody could succeed on your bottom tier, it isn't a tier, it's an advertisement.
Don't gate things people already have. Taking something away from existing customers to create a tier is the fastest way to lose them. When you restructure, grandfather the base.
Sort your features first
Before you draw any lines, sort what you have into three groups. This is a useful exercise on its own, and most product teams have never done it.
Leaders. The two or three things that actually drive the purchase decision. When a customer explains why they bought, these are what they name. Build these brilliantly and use them at the gates.
Fillers. Pleasant, used sometimes, no effect on whether anyone buys. Keep a few for completeness. Stop investing in them.
Killers. Things that actively make people less likely to buy. Complexity they didn't want. Data they didn't want to hand over. Lock-in they noticed. Every product has one or two, and almost nobody has asked.
That last group is the reason to do this exercise. Most companies have never asked customers what makes their product harder to buy, and the answer is often a feature somebody fought hard for.
Where the money leaks in a tier ladder
Three common patterns.
Customers sitting in the wrong tier. Someone on your entry plan who's clearly getting mid-tier value, because the gate doesn't catch them. Look at what your bottom-tier customers actually use, and you'll usually find a group who should be paying more and have found a way not to.
A middle tier nobody chooses. If most customers land at the bottom or the top and the middle is empty, your gates are in the wrong place. The middle tier is supposed to be the obvious answer for the typical customer.
Enterprise deals that are just the middle tier with a discount. If your top tier isn't genuinely different, every large deal becomes a negotiation on price rather than a conversation about what they need. That's a packaging failure showing up as a discounting problem, and it shows up again in net revenue retention.
Not just software
Tiering works anywhere, and it's under-used outside technology.
Services. Three engagement levels: a defined scope, a broader one, an ongoing partnership. It replaces the endless custom proposal with three things a client can choose between.
Manufacturing. Standard, enhanced and premium specifications, or different service wrappers around the same product: delivery commitments, warranty terms, technical support.
Healthcare. Package rates by complexity, room category, or level of consultant access.
D2C. Pack sizes, bundles and subscriptions are tiers by another name, and they're also how you keep the same product at different prices across different channels without customers comparing directly. That is the practical answer to the channel margin problem.
A quick honesty check
Take your current tiers and answer three questions.
Can you say, in one sentence per gate, what changes for the customer when they move up?
Does the middle tier hold the customers you most want, at the margin you need?
If you deleted your bottom tier tomorrow, would those customers move up, or leave?
If any of those is hard to answer, the ladder needs work before the prices do. And every tier still has to clear your floor.
Where to start
Pull the usage data for your bottom tier. Find the customers who are clearly getting more value than they're paying for.
That group tells you exactly where your gate should have been.
Our Pricing Maturity Assessment looks at packaging alongside the other layers of pricing and the cost floor underneath, so you can see whether your tier design is the thing holding you back.
Frequently asked questions
How many pricing tiers should I have?
Three, usually. Sometimes four if you have a genuine enterprise segment with different requirements. Beyond four, buyers stop comparing and start delaying the decision.
What should separate one pricing tier from another?
How much the customer uses, how complex their setup is, or what they need in order to be able to buy at all: security, compliance, data residency, support commitments. Splitting on feature count alone produces gates customers don't believe in.
Why should the middle tier be the one that wins?
Because when people are given three options they reliably gravitate toward the middle. Design it as the plan you'd genuinely recommend for a typical customer, and put your target margin there, rather than leaving it to chance which tier carries your economics.
How useful was this article?
One tap. It tells us what to write more of.
The next one
Get what we publish next, by email.
Working notes on raising, borrowing, protecting, growing and structuring capital in India. One email a week at most, and you can leave any time.
We use your address only to send this. See our privacy policy.
We store your address to send you these emails and nothing else. See our privacy policy.
Related reading
