The pricing page patterns SaaS uses in 2026

Three plans isn't a law. Here are the patterns the best teams ship, and the per-plan moves that actually move conversion.

Pricing pages are the most over-debated and under-tested page in any SaaS product. Every team thinks theirs is unique. The truth is there are about four patterns that work, three details that matter, and a small number of mistakes that quietly kill conversion. This is what to ship.

Pick one of four patterns

1. The classic three-tier

Free, Pro, Enterprise. The middle one is highlighted. This is the most boring pattern and also the highest-converting for most B2B SaaS. Don't fight it unless you have a specific reason.

The trick: the middle tier should be the obvious choice for the median user. If users are stuck between Free and Pro, your free tier is too generous. If users skip Pro for Enterprise, your Pro is too thin.

2. The single-price card

One plan, one price, no tiers. Linear shipped this for years; Cron did too. It signals confidence, the product is good enough that we don't have to upsell you, and removes choice paralysis entirely.

Reach for it when your product is genuinely one product, not a feature ladder. Avoid when your customers have wildly different usage profiles (a startup using 1k API calls/mo and an enterprise using 50M can't pay the same price).

3. The usage-based slider

A slider for the metric that matters (seats, requests, GB), with the price updating live. Vercel and Stripe ship variants of this. It turns the pricing page into a calculator and lets customers see themselves in the product.

Powerful when your pricing scales on a single metric. Dangerous when it scales on five, at that point you're shipping a configurator, not a pricing page, and you should probably move to a quote.

4. The annual/monthly toggle with a per-seat row

Two tiers, a billing toggle, and a small per-seat add-on row. This is the pattern team-collaboration tools converge on, Notion, Linear, Figma all variants of it. Reads as fair because the toggle gives users agency and the per-seat row makes scaling honest.

The three details that move conversion

Anchor with the highlighted middle plan

Mark one plan as recommended or most popular. Visually elevate it, slightly larger card, accent border, a small badge. This is the most-cited and least-controversial finding in pricing UX. It works because most users are evaluating options and looking for the maker to tell them which one to pick.

Strike-through the original price

If you're offering a discount, show the original price next to the current one with a strike-through. Don't be subtle, $199 next to $99. The contrast does the persuading; you don't have to explain.

Let the features comparison breathe

The feature list under each price is what closes the sale. Each row gets a check or a value, vertical alignment is consistent across plans, and the rows are grouped by category (Core, Collaboration, Admin) when there are more than 8 rows. The single most common mistake is cramming 25 rows into one column with no grouping, nobody reads it.

The four mistakes

  1. 01Hiding the price behind "Contact us". Acceptable for Enterprise only. If your Pro plan is "Contact us", you've told every visitor you're not for them.
  2. 02Five tiers. Beyond three, decision fatigue erases any gain from the extra granularity. Collapse to three, push the rest to a comparison table.
  3. 03Per-seat pricing with no minimum. Buyers calculate 1 × $20 = $20 and decide your product is for them, then churn at month two when reality hits. Set a 3 or 5 seat minimum, advertise it, and you'll filter for the right customer.
  4. 04A pricing FAQ that's just legalese. The FAQ should answer the questions people actually ask before they buy: cancellation, refunds, what counts as a user, what happens when I hit the limit, do you offer student/non-profit discounts. If your FAQ says "By using our service you agree…" you've wasted the slot.

What about the lifetime plan?

Lifetime deals work for indie products and tools that don't have ongoing infrastructure costs. They don't work for SaaS that has to keep paying for servers, support, and updates. If you're indie, ship one, it doubles as social proof ("founding members"). If you're a venture-backed SaaS, don't, you'll be subsidizing those users for a decade.

Build yours

The pricing section entry in the directory has the anatomy for each of the four patterns above, plus tuned prompts that produce them in your stack, type scale, anchor styling, feature-list rhythm all encoded. Pick the pattern that fits your product, paste the prompt, then spend your time on the actual prices.

Keep reading