The Hidden Decision on Your Pricing Page
The hardest part of packaging is deciding when a customer has received enough value to pay more.
Pricing and packaging are hard because most of the evidence arrives after you commit. You have to divide a mixed customer base into plans, decide what each plan includes, and set a price before you can see how buyers will respond. Your go-to-market team then takes the package into the market, where customers expose the assumptions that were wrong.
Changing prices or plans later is expensive. New prices affect pipeline and renewals. New packages can alter existing contracts and the systems that quote and bill them. Sales has to explain the difference. Even sensible changes create work across the company, so teams research heavily, debate fiercely, and leave the package alone as long as they can.
Most of that attention goes to the visible choices, like those on your /pricing page: what each plan costs and the features printed beneath it. Somewhere inside a plan, someone chooses the number of users, messages, projects, or API calls a customer gets before the next tier begins.
That number is a forecast about customer value. It predicts that a customer who reaches the limit has received enough value to pay more. It also predicts that customers below the limit still need room to adopt the product. Both predictions can be tested.
Every gate makes a claim
A single price struggles to serve customers with different budgets and stakes. A price low enough for a two-person team leaves enterprise willingness to pay untouched. A price built for the enterprise shuts the two-person team out. Tiered packaging separates those buyers. Rafi Mohammed’s good-better-best structure gives each edition a job: the entry plan brings in customers who would otherwise buy nothing, the middle plan carries the main offer, and the top plan collects more from customers who need more.
The place to focus is the boundary between two plans. Each boundary has to answer two questions. What changes when the customer crosses it? What has happened in the customer’s business that makes paying more reasonable now? Software companies usually answer the first question with a feature list. Advanced reporting starts here. Audit logs start there. API access requires the plan above. The second question, what changed in the customer’s business, gets much less attention, even though it decides whether the customer crosses the boundary willingly or resents being pushed across it.
Draw the gate where the customer has already gotten value from the product. Tie it to something they can watch growing on their own side: more people doing the work, more records under management, and more administrative control needed now that the product runs something the business depends on. Then the higher bill has a cause the customer recognizes, because they created it.
Three places a gate can go
There are three useful places to draw a gate. Capabilities that create adoption should stay open long enough to do their job. Invitations, integrations, shared spaces, and the basic workflow bring the product into daily use. Closing them too early reduces the activity that every later upgrade depends on.
Capabilities associated with operational maturity can support an entitlement gate. Audit logs, advanced permissions, custom reporting, and administrative controls become valuable after a product is established inside a company.
The smallest customers rarely need them. Larger customers often need them to keep using the product safely.
Capacity can support a different kind of gate. The customer keeps the same basic capability but pays as the amount grows: more pipelines, contacts, projects, storage, or transactions. Use itself moves the account toward the next plan.
HubSpot’s customer platform uses all three. Its free CRM includes contact records and a basic deal pipeline, which lets a small team begin running sales work in the product. Custom reporting and forecasting appear at Professional. More detailed permissions and controls appear farther up the range. Deal pipelines rise as a capacity number: one on Free, two at Starter, fifteen at Professional, and a hundred at Enterprise.
The capacity limit creates its own upgrade moment as the customer’s operation becomes more complex. A feature gate triggers when someone reaches for a missing capability, which may happen long after the account has become commercially valuable. Both can work, but they depend on different customer behavior and should be measured differently. They aren’t interchangeable.
A feature gate should not be justified simply because a capability is valuable or can drive upgrade revenue. It requires evidence that the capability becomes materially more important as a customer grows in sophistication, scale, or operational complexity.
Similarly, a capacity gate should be tied to a unit that increases alongside customer value and has a threshold customers can anticipate. The unit should reflect a meaningful expansion in use—such as active users, transaction volume, managed assets, or automation runs—not an incidental count the product happens to store.
Arbitrary limits are easy to implement but difficult to defend. Charging for a metric simply because it is available in the database can feel punitive, unpredictable, or detached from the value delivered. Strong gates create a clear progression: customers receive meaningful value at lower levels, recognize when their needs have outgrown those limits, and can understand why upgrading is worthwhile.
A customer should see the wall coming
Slack chose message history as a free-plan limit early in the product’s life. History accumulates as a team works, and it becomes more valuable as decisions and files collect inside it. The original threshold was 10,000 messages.
Users reached that number at radically different times. A quiet five-person team could take years to reach it. A busy workspace could reach it in weeks. Customers knew the number but couldn’t predict the date without tracking their own message velocity.
In 2022, Slack replaced the message count with a 90-day window. Every free workspace could now anticipate when a message would disappear from view. Slack later added a second limit: messages and files remain visible for ninety days, but data more than one year old is deleted.
Slack kept the underlying value metric and changed how the customer experienced it. Time made the limit predictable in a way a message count couldn’t. A team deciding whether to upgrade could identify which history it would lose and when.
Visibility requires more than putting a number somewhere in the documentation. The customer needs to know the threshold, see current usage against it, understand what happens at the boundary, and connect the limit to the value they receive. Missing any one of those pieces turns an upgrade trigger into a surprise.
Notion shows the difference between publishing a limit and making it easy to find. Its pricing page says pages and blocks are unlimited for individuals and “limited for 2+ members” on the free plan. The exact threshold appears in a separate help-center article: 1,000 blocks per workspace. A buyer can find the number, but the page where Notion asks that buyer to choose a plan doesn’t disclose it.
An obscure threshold changes customer behavior. Teams share logins, open a second account, divide one workspace into two, or keep work outside the product. The company sees lower conversion while the action that explains it happens elsewhere. Support tickets and cancellation interviews may reveal the workaround before the product dashboard does.
Limits expire
A gate drawn correctly at launch won’t remain correct on its own. The product changes what ordinary users can accomplish. The company moves upmarket. Competitors reset expectations about what belongs in an entry plan. Customers who once needed six months to reach a limit may reach it during onboarding, while another segment may never approach it at all.
Moving a gate creates commercial work. Customers calculated budgets based on the plan they bought, salespeople made promises about what it included, and finance built a forecast from the resulting contracts. A new boundary reopens those decisions across every affected renewal.
That dynamic helps explain why packaging changes often arrive beside price changes. In OpenView’s 2023 SaaS pricing data, drawn from more than 700 companies, half of the respondents had changed both pricing and packaging during the year. A quarter changed pricing alone, three percent changed packaging alone, and 22 percent changed neither. Packaging changes rarely happened on their own in that sample. The data suggests companies revisit their gates when a price exercise forces the discussion.
A standing review makes the discussion cheaper. Give every material limit an owner and examine it every six months. Pull the distribution of customer usage around the threshold, the time each segment takes to reach it, conversion after accounts cross it, and evidence of workarounds. Compare those numbers with the customer behavior that existed when the limit was set.
Feature gates need a parallel review. Measure whether the gated capability now appears during activation, whether salespeople routinely give it away, and whether competitors have made it standard. A feature that once identified a mature buyer can become part of the basic product customers expect.
Each review should end with a decision to keep, move, or remove the gate. Moving it requires a transition plan: notice, grandfathering where appropriate, and a clear explanation of what changed in the product or the customer’s use. Document the changes clearly. The goal is to avoid forcing the next pricing project to reconstruct the reasoning from old comparison tables and scattered memories.
Every threshold on a pricing page is a public claim about the customer on either side of it. The company is saying that one customer is still getting started while another has reached the point where paying more makes sense. Usage data can test that claim long before a pricing crisis does.
Before the next debate about plan names, find out who chose the numbers inside them, what customer behavior supported the choice, and when anyone last checked. If the evidence has disappeared, the gate is running on an inherited assumption. Schedule a review of the assumption and determine whether it still reflects your current customers.
Gates should grow with the customer
A pricing page is not just a menu of plans. It is a set of promises about how customers grow, where value accumulates, and when paying more becomes fair. The strongest gates make those promises visible, testable, and revisable.
Treat every limit as a hypothesis, not a permanent rule. When customers can see it coming and recognize the value behind it, a gate supports both adoption and expansion. When they cannot, it becomes friction disguised as packaging.