SaaS Packaging and Tiering

Pricing conversations in SaaS collapse into arguing about a number, usually within ten minutes. Should the middle plan be 79 dollars or 99. Meanwhile the decision that actually determines whether you can win mid-market deals, which capabilities sit in which plan and what the plan scales on, gets made by an engineer deciding where to put a feature flag. Packaging is the marketing decision. The number is the easy part.

Why packaging matters more than the price number

Because packaging decides who can buy at all. A 15 dollar per seat plan that caps integrations at two cannot serve a 400 person company no matter what you charge, and a plan that includes SSO at the entry tier gives away your single best upgrade trigger.

Price is also easier to change. You can raise prices 12 percent with a notice period and some churn. You cannot restructure what is in each plan without rebuilding the pricing page, the sales deck, the billing logic, the docs and the migration path for every existing account.

The full strategic frame sits in SaaS Product Marketing Strategy. This page is the packaging layer specifically.

How many tiers, and why three plus enterprise persists

Three visible tiers plus a contact-sales enterprise option. It’s the dominant structure in B2B SaaS and it survives because it does three jobs at once.

The top visible tier anchors. A buyer seeing 299 dollars at the top reads 99 dollars in the middle as reasonable; the same 99 dollars sitting alone reads as expensive. The middle tier is where you want most volume, and it should be designed as the obvious default rather than the compromise. The entry tier exists to remove the price objection at first contact and to create a population you can expand.

Enterprise as a fourth, unpriced tier does something different. It’s a negotiation surface. It signals you serve large customers without committing to a number, and it gives sales somewhere to put procurement’s demands.

Structure	Works when	Risk	Example pattern
Two tiers plus enterprise	Simple product, one clear buyer segment	No anchor, middle-priced buyers underserved	Early stage tools under $5M ARR
Three tiers plus enterprise	Most B2B SaaS	Middle tier gets overloaded over time	The category default
Four or more visible tiers	Genuinely distinct segments with different jobs	Decision paralysis, long support threads	Products serving individual, team and org buyers at once
One tier, usage priced	Infrastructure and developer tools	Hard to forecast, spooks procurement	Metered API products

The failure mode with three tiers is drift. Every quarter a feature gets added, someone argues it belongs in the middle tier, and after two years the middle plan contains everything and the top plan’s only differentiator is a higher seat cap. Audit the boundaries annually. If you can’t articulate in one sentence why a buyer moves from tier two to tier three, the boundary has eroded.

Choosing a value metric that survives contact with customers

The value metric is what the plan scales on, and getting it wrong causes more revenue damage than any other packaging decision.

Three tests. It has to grow as the customer gets more value from you. The customer has to be able to predict it roughly before they buy. And you have to be able to meter it accurately enough to defend an invoice.

Seats are the most common metric and the most quietly broken one, because seats grow with headcount rather than with value. A company can triple its use of your product without adding a single seat. Slack’s active user billing is an interesting correction here: they bill for users who actually use the product in a period rather than every account provisioned, which removes the “we’re paying for people who left” objection that seat models generate constantly.

Zapier scales on tasks, which is closer to a true usage metric because task volume genuinely tracks how much work the product is doing. The tradeoff is predictability. A customer who can’t estimate their monthly task count is a customer who delays the purchase.

HubSpot’s move to a seat model, splitting core seats from view-only access, is worth studying because it’s a case of a company recognising that its old packaging was charging the same for people who ran campaigns and people who only looked at dashboards. That’s a value metric correction, not a price rise, though customers experienced it as both.

Value metric	Predictable for buyer	Tracks value	Best for
Seats	High	Weak	Collaboration tools where usage is per person
Active users	Medium	Medium	Products with variable adoption across a licence base
Usage volume (tasks, calls, events)	Low to medium	Strong	Automation, infrastructure, developer tools
Records or contacts	High	Medium	CRM, marketing automation, data products
Outcomes (tickets resolved, deals closed)	Low	Strongest	Products with a clean, attributable output

Outcome-based metrics are where the category is drifting, particularly for products with AI-driven automation, and they score best on value alignment while scoring worst on predictability. That tradeoff is real and unsolved.

What to gate versus what to include

Here’s my position, and it’s the argument of this page. Gate on value metric growth, not on features your buyers consider standard.

