SaaS pricing page design: how to build one a buyer can decide on

Websites

Imran KhanNovember 9, 202618 min read

Illustration of a pricing page with three plan cards, the middle one marked Popular, and a cursor over its Book a call button

A pricing page has one job: let a buyer work out which plan is theirs, what it costs and what happens next, without asking anyone. Most pricing pages that fail don't fail on looks. They fail because the visitor has to guess one of those three things.

We design and build SaaS marketing sites for a living, so we're not neutral, and we'll say where our own examples are thin. We have no client SaaS pricing page to show you. What we have is our own pricing page, which sells a monthly plan and a fixed-scope project side by side, and two website templates, Finsaro and Agentory, which we designed for other founders to buy. We've used those. We've also left out the "this change lifts upgrades by 30%" figures that many guides quote, because we couldn't check where they came from. Every outside fact below is linked and was read on 5 November 2026. The Nielsen Norman Group pieces we lean on are of different ages (2013, 2014, 2017 and 2024), and we give each one's year where we use it, because user behaviour changes and you should weigh them accordingly.

What a SaaS pricing page is for

Someone who opens your pricing page has usually already decided your product might help. They are now asking narrower questions: which plan fits me, what will I really pay, can I get out, and who else is paying this. If your page answers those in order, it's doing its job. If it makes them open another tab to find out, it isn't.

That makes it different from the rest of your site. The home page explains. The product pages persuade. The pricing page is where a person checks that the offer is safe to say yes to. It's closer to a form than to a brochure, and it should be designed like one: one decision, no distractions, clear next step.

If you're planning the whole site, our guide to SaaS website design best practices goes through every page. If the page you're fixing is a campaign page, read SaaS landing page design. This guide is about the single page where the money question gets answered.

Decide what you charge for before you design anything

A pricing page can't fix a pricing model that confuses people. If you can't say in one sentence what a customer pays for, the page will end up listing everything to compensate, and the buyer will see a wall of text.

Settle these before opening a design tool:

  1. What the price scales with. Seats, usage, projects, hours, features. Pick the thing a customer can see growing, so the next plan makes sense to them.
  2. How many plans you really have. Count the groups of buyers who need different things, not the number of price points you could invent.
  3. What is the same on every plan. Whatever is true for everyone (cancel any time, you own your data) goes in one place instead of being repeated and diluted.
  4. Whether a price can be shown at all. More on that below.

We follow our own advice here. Our three plans on our pricing page differ mainly on how much senior designer time you get a month, and the rest sits in the same list on every card: design and build in the same hours, unused hours roll over, you can top up, pause or cancel any month and you own everything we deliver. A buyer who has understood one plan has understood all three.

Show the price, or say why you can't

Price is the first thing business buyers look for. The Nielsen Norman Group's 2013 article on stating the price on B2B sites says business customers report pricing as the most needed piece of information online, yet many B2B sites don't show it. It also reports that in their studies they watch participants go to competitors' sites when a site doesn't show prices, and it points out that price tells people which product category they're looking at.

For a self-serve product, that decides it: show the numbers. A visitor who can't qualify themselves in a minute will go and look at someone else's page.

For a product sold by a sales team, you often can't print a single figure. The same article has a section on what to do then, and the idea is simple: give the buyer something to work with. A starting price, a typical range, or an example of what a common scenario costs all beat a button that says "Contact sales" and nothing else. Whatever you do, say what moves the price. We do it on our own page. Under our fixed-scope line, the FAQ lists the three things that push a project up or down the range: how many screens or surfaces there are, whether we're designing only or designing and building, and how settled the brief is.

A split we'd suggest, and one the guides from Webstacks and Designstudio UI/UX also describe in their own ways: publish exact numbers for the plans a person can buy alone, and keep a "talk to us" for the top plan where the deal really is custom. That's our judgement and not a rule, but it fits the Nielsen Norman Group's 2013 finding that buyers go elsewhere when they can't find a price. That finding is old, so test it with your own buyers.

Designstudio UI/UX gives a rule of thumb for where the line sits, based on average contract value (ACV): under $25K, always show pricing; between $25K and $100K, show starting prices and keep "Contact Sales" for the enterprise tier; hide the price entirely only for genuinely custom deals. It's that guide's own rule, not a tested one, but it's a useful starting point if you're arguing about this in a meeting.

Trials and guarantees belong in the same decision. A free trial, a free plan or a money-back window each lowers the cost of saying yes, and the page should say which one you offer and for how long, next to the button. We don't have our own test data on which works best for which product, so we won't rank them. Put whichever you offer where the doubt is, and make sure the terms are written on the page, not only in the sign-up flow.

