SaaS Pricing Page Best Practices: 10 Checks, With Data

Your pricing page is where a SaaS visitor stops browsing and starts deciding. Many visitors get there from the homepage, and our SaaS homepage best practices cover that page section by section. It's also one of the most visited pages on most B2B SaaS sites. In HockeyStack's analysis of 80 B2B SaaS companies (31 million unique visitors, published December 2025), pricing pages took 16.5% of all website traffic, against 0.91% for demo pages.

That makes small problems on the pricing page expensive. This guide covers 10 checks, in roughly the order a buyer reads the page, with the research behind each one and where that research runs out.

1. Show the price

Nielsen Norman Group's usability studies with business buyers found that price is the information people want most, and that participants left sites that hid it and went to competitors. Hiding the price doesn't stop the question. It just sends the visitor somewhere else to answer it.

The pipeline data points the same way. In the HockeyStack report, pricing pages without public prices converted more form fills (4.6% vs 2.8%). But leads from pages with public prices turned into pipeline at 17.5% vs 10.3%, about 1.7 times better. More forms from hidden pricing mostly meant more people asking "how much?"

Fix: publish your prices. If you truly can't, NN/g's advice is to show a starting price, a range, or prices for a few typical scenarios rather than only "Contact us."

2. Name each plan for the buyer, not the metal

"Silver, Gold, Platinum" tells a visitor nothing about which one is theirs. A one-line "for" statement under each plan name does: "For one site and a small team," "For teams running several products."

Fix: under every plan name, write who it's for in plain words. A visitor should be able to pick their column before reading a single feature row.

3. Keep the choice small

NN/g's guidance on comparison tables is that people compare options feature by feature when there are only a few, and suggests a ceiling of about five. Most SaaS pricing pages work best well under that: three or four plans, with enterprise as a "talk to us" column.

Fix: if you have more than four self-serve plans, ask which ones people actually buy. Retire or hide the rest, or move add-ons out of the plan grid.

4. Treat plan order and the "recommended" badge as hypotheses

Speero's eye-tracking study of a survey tool's pricing page (Speero, 2016) found that participants spent the most time on the first two plans from the left, whatever those plans were. More of them picked the Pro plan when the expensive plans came first.

Read that with its limits, which the authors state: participants were given a scenario and weren't actually buying, and it was one product at one price range. It's a good reason to check where attention goes on your table. It isn't proof that reversing your plan order will work for you.

Fix: put the plan most buyers should choose where attention lands, mark it clearly, and check what real visitors look at and click before and after any change.

5. Explain the thing you charge for

Every SaaS price has a unit: seats, contacts, projects, tracked visitors, API calls. If a buyer can't tell how many of those they have, they can't tell what they'll pay. That uncertainty is a quiet reason people leave to "check with the team."

Fix: define the unit in one sentence next to the price, and link a short explanation. Then answer the follow-up question every buyer has: what happens if I go over? Say whether you cut service off, bill an overage, or suggest an upgrade, and at what price.

6. Spell out the billing terms next to the button

Buyers hesitate when they don't know what they're agreeing to. Before clicking, they want to know:

Monthly or yearly billing, and the price for each
Whether a trial needs a payment method, and when the first charge happens
Whether tax is added at checkout
How to cancel, and what the refund policy is

Fix: put one short line of terms under each button, and link the full details. Be literal. If a card is saved at signup, say so. A buyer who finds a surprise in checkout or on their statement is a refund request, a chargeback, or a bad review.

For an example, our own pricing page lists all three self-serve prices ($99, $249 and $499 a month), what counts as a visitor, what happens over the limit, and when the first charge happens.

7. Make the comparison table easy to scan

The feature table is where buyers check the one row they care about. NN/g's comparison table research lists the common failures: inconsistent values across columns, cute wording instead of plain values, long sentences in cells, and column headers that scroll out of view.

Fix:

Keep plans as columns and features as rows, with short values ("5 seats," not a sentence).
Make the column headers sticky on long tables.
Define unfamiliar terms with a tooltip or a link.
Show a short "at a glance" table first, with the full table behind a link or expander.
On phones, show two plans side by side at most, or switch plans with tabs.

