Your pricing page is a growth surface, not a finance document.

Most pricing pages are written by the person who owns the revenue, and they read as a statement of fact: here are the numbers, here is what each one costs. That framing quietly mislabels one of the most powerful growth surfaces you have as an accounting artifact. The prices are the least interesting thing on the page. The structure — the tiers, the limits, what’s gated behind which wall, and how someone climbs — is shaping behavior long before anyone reaches for a card.

Start with tiers. A tier boundary isn’t a fence around revenue; it’s a mirror you hold up to the user. The lines you draw teach people which one they are — oh, I’m a team, not an individual; I’m past hobby, I’m a business now. Draw them where real usage clusters and the page sorts your users for you. Draw them badly and you either strand a heavy user in a cheap plan or scare a curious one off the ladder before they start. Segmentation isn’t a finance decision you back into. It’s a product decision about who your users are allowed to become.

Then limits, which are the real levers, because a limit is a throttle you can point in either direction. Placed right at the moment value has been proven — you’ve organized ten projects, invited your fourth teammate, pulled the report you actually needed — a limit converts, because the user is upgrading toward more of something they already want. Placed during onboarding, before the aha, the identical limit is a wall in front of a stranger, and it doesn’t monetize activation, it kills it. Same number, opposite outcome, decided entirely by where on the value curve it bites. Gate after the promise is kept, never before.

The free tier deserves the same reframe. Read as finance, it’s revenue left on the table, and the instinct is to shrink it. Read as growth, it’s distribution — but only if it’s built to produce something other people see, or something that pulls the user back. A free tier that generates shared artifacts, public links, or a daily habit is a loop. A free tier that’s just a stingy trial is a cost. Design it for the loop, not the taste-test.

Upgrade paths are the last piece, and the mistake is thinking they live on the pricing page. They don’t. The page should only ratify a decision the product already surfaced — you’re on 4 of 5 seats; this is your third export this week. The best upgrade prompt is a moment inside the workflow where the ceiling and the value show up in the same breath. The pricing page is just where the user goes to confirm what the product already told them.

Put it together and the reframe is simple: every tier boundary is a behavioral hypothesis. Where you draw a line is a bet about when value is proven and what makes someone reach for their card — and like any hypothesis it should be measured. Watch upgrade, downgrade, and expansion at each boundary like a funnel, not a receipt. Optimize the page for capturing today’s revenue and you’ll over-gate, strangle the loop, and suppress the growth that pays for next year. Optimize it for behavior and the revenue tends to follow, because you priced the thing where the value actually lands.

To read further: Shapiro & Varian, Information Rules (1998), on versioning and segmenting by willingness to pay — old, but still the clearest account of why the same product offered at three price points beats one.