Build the page in the order the buyer asks

The most common structure problem is a page that starts with a grid of plans and nothing else. Here is the order we'd use, and it's the order a nervous buyer asks things.

  1. A heading that says what the page is for. One line. "Pricing" on its own is fine. A promise on top of it is better, as long as it's a real one.
  2. The plans. Side by side, with the price, who it's for and one button each.
  3. The comparison table, if you have more than a few differences to show.
  4. Proof. Who else pays this and what it did for them.
  5. The FAQ, which answers the objections the table can't.
  6. A way to talk to a person. A call, a chat or an email, for the buyer who's still unsure.

Our template for finance software companies, Finsaro, shows the same thinking over a whole site. On its case study page we describe its pricing page as three plans side by side, a full comparison table beneath them, and the reassurances people look for before they pay: a refund window, no hidden fees and cancel any time. The questions that are left come after. The home page makes the same move one step earlier. It shows the product first, then what it does, then the numbers and the people who use it, and only then the plans, so that by the time a visitor reaches the price they've seen what they'd be paying for.

Plans: how many, how named, which one to highlight

How many. Eleken's guide says to stick to three tiers and warns that more than four plans can confuse, and we lean the same way, with one condition. Three plans work because they let a buyer place themselves: smaller, middle, bigger. A fourth plan usually means you haven't decided who one of the first three is for. If you truly have a free plan and three paid ones, show the free one as a lighter option, not as a fourth card of equal weight.

How named. A name should tell a buyer if the plan is theirs. In our view, plan names that describe the buyer or the job ("Solo", "Team", "Scale") are easier to use than names that only rank ("Silver", "Gold"), because a person who doesn't know your product can still place themselves. We haven't tested that, so treat it as a starting point. Under each name, one line on who it's for. On our own page, the middle plan is described as "for a product that ships every month: the same senior designer, twice the hours". The line does more than the name does.

Which to highlight. Pick the plan most buyers should choose, and mark only that one. We use a "Popular" tag on the middle card. If every card is highlighted, none of them is. A highlight is a claim about your customers, so make sure it's true. If you don't know which plan most of your buyers pick, find out before you decide, from your own sign-up data.

What goes on a card. The name, the one-line "who it's for", the price with its unit, the main thing that differs from the plan next to it, and one button. Don't put the entire feature list on a card. Keep that for the table.

Switches for billing period and size

Toggles help when they remove a calculation the buyer would otherwise do in their head. Monthly versus annual is the usual one. Our page has a Monthly, Quarterly and Yearly switch for the same reason, and a "2x size" switch that doubles everything on the plan: twice the senior designers, twice the hours and twice the requests at a time, at twice the price. We explain it in the FAQ in one line, because a switch that changes a number without explaining why is the fastest way to lose trust.

Three rules for any switch:

  • It changes the numbers on the page, all of them. If the price changes and the feature list doesn't, the buyer wonders what else is wrong.
  • The default should be the option you expect most buyers to choose, not the cheapest-looking one. That's our view; check it against your own sign-ups.
  • The label says what will happen. "Annual" tells a buyer less than "Annual, billed once a year".

The comparison table

A table has one job: help a buyer who has narrowed to two plans choose between them. The Nielsen Norman Group's 2024 article on comparison tables defines it as columns for products or services and rows for their attributes, so people can compare quickly. Two of its points matter most for pricing pages.

First, you don't have to show everything at once. Its example is SmugMug, which showed a very simplified "at a glance" table for its three plans and put the detailed table on a different page. Show the five or six rows that decide between plans and let the buyer ask for the rest.

Second, on a long table the column headers should stay in view as people scroll. The same article reports that without fixed headers, users have to remember which column is which, or scroll back up to check.

Our own habits on top of that:

  • Write rows in the buyer's words. "Seats" beats "licence entitlements".
  • Put the rows that decide first. The detail goes in a group that opens on request.
  • Repeat the button under the table. A buyer who has just finished comparing shouldn't have to scroll back to act.
  • Say what's the same. A one-line "every plan includes" above the table saves a dozen identical ticks.

### The table on a phone

This is where pricing pages quietly break. A table that works at 1440 pixels can be unreadable at 375, or worse, push the whole page sideways. We hit this ourselves on this blog: in our guide to what it costs to design an app, a table with four or five columns pushed the whole page to 472 pixels wide on a 375 pixel phone until we cut the tables to three columns. That's now a rule for every post here.

