Four-Tier Wall

The four-tier wall is what happens when a team cannot commit to a customer segment so they build four pricing columns of equal height with overlapping features. Hobby, Pro, Team, and Enterprise sit there like identical soldiers while the visitor hunts for a difference that does not exist. The feature lists run long and bleed across every column so that three of the four options deliver some version of collaboration, exports, history, and support. Real differences hide in asterisks or require a comparison table that scrolls off the screen. Teams reach this layout because they could not pick a primary buyer. Product wanted simplicity. Sales wanted every feature available midway up the page. Marketing asked for something for the hobbyists. No one killed any idea so the designer got instructed to make four equal columns. The result exposes the pricing page as the most honest screen on the site. Every unresolved argument from the last six months of roadmap meetings appears here as another row of checkmarks.

This is not thoughtful segmentation. It is not the same as Linear running Free, Standard, Plus, and Enterprise. Linear made each tier represent one concrete leap a real design team actually takes. Solo tinkerer to coordinated group to power users who live in the advanced permissions to orgs that need SAML and audit trails. The columns do not match in height because the value jumps are real and the copy says so above the fold. The four-tier wall offers no such clarity. It is a hedge dressed up as choice that forces the buyer to decode the team's unfinished product strategy.

It is not the clean opinion Vercel ships with three tiers or the decisive single price Superhuman posts at thirty dollars a month with zero decoys. Those pages qualify the visitor in under ten seconds. The wall generates support questions that start with which plan should I pick. It is not honest transparency. It is the spec doc the team could not turn into pricing.

Framer in 2024 and 2025 became the concrete example most designers recognize immediately. The product earned respect for its quality yet the pricing page kept sprouting new tiers as features and segments multiplied. One column for indie designers. Another for small teams. A third for agencies. A fourth that blurred into enterprise with vague promises and a contact-sales button where the price should sit. Visitors scanned the overlapping lists, failed to self-qualify, and bounced. The same wall appeared on the 2023 pricing pages of several no-code and AI tools that raised massive rounds and tried to serve every persona at once. One tier looked too much like the next. The only obvious difference was price yet the features felt interchangeable. Buyers closed the tab without telling anyone why. Contrast that with GitHub whose model has stayed stable for over a decade. Free for solo open source work. Team for groups that need private repos and collaboration. Enterprise for companies that live or die by compliance features like SAML, SCIM, and audit logs. Each tier matches a real organizational state instead of an internal compromise. Cursor follows the same discipline. Its default AI plan carries a clear number. Business exists only for teams that need SSO and admin controls. No fourth column appears because no one confused a solo developer with a fifty-person engineering org.

Stripe gets away with a calculator because transactions are literally the unit of measure. Most teams copying that pattern are not Stripe. They are reaching for sliders because they still cannot tell a team of eight what the product should cost. Anthropic splits first by developer versus business use cases then layers usage inside each split. That initial split is the opinion. Figma charges per editor seat while viewers ride free and treats Dev Mode as a side chip instead of forcing another column into the wall. Notion keeps per-seat pricing clean and lists the AI add-on as its own line so buyers understand it is not a sneaky bundled increase. These teams formed clear opinions before they opened Figma. The four-tier wall teams design the page first and hope the opinion appears later.

Use the four-tier wall when your team meeting ends with everyone defending their favorite customer segment and no one has the guts to kill a use case. Ship it when internal politics matter more than buyer clarity or after customer interviews reveal four personas and you refuse to pick one as the beachhead. Deploy it if you want more demo calls from confused prospects who cannot self-qualify after thirty seconds on the page. It performs beautifully at creating the illusion of sophistication while killing conversion.

Never use it once you can state in one sentence who the product is for. Avoid it the moment your team can articulate the single decision each tier represents. Cut the fourth column the instant it appears in wireframes. One decision per tier is the rule. Solo versus team. Self-serve versus contract. Five seats versus unlimited. If the fourth tier does not represent a clean new decision it is noise that dilutes everything above it. The strongest pricing pages in 2025 and 2026 stay short because the teams behind them finished arguing first. They killed ideas instead of adding columns. They respected the five rules instead of hiding behind layout experiments.

Four-tier walls are museums of internal disagreement rendered in coral buttons and green checkmarks.