Design a SaaS Pricing Page That Converts

You settled on your numbers. Then you drop them onto a page, ship it, and watch people arrive, scroll, and leave without clicking a thing. The prices were not the problem. The page was. A pricing page is not a spreadsheet with a buy button. It is the last screen between a person who was interested and a person who pays you, and how you lay it out changes how many of them cross that line.

This guide is about the page, not the numbers. If you are still deciding what to charge, that is a different job and it lives in how to price your SaaS. Here we assume the prices are set and the question is purely design and psychology: how to arrange tiers, where to point attention, what each card has to show, and where signups leak out without you noticing.

Where does the money actually come from?#

The pricing page sits at a very specific point in the chain, and seeing where it sits tells you what it is responsible for.

Right person lands on the pricing page
        |
        v
They scan the tiers (a few seconds, not minutes)
        |
        v
One plan reads as "this is the one for me"
        |
        v
The card answers their questions without friction
        |
        v
They click the CTA (trial or buy)
        |
        v
Subscription begins ---> monthly recurring revenue

Everything upstream, the traffic, the positioning, the ad, has already done its work by the time someone reaches this page. The page's only job is to not lose them. That framing matters because it stops you decorating the page and starts you removing friction from it. Every element either helps a ready buyer choose and click, or it is in the way. If how software revenue stacks up is still fuzzy, where does online money come from covers the base mechanism.

The concrete move: open your current pricing page and, for each element on it, ask "does this help someone choose or click, or is it clutter?" Note every element that fails that test.

How many tiers, and naming them#

Three tiers is the default because it works, not because it is a rule. One price forces a yes-or-no decision, the hardest kind to win. Five or more force a research project, and people do not research, they leave. Three gives a low, a middle, and a high: enough to create a sense of choice without creating work.

Name the tiers for the buyer, not for your database. "Starter, Pro, Business" or "Solo, Team, Company" tells a person which one is theirs in one glance. "Tier 1, Tier 2, Tier 3" or cute internal codenames make them do translation work they will not bother to do. The name is a signpost that says "people like you pick this one."

If your product serves two very different buyers, say a solo user and a big team, the tier names can do the sorting for you. A freelancer sees "Solo" and knows where to look. A manager sees "Team" and skips the rest. You are routing people to their answer before they have read a single feature.

The concrete move: if your tiers are named by number or by internal jargon, rename them now to describe the buyer or the use case. That is a five-minute change that removes real friction.

Anchoring and the recommended plan#

Here is the quiet mechanism that does the heavy lifting. When three prices sit side by side, the highest one changes how the middle one feels. On its own, your $49 plan might read as expensive. Next to a $99 plan, that same $49 reads as the sensible middle. This is anchoring, and it is not a trick. It is giving people a frame to make a decision they had to make anyway. The high tier earns its place even if almost nobody buys it, because it makes the plan you actually want to sell look reasonable.

Then you point. Pick the plan you want most people to buy, usually the middle one, and mark it: a subtle border, a soft background tint, a small "Most popular" or "Recommended" label at the top of the card. That badge is one of the highest-leverage elements on the whole page. Faced with three options, most people want to be told which is the safe default, and the marked plan becomes that default. You are not forcing anyone. You are answering the question "which one should I get?" before they have to ask it.

Keep the emphasis honest and light. If the recommended card is twice the size, glowing, and covered in badges, it reads as a hard sell and people get suspicious. A little more prominence than the others is plenty. The badge does the work; the styling just supports it.

The concrete move: mark exactly one plan as recommended, make it the one you want to sell, and give it just enough visual weight to draw the eye first. One plan, not two.

Framing annual billing#

Whether to offer annual at all is a strategy question, and annual vs monthly billing for a SaaS is where that decision belongs. On the page itself, the design question is how to present it so people can choose without doing math.

The standard pattern is a toggle at the top of the tiers: monthly on one side, annual on the other. When someone flips to annual, every card updates to show the annual price. The key detail is to state the saving in plain language right on the toggle or the cards, "save 2 months" or "save 17 percent," so the benefit is visible instead of something the buyer has to calculate. A saving nobody can see does not persuade anyone.