The Nielsen Norman Group's 2017 piece on mobile tables covers the options: keep the columns large enough to be legible, stick column headers in place, make it obvious when a table scrolls sideways, and use accordions for groups of data. It also calls rotating the phone a last resort. For a pricing table, our practice is to stack the plans, put each plan's list under its own card, and show only the differences as a short table of three columns or fewer. Test it on a real phone, not just a narrow desktop window.

Proof, placed next to the price

A visitor looking at a price is asking whether it's worth it. Proof belongs within sight of the answer. That can be a customer quote, a line from a review, a customer count, a rating or a logo row. Match it to what's being sold: a quote about audit logs belongs beside an enterprise plan and a quote about getting started quickly belongs beside the smallest one.

We follow this on our own page, where a rating and the number of founders we've worked with sit in the hero, above the plans. On Finsaro's home page, as the case study describes, the numbers and the people who use the product come before the plans. And only use proof you can show. If you don't have customers yet, say what you do have, such as a refund window or a trial. That's our advice, not a tested rule. Invented numbers are worse than none, and a buyer who's about to pay is exactly the person who checks.

The buttons

One button per plan, one label, the same label across the page. Say what happens next: "Start free trial", "Book a call" or "Buy now" all tell a buyer something. "Get started" tells them nothing. On our own page every plan's button reads "Book a call", because that's honestly what happens next, and under the plans there's a line for the buyer who's still unsure: "Not sure which tier fits? Book a call. Fifteen minutes is usually enough."

If you sell both ways, self-serve and through sales, don't give every plan two equal buttons. Let the plan that's sold alone have the buying button and let the top plan have the talking one, so the page tells the truth about how each is bought.

