Your prospect has two tabs open. One is your pricing page. The other is your closest competitor's. They are scrolling between them, line by line, and deciding which one is easier to trust.
That is the real brief for SaaS pricing page design. The page has to hold up in a direct comparison without turning into a spec sheet. Here is how we think about it, using two SaaS sites we built: QuestBlue and Construxos.
Why do SaaS buyers open your pricing page next to a competitor's?
Because the category lets them. Cloud communications, for example, is feature dense, and buyers compare providers on capability and price before they ever talk to anyone.
That was the situation QuestBlue faced. The buyer is often a technical evaluator. They are not browsing. They are building a comparison.
This creates two ways to lose:
- Underexplain, and the evaluator cannot verify you do what the other vendor does.
- Overexplain, and the page becomes a spec sheet nobody finishes.
The pricing page has to sit between those failures. Everything below is about where to stand.
Should pricing tiers be published rather than hidden behind a call?
Published. Take the position and keep it.
When a buyer cannot find your price, they do not assume it is fair. They assume it is high, or that you will quote whatever the market will bear. Then they go back to the other tab, where the price is on the page.
For QuestBlue, we published transparent pricing tiers so buyers could qualify themselves against competitors. That phrase matters. A published tier lets the wrong buyer leave early and the right buyer arrive warm. Both outcomes save your sales team time.
If your pricing is truly custom at the top end, publish the tiers you can and say plainly what moves a buyer into a custom quote. Hiding everything because one plan is bespoke is a bad trade.
Should tier names be clever or plain?
Plain, or at least instantly rankable. A buyer comparing two vendors should not need a decoder ring to know which of your plans matches which of theirs.
A good tier name does one of two jobs. It signals size or stage, so the buyer can place themselves. Or it names the kind of buyer the plan is for. A name that signals neither is decoration.
Test it this way. Cover the prices and show the tier names to someone outside your company. Ask them to put the plans in order from smallest to largest buyer. If they hesitate, rename.
Save the personality for your copy. The label on a plan is navigation, and navigation should be boring in the best sense.
How do you say who each tier is for?
Write it out. One sentence at the top of each plan, in the buyer's words, before any feature list.
Construxos sells a platform with tiered products into construction. Their brief was to explain who each tier is for without turning the site into documentation. We built tiered product pages that let each plan make its own case to its own buyer.
That is the move. Each plan gets room to answer three questions:
- Who is this for?
- What problem does it solve for them?
- What do they get that the plan below does not?
A comparison grid cannot do that work. It lists features. It does not say who should care. Give every tier a short argument of its own, then let the grid back it up.
How much feature detail is enough for a technical evaluator?
More than a marketing page usually offers, and less than the documentation does.
The evaluator needs enough to check a claim. For QuestBlue, we built feature-rich service pages with the depth that a technical evaluator needs to compare providers. Depth is not a vice here. It is the reason the evaluator stays.
The discipline is placement. Put the summary first and the detail underneath. Use clear headings so someone hunting for one capability can jump to it. Keep paragraphs short and lists honest.
A useful rule: if a detail answers a question a buyer would ask on a call, it belongs on the page. If it only matters after they have signed up, it belongs in the docs.
How do you keep depth from burying the signup?
By never letting the signup leave the screen, or the story.
QuestBlue's brief was explicit: depth on every service, and pricing transparent enough to survive comparison, without burying the signup. We kept the signup path prominent throughout, so depth never costs the conversion.
In practice that means:
- A signup action in the header that stays reachable as the page scrolls.
- A repeat of that action at the end of each major section, worded for that section.
- One primary action, not three competing ones.
Construxos took the same stance with its demo. We structured every page around the demo signup, treating it as the single conversion event that matters. When there is one event that matters, every design decision gets easier.
What should a skimming buyer see in ten seconds?
The plans, the prices, who each plan is for, and the next step. Nothing else needs to compete.
Most pricing page visitors skim first, even the thorough ones. They are deciding whether the page deserves a closer read. If the first screen is a wall of features, they will close it.
QuestBlue's information hierarchy was built so a skimming buyer and a thorough one both get what they need. The skimmer gets the tiers and the path forward. The thorough buyer keeps scrolling into the detail.
Read your page with your eyes half closed. Can you still make out the tiers, the audience for each, and the button? If not, the hierarchy needs work before the copy does.
How do previews of the product help a sceptical buyer?
They answer the objection that no feature list can: "does this actually work the way you say?"
Construxos is construction software, and construction software is bought by people who are sceptical of software. These buyers want to see the product working before they book a demo. A promise is not enough.
So we designed client-portal previews that let prospects see the platform before committing to a demo. It lowers the cost of saying yes. The buyer arrives at the demo already knowing what the screen looks like.
For your own page, ask what the most sceptical person in your market needs to see. Then put it next to the plan that includes it.
What should you test on your own pricing page this month?
Run these checks. None needs a redesign to start.
- The two-tab test. Open your page beside your closest competitor's. Can a buyer tell which plan matches which?
- The cover-the-price test. Can a stranger identify who each tier is for from the copy alone?
- The ten-second test. Show the page for ten seconds, then ask what they remember.
- The signup test. Scroll the whole page. Is a way to sign up in view at every stop?
- The sceptic test. Is there anything on the page that shows the product, not just describes it?
If two or more fail, the page is costing you comparisons you could have won. Our SaaS website design work covers how we approach this, and you can see the finished sites for QuestBlue and Construxos.
Want a second opinion on your own page? Tell us where to look and we will start with the two-tab test.