One more detail: when annual is selected, show the effective monthly cost ("$41/mo, billed annually") rather than only the big yearly number. The large annual figure can spook people even when it is the better deal, so anchoring it back to a monthly-feeling number keeps the sticker shock down.

The concrete move: add a clear monthly-annual toggle, spell out the saving in words next to it, and show annual prices as an effective monthly rate with the billing note underneath.

What a plan card must show#

A ready buyer scanning a card is asking four questions, fast. Answer all four and let nothing else fight for attention.

The price, big and unmissable, with the billing period next to it so there is no ambiguity about what they are agreeing to. A one-line description of who the plan is for, "For solo builders shipping their first product," so people self-select without reading features. A short list of what they get: three to six items that capture what matters for that tier, not every feature you have ever built. And one clear button, with a label that says what happens next, "Start free trial," "Get started," "Choose Pro." A button that just says "Submit" wastes the one moment you have their finger hovering.

The mistake here is treating the card like documentation. Feature-list overload is real: when a card has thirty rows of checkmarks, people do not read carefully, they get tired and bounce. Put the few things that differentiate the tiers on the card and move the exhaustive comparison into a separate table lower down for the buyers who want it. The card sells; the table informs. For how any conversion-focused page earns the click, what makes a good landing page applies the same discipline.

The concrete move: trim every plan card to price, a one-line "who it is for," at most six benefits, and one action button with a specific label. Everything else goes below the fold or into a comparison table.

A clearly hypothetical layout, and a before/after#

Every number and result below is invented to show the shape of the thing. It is not data, not typical, and not a promise.

Here is a three-tier layout for an imaginary tool that helps solo founders manage customer support.

   STARTER            PRO  [Recommended]        TEAM
   $19/mo             $49/mo                    $99/mo
   For your first     For a growing solo        For a small
   support inbox      product                   support team

   1 inbox            5 inboxes                 Unlimited inboxes
   1 seat             3 seats                   10 seats
   Email support      Priority support          Priority support
                      Automations               Automations + API

   [Start trial]      [Start trial]             [Start trial]

Notice what the layout is doing. The names route people. The middle plan carries the badge and sits between a cheaper anchor and a pricier one, so $49 feels like the middle rather than the top. Each card shows the same four things in the same order, so the eye can compare down a column instead of hunting. The benefit lists step up along things the buyer can feel getting bigger: inboxes, seats, support level.

Now a before/after, clearly illustrative and invented to show direction, not a measured result.

BEFORE                          AFTER
5 tiers, no plan marked         3 tiers, middle marked "Recommended"
Prices shown "on request"       Prices shown plainly
30-row feature list per card    4 benefits per card + table below
Button reads "Submit"           Button reads "Start free trial"

Illustrative outcome: the page moves from "people scroll
and leave" to "people pick the middle plan and click."

The point of the before/after is not the fictional lift. It is that every change is subtraction and clarity, not addition. You removed tiers, revealed the price, cut the feature lists, and made the button honest. None of that required new features, only decisions about attention.

The concrete move: sketch your own three-tier layout in this exact form, on paper if you like, before you touch any code. Get the structure right first.

What you need and what it costs#

Building the page needs almost nothing beyond what you already have.

Required: a payment processor or merchant of record you have already chosen (that is a pricing-strategy setup, not a page decision), and a page that can render three cards and a billing toggle. A hardcoded three-tier page in plain HTML converts exactly as well as one wired to a fancy billing engine. Optional and genuinely useful: simple analytics so you can see which plan people click and where they drop off, which tells you whether your anchoring is working. Nice to have and easy to over-invest in: a live pricing configurator, per-seat sliders, currency auto-detection, animated toggles. Solo builders love building billing UI because it is a fun problem. It is also a great way to spend a week polishing something that does not move conversion.

The cost is your time, and the trap is spending it on the plumbing instead of the words and the layout.