Put the reassurance next to the button, where the doubt is. "Cancel any month", "No hidden fees", "Refunds in the first month" (only if it's true) do more beside the button than in the footer.

The FAQ: answer what the table can't

A pricing FAQ isn't there to fill the bottom of the page. Each question should be one a buyer has stopped at before. Ask your sales team and your support inbox, and write the answers in their words. The ones that almost every pricing page needs:

  • What exactly is included in each plan?
  • What happens if I go over my limit?
  • Can I change, pause or cancel, and when?
  • What's the difference between the monthly and the annual price?
  • Is there a refund, a trial or a way to try it first?
  • Who owns what I make or store?
  • What do I do if none of the plans fit?

Our own FAQ answers "What does a subscription actually include?", "When is a fixed-scope project the better choice?", "What pushes a project up or down the range?", "What does 2x size mean?" and "Can I pause, change or cancel my plan?" We wrote them after thinking about what a founder asks before booking a call, and each answer gives a rule of thumb, not a pitch: where the roadmap is still shifting, for example, a subscription usually works out better than a fixed scope.

Keep the answers short. Accordions are the usual way to show a FAQ. The Nielsen Norman Group's 2014 article on accordions is about complex content on desktops, not pricing pages, so we wouldn't lean on it for this. Our own rule is simple: an accordion is fine for short answers, but don't hide the logic of your pricing inside one.

Two ways to buy on one page

Some businesses sell more than one way. We do: a monthly plan, where you get a designer's hours, and a fixed-scope project for people who know exactly what they need. That's a design problem a lot of services and SaaS-with-services companies share, such as a product with a setup package or a plan with a one-off migration.

What worked for us is to make the two cases visibly different and to say how to choose. The plans take the main part of the page. The fixed-scope project gets its own short block beneath them ("One time projects starting from $5,000"), and the FAQ explains when each is the better choice. The buyer is never asked to compare a monthly price with a one-off price in their head.

A pricing page for a product you can't see

A pricing page for a product we'll never see is its own exercise. When we designed Finsaro and Agentory, every figure, quote and plan was a stand-in for the buyer's own. That changes the brief. The layout has to hold prices of different lengths, plan names of different lengths and a feature list of any size, and it has to say what to put where. Our case studies describe a frame for each stand-in, made to be filled with the buyer's own content. If you design a page your team will edit, do the same. Make the price, the unit, the list and the FAQ real, editable pieces instead of one screenshot of a table.

Usage-based and AI pricing

If you charge by usage, or sell AI features by credits, the page has a harder job: it has to make a variable bill feel predictable. We don't have a client project of this kind to show you, so we'll attribute what we read. The Webstacks guide, one of the top results for this search, reports that of the 19 pricing pages it reviewed, at least eight carry a dedicated AI pricing dimension, and that the most common pattern is a credit allotment layered on top of an existing seat or usage price. Webstacks praises examples that show the allotment inline with each tier. Our own view, which we haven't tested, is that whatever your meter, you should also give the buyer a worked example of a typical month.

Mobile and speed

We haven't got a trustworthy figure for how many buyers open a pricing page on a phone, so we won't quote one. Check your own analytics, and if the share isn't tiny, design the phone layout first and check the desktop second.

On a phone:

  • Stack the plans, with the highlighted plan first or marked clearly.
  • Keep the price and the button visible together without scrolling past the feature list.
  • Make switches large enough to hit with a thumb.
  • Send the buyer a way to keep the page. A short link or an email-this-plan button helps a buyer who's showing it to someone else.

Page speed is the same as on any marketing page, so we'll point to our landing page guide instead of repeating them here.

Test it, then change one thing

You can learn a lot before you have enough traffic for a test. Ask five recent customers to find the plan they'd choose and say what they expect to pay, and watch where they hesitate. Look at what visitors do on the page: which switch they use, where they stop scrolling, which FAQ they open. If you do have the numbers, the first measures are simple: how many visitors reach the pricing page, how many click a plan button, how many finish, and how that splits between phone and desktop.

Then change one thing at a time. If you change the plan names, the highlight and the button label together, you won't know which one did the work. And write down the date of each change, because pricing pages are easy to forget about, and stale prices are worse than no page.

Ten mistakes we'd fix first

  1. No price and no way to estimate one. The visitor goes to a competitor.
  2. Four or five plans that nobody can tell apart. Cut or merge.
  3. Everything highlighted. Choose one.
  4. A table that breaks on a phone. Test it on a real device.
  5. A feature list that reads like the product's menu. Show the rows that decide.
  6. A switch that changes some numbers and not others.
  7. A button that says "Get started" on every plan. Say what happens next.
  8. Proof from a different page. Put it by the price.
  9. An FAQ that dodges the question. If a buyer asks about cancelling, say how.
  10. Prices that were true last year. Date the page, and update it when the plans change.

A checklist before you launch

  • [ ] I can say in one sentence what a customer pays for.
  • [ ] Each plan has a name, a one-line "who it's for" and one button.
  • [ ] One plan is highlighted, and it's the one most buyers pick.
  • [ ] Every switch changes every number it should.
  • [ ] The table shows only the rows that decide, and works on a phone.
  • [ ] Proof sits near the price and none of it is invented.
  • [ ] The FAQ answers the questions our sales and support teams hear.
  • [ ] A buyer who is still unsure has a way to talk to a person.
  • [ ] I've tested the page on a real phone.
  • [ ] The date and the prices on the page are current.

What it costs to have a pricing page designed

We don't sell a pricing page on its own, and we'd be wary of anyone who quotes one flat figure for it, because the work is mostly structure and copy and depends on how many plans, switches and tables you have. For us it's part of a project or a monthly plan. Our fixed-scope projects start from $5,000, and our monthly plans start from $2,000 a month for 40 hours of a senior designer's time, with design and build in the same hours. Those are our prices for design work in general, not the price of this one page. The details are on our pricing page. Whatever you're quoted, check what's included: the copy, a phone layout, a table that works on a phone and a page your team can edit without a developer.

FAQ

Three for most products, so a buyer can place themselves as smaller, middle or bigger. See the plans section above.

Show them where you can. If you can't, show a starting price, a range or an example, and say what moves it.

Yes, one, and only if it's the plan most buyers should pick.

See the list in the FAQ section above.

Stack the plans and keep any table to three columns or fewer. The Nielsen Norman Group's mobile tables article lists the other options.

Count how many visitors reach it, click a plan and finish, split by phone and desktop. With little traffic, watch five customers use it.

It depends on how many plans, switches and tables the page has, and we don't price the page alone. For us it's part of a fixed-scope project (from $5,000) or a monthly plan (from $2,000 a month). See our [pricing page](/pricing/).


If your pricing page isn't doing its job, book a call and bring the link. We'll tell you what we'd change first, and what our SaaS website design work would cover.

About the author

Imran Khan, Founder & Creative Head

15 years of industry experienceFormer Head of Design at Day TranslationsFormer Creative Lead at SupersideWork at Superside for brands including Meta, Red Bull and Ray-Ban

Find him on-

Imran Khan, founder of Usarion

Book a call

Pick a time that suits you

Get in touch

Let’s build something amazing together

Project details

or write directly to hello@usarion.com

We use your details only to reply to you. Privacy policy

For product, interface and web-system work that needs clear direction and careful execution.

// CookiesWe use Google Analytics and Microsoft Clarity to see which pages help people. They only run if you say yes. Privacy policy