SaaS pricing page design: what makes buyers pick a plan

People who reach your pricing page are already interested. They came to decide, not to browse. A lot of pricing pages make that harder than it needs to be: too many plans, names that don’t say who they’re for, prices hidden behind a call, and the real questions answered nowhere.

We build our own SaaS products, and pricing pages are part of the website work we do for others, so we see them from both sides. This is the layout we keep coming back to.

What should a pricing page answer?

Three questions, fast: which plan is for me, what does it really cost, and what happens next. Every block on the page should serve one of them. If one doesn’t, it’s probably slowing the decision down.

How many plans should you show?

Two to four. More makes people compare instead of choose.

Each plan should differ from its neighbors in who it’s for, not just in limits. If two plans differ only by a number of seats, one of them is probably a slider, not a plan. Highlight one plan, usually the one most buyers should pick, and say why in a few words.

Name plans by who they’re for

“For solo founders”, “For teams”, “For companies” is easier to pick from than abstract tier names. If you use names, add a one-line “best for”.

Names like Pro, Plus and Premium force people to read the whole feature list to work out where they fit. A short line under each name does that work for them. The same goes for the button: “Start free trial” or “Talk to us” says what happens next better than “Choose plan”.

How do you make the price honest?

• 01Show the real number, with billing period and currency. If there’s an annual discount, show both prices and make it obvious which one is selected.
• 02“From” prices are fine when scope varies. Say what changes the price: seats, usage or scope.
• 03Keep “Contact us” for the top tier only. A page where every plan says “Contact us” isn’t a pricing page.
• 04Show what costs extra: setup fees, add-ons, overage. A surprise at checkout costs more trust than an honest number on the page.

What goes in the comparison table?

Below the plan cards. Group features and lead with the ones that differ, not every checkbox.

The cards are for choosing; the table is for checking. Put a handful of key differences on each card, and the full detail in the table for the people who need it. Group rows by theme, like collaboration, security or support, keep the plan names visible as people scroll, and write rows in plain words instead of feature names only your team knows.

The plan cards are for choosing. The table is for checking.

Where should objections go?

In a FAQ on the pricing page itself, below the table: cancellation, trials, discounts, security, what counts as a seat. The questions people ask right before buying are mostly about risk:

• 01Can I cancel, and what happens to my data?
• 02Is there a trial, and do I need a card for it?
• 03Are there discounts for annual billing, startups or nonprofits?
• 04How is security handled?
• 05What counts as a seat, a project or a unit of usage?

Answer each in two or three sentences, and mark the section up as FAQ schema so search engines and assistants can read it as questions and answers.

How do you make prices readable for AI?

Write prices in HTML text, not images, and add Offer schema. Assistants quote what they can read.

When someone asks an assistant what your product costs, it answers from whatever it could parse. A price inside an image, a tab that only loads on click or a calculator with no default value is invisible to it. Keep plan names, prices, currency and billing period in plain text on the page. More on writing for AI answers in How to make your work legible to AI.

A worked example

Our own /partner page: three engagements (Launch, Partner, Director), each with a “from” price, what’s included, no long contracts, and a FAQ. Here is how it maps to the rules above.

• 01Three options. The names are abstract, so each one has a line that does the “best for” job: from idea to launch, ongoing design for teams that already shipped, a fractional design lead for funded teams.
• 02A “from” price on every engagement, in text, with the billing period: from US$12k, from US$6k/mo, from US$18k/mo.
• 03What’s included, as a short list per engagement, instead of a feature matrix.
• 04Risk answered right under the prices: no long contracts, month to month, pause anytime.
• 05A FAQ on the same page, marked up as FAQPage schema, and each engagement marked up as an Offer.

It isn’t a SaaS plan grid, because a design studio doesn’t sell seats. The rules still apply: few options, a clear line on who each is for, honest prices, and objections answered on the page.

A pricing page checklist

• 01Two to four plans, one highlighted.
• 02A one-line “best for” under every plan name.
• 03Real prices with currency and billing period, or “from” prices with what changes them.
• 04“Contact us” only on the top tier.
• 05A comparison table below the cards, grouped, leading with the differences.
• 06A FAQ on the page covering cancellation, trials, discounts, security and seats.
• 07Prices in HTML text, with Offer and FAQPage schema.
• 08A clear next step on every plan.

If your pricing page needs a rework before or after launch, send your brief.

• Pricing
• Websites
• SaaS