The concrete move: build the simplest version that shows three cards and a toggle, ship it, and put your remaining energy into the copy on the cards.

How long it takes#

Laying out the page is an afternoon. Learning whether it converts takes longer, because you need real visitors before the page has told you anything.

Do not judge the page on a quiet weekend or a handful of clicks. Give it a few weeks and a reasonable number of the right visitors first. The useful signal is not just "did they buy" but "which plan did they click and where did they stop." If everyone clicks the cheapest plan, your anchoring or your value framing needs work. If people reach the page and leave without clicking anything, the problem is usually clarity or trust on the page, or it is upstream in who you are sending there.

The concrete move: ship the page, leave it alone for a few weeks while real traffic hits it, and only then look at which plan gets clicked.

What beginners get wrong#

The mistakes repeat, which is good, because you can just skip them.

Hiding the price behind "contact us." For most solo and small-team SaaS, this is the single biggest leak. A self-serve buyer who has to email you for a number will almost always just leave and find a competitor who shows theirs. Reserve hidden pricing for genuine enterprise deals, and even then show the lower tiers plainly.

Too many tiers. Five or six plans do not look generous, they look like a decision the buyer does not want to make, so they make the easiest one: leaving. Three is almost always right.

Feature-list overload. A card with forty checkmarks does not inform, it exhausts. People stop reading and bounce. Short cards, detailed table below.

No recommended plan. An unmarked set of three tiers leaves people to figure out the default themselves, and figuring things out is friction. Mark one.

Vague buttons. "Submit," "Buy," "Go." The label is free real estate to reduce anxiety by saying exactly what happens next. Use it.

Treating the trial CTA as an afterthought. Whether the button starts a trial or a purchase is a real choice, and free trial vs freemium is where that belongs, but on the page the button must make clear which one it is so nobody clicks expecting free and lands on a credit-card form by surprise.

The concrete move: audit your page for those six leaks, find the one you are guilty of, and fix it today.

How I would start#

If I were building or fixing a pricing page today, here is the order I would work in.

1. Decide the one plan I want most people to buy. Everything else on the page serves that decision, so I make it first.
2. Lay out three tiers side by side, named for the buyer, with that chosen plan in the middle and marked "Recommended."
3. Strip each card down to four things: price with billing period, a one-line "who it is for," at most six benefits, and one button that says what happens next.
4. Add a monthly-annual toggle with the saving spelled out in words, and show annual as an effective monthly rate.
5. Make sure every price is visible, with no "contact us" gate on the self-serve tiers.
6. Move any exhaustive feature comparison into a table below the cards, for the few who want it.
7. Add basic analytics so I can see which plan gets clicked, then ship it and leave it alone long enough to learn something.

If I already had a live page that was underperforming, my first move would be the cheapest one: mark a recommended plan and reveal any hidden prices. Those two changes alone fix the most common leaks.

What I would not do#

I would not hide prices to "capture leads," because the lead I capture that way is a person I annoyed into leaving. I would not add a fourth or fifth tier to serve one unusual customer, because I would pay for it in confusion from everyone else. I would not bury the differences between plans under identical forty-item feature lists that make people compare checkmarks instead of understanding tiers. I would not make the recommended plan so loud it reads as a hard sell. And I would not treat the page as finished, because a pricing page is something you tune as you learn who is buying, not a thing you ship once and forget.

The bottom line#

Your prices can be perfect and your pricing page can still lose people, because the page is a design problem, not a math problem. The math already happened. What is left is attention: making one plan the obvious choice, answering a nervous buyer's questions on each card, and closing the leaks that quietly send ready buyers away.

So do the plain version. Three tiers, named for the buyer, one marked as recommended, short honest cards, visible prices, a clear button. That is a page that converts, and none of it requires a new feature. When you are ready to send people to it, how to get your first customers covers the traffic side, and the wider engine this all plugs into is in how making money online works. But the layout of the page in front of your prices is a decision you can improve this afternoon.