Feature gating a capability the buyer thinks is table stakes trains them to see the product as incomplete. If a competitor includes basic reporting at the entry tier and you gate it, every evaluation includes the sentence “and you have to pay more for reports”. That sentence costs more than the upgrade revenue it generates.

The features that gate cleanly are the ones that genuinely correspond to organisational scale: SSO and SAML, audit logs, granular permissions and roles, advanced admin controls, SLAs and support tiers, data retention limits, and API rate limits. A five person team doesn’t want SAML. A 500 person company can’t buy without it. That’s a real boundary and nobody feels cheated by it.

Feature gating has one legitimate home beyond scale features: capabilities aimed at a genuinely different buyer. If your entry tier serves practitioners and your top tier serves a VP who needs cross-team rollups, that rollup view is a fair gate because it’s for a different person with a different budget.

The deeper mechanics of tier boundary design are in Good Better Best Packaging for SaaS, and the definitional detail sits in Feature Gating.

Plan naming and the cost of clever

Descriptive names win. Starter, Growth, Business, Enterprise tells a buyer the order and roughly who each is for without reading anything else.

Invented names, the Ignite and Momentum and Atlas school, create a decoding step. The buyer now has to read the feature table to work out which is bigger. On a page where you want the buyer moving forward, you’ve added a puzzle.

There are two defensible exceptions. When your tiers genuinely aren’t ordered, meaning they serve parallel audiences rather than escalating scale, descriptive size names mislead and role names work better. And when the brand is the product, as with a few consumer-adjacent tools, a named tier can carry real identity value. Neither applies to most B2B SaaS.

One overlooked detail: reps have to say these names on calls. “We’d put you on Momentum” sounds like a sales invention. “We’d put you on Business” sounds like a fact.

Add ons, platform fees and the pricing page mess

Add ons solve a real problem. Some capability is needed by 20 percent of your customers, carries genuine marginal cost, and would push the base price past what the other 80 percent will pay. Put it in the tier and you lose volume. Build it as an add on and you monetise the minority without penalising the majority.

Common clean add ons: premium support, extra data retention, additional environments or workspaces, dedicated infrastructure, advanced security review packages, and professional services or onboarding.

The cost is pricing page complexity. Every add on is another line a buyer has to evaluate and another variable in a procurement spreadsheet. Three add ons is manageable. Nine and your pricing page becomes an exercise rather than a page.

Platform fees, where a customer pays a base amount plus per-unit charges, work well for usage-priced products and badly for seat-priced ones. They stabilise your revenue and they make the entry price look higher than it is. Atlassian and Datadog both run versions of this, and both get regular complaints about bill predictability, which is the honest cost.

What a packaging change actually costs to ship

This is the part that gets underestimated by roughly a factor of three. A packaging change is not a pricing page update.

Six to ten weeks is realistic for a company past Series A. The migration comms step is where most of the damage gets done or avoided: a blanket announcement leaves every customer wondering whether it affects them, and your support queue answers that question one thread at a time.

Grandfathering is not generosity, it’s risk management. Twelve months on existing terms costs you some revenue and buys you no churn spike and no review site backlash. Companies that force immediate migration save a quarter of revenue and spend two quarters on damage control.

If a packaging change coincides with a launch, the tier structure and the launch narrative have to be built together rather than sequentially. The mechanics are in Feature Launch Tiers for SaaS and the surrounding launch structure in B2B SaaS Product Launch Playbook.

How to run the review without a full rebuild

Most companies don’t need a packaging overhaul. They need an annual audit that catches drift before it compounds.

Four questions, once a year. Can you state in one sentence why a customer moves from each tier to the next? What share of each tier’s customers buy each add on? Which features have quietly migrated down a tier since the last review? And what share of lost deals cited a packaging boundary rather than a price?

That last number is the most useful and the least tracked. If 20 percent of your losses mention a limit or a missing capability in the tier they could afford, that’s a packaging problem wearing a pricing costume. The structured version of this review is laid out in 90 Day Pricing and Packaging Refresh, and the pricing side of the equation sits in SaaS Pricing Strategy.

Start with the value metric. If it doesn’t grow with customer value, nothing else in your packaging can be fixed, and the rest of the work described in Marketing a SaaS Product and SaaS Product Launch Strategy is built on sand. Fix the metric first, then the boundaries, then the names, then the page.