8. Answer the objections in an FAQ under the table

Pricing page visitors often scroll past the plans looking for the catch. Use that. Answer the questions your sales team or support inbox hears most: contracts, cancellations, refunds, data handling, security reviews, discounts for nonprofits or startups, and how to change plans.

Fix: pull the last 30 pre-sale questions from your inbox, chat and sales calls, and answer the top five to eight under the table, in the buyer's words.

9. Put specific proof near the decision

A row of logos at the top of the page does less than one specific line from a customer near the plans. "We set it up in an afternoon and cut our review time in half" works better than "Great tool!", as long as it's real, attributed, and you have permission to use it.

Fix: put your most specific, believable proof between the plan grid and the FAQ. Match it to the plan when you can: a small-team quote near the small-team plan.

10. Give every plan one clear next step

Each column needs one button, labeled with what happens: "Start your trial," "Book a call," "Contact sales." If enterprise buyers need a conversation, give them a short form or a calendar link, not a dead end. Our guide to the demo request page covers what that page should include.

Fix: check that every button says what happens next, and that "talk to sales" leads to a page that books the conversation.

How to find which check is costing you

A pricing page usually has one or two real problems, not ten. Find them with evidence:

Exits. In your analytics, look at how many sessions end on the pricing page, and where those visitors came from.
Attention and scroll. Do visitors reach the comparison table and the FAQ? Do they look at the plan you recommend, or skip it?
Clicks that go nowhere. Repeated clicks on feature names or values usually mean people want a definition you didn't give them.
Toggle use. If many visitors flip between monthly and yearly billing and then leave, the yearly saving or the terms may be unclear.
Questions. What do prospects ask sales right after visiting pricing? That's the missing content.

Then fix the biggest issue first and measure it before and after. If your traffic is too low for an A/B test, our guide to CRO without A/B testing shows how to measure a change honestly.

The checklist (copy this)

Prices are public, or a starting price, range or typical scenarios are shown
Each plan has a one-line "for" statement
Three or four self-serve plans, at most five columns in total
The recommended plan sits where attention lands and is clearly marked
The billing unit is defined, with what happens over the limit
Billing period, trial terms, tax, cancellation and refunds are stated near the button
Comparison table: short values, sticky headers, defined terms, works on a phone
An FAQ under the table answers the top pre-sale questions
Specific, attributed proof sits near the plans
Every plan has one clearly labeled next step

Where Cortality fits

Most of these checks need an answer to one question: what do visitors actually look at, and where do they stop?

For a quick first look, our free page leak scan shows where your pricing page is likely losing buyers and what fixing it could be worth. It takes about a minute and needs no install. The scan is a prediction from our attention model, not data from your real visitors, so use it to decide where to look first. You see a first-screen attention prediction right away, and the full findings arrive by email a few minutes later.

For the rest of the path from homepage to signup, see Cortality for SaaS teams.

The paid product measures how real visitors use every part of your page, including which plan columns, table rows and FAQ items get attention, and ranks what to fix with the exact change for each. After you ship a fix, it re-measures to show whether it worked. See what a finding looks like.

Your first week is free, and you see your first report before you pay. You save a card at signup, and nothing is charged until 3 days after your first report. Cancel before then and you pay nothing, and any charge can be refunded within 14 days (refund policy).

FAQ

Should a SaaS company show prices on its pricing page?

In most cases, yes. NN/g's research with business buyers found price is their top information need, and HockeyStack's data found leads from pages with public prices became pipeline about 1.7 times as often. If prices really vary by customer, show a starting price or typical scenarios.

How many plans should a SaaS pricing page have?

Usually three or four self-serve plans plus an enterprise option. NN/g suggests comparison tables work best with about five options or fewer, and fewer is easier on a phone.

Should I list the most expensive plan first?

Maybe. One eye-tracking study found people spent the most time on the first two plans and chose a higher plan more often when it came first. But participants weren't really buying, so test it on your own page before changing the order.

What should go under the pricing table?

An FAQ that answers real pre-sale questions (contracts, cancellation, refunds, data and security), plus your most specific customer proof.