SaaS website best practices: what 20 B2B SaaS pricing pages do, and the pages your site needs

The short answer

A SaaS website has to serve three visitors at once: the user who wants to try the product, the buyer who needs a price, and the reviewer who has to approve security and spend. A good SaaS site gives each of them a path that doesn't require a sales call.

On 17 October 2026 we read the pricing pages of 20 well-known B2B SaaS products. The typical page shows four plans, two of which you can buy without talking to sales. 15 of the 20 offer a free plan, 15 end with an enterprise "contact sales" card, 12 badge one plan as the most popular, and all 12 pages with a monthly/annual switch open on annual. Their homepages are just as consistent: 19 of 19 link to customer stories, and 18 link to a security or trust page.

The rest of this guide shows the data, what to copy, the pages a SaaS site needs, and the mistakes we found on pages from companies that can afford to get them right.

What 20 SaaS pricing pages do

We read each page on 17 October 2026, logged out, in English, in US dollars. Where the HTML didn't contain the plans, we read the page in a browser. We counted what a visitor sees on the main view: plan cards, free plan or trial, the billing switch and the saving it claims, badges, the enterprise card, the pricing unit, the comparison table, the FAQ, compliance claims and calculators.

The counts across all 20:

Two caveats. Intercom was running a live price test while we read it: some visits showed its Essential plan at USD 29 with "Save up to 26%", others at USD 19 with "Save up to 35%". And a few pages differed between our logged-out copy and a browser, so treat single details as a snapshot of one day.

What to copy for your own pricing page

Four cards, two you can buy

Free, two paid plans and Enterprise is the default for a reason: one plan to start, one to grow into, and one for procurement. Pipedrive is the exception that sells four self-serve plans, and Linear shows how little a page needs: four cards and a comparison table, with no badge, no trial and no FAQ.

Choose a free plan or a trial on purpose

The five products without a free plan are mostly seat-priced team tools sold to a manager, and four of them offer a 14-day trial instead. If your product only shows its value once a team is set up, a trial with a deadline usually fits better than a free plan nobody upgrades from. Say what the trial needs: Pipedrive repeats "No credit card required" under every button.

Default to annual, and show the arithmetic

Every switch we saw opens on annual billing, so the headline is the per-month equivalent of a yearly price. The real discount is usually about 17%, the same as paying for 10 months out of 12 (Notion USD 10 against 12, Zoom USD 14.16 against 16.99, Airtable USD 20 against 24). Pipedrive also prints the yearly total under the monthly figure ("One payment of US$ 168 per seat/year"), which saves a buyer the multiplication their finance team will do anyway.

Mark one plan, and put a floor on Enterprise

All 12 badges sit on a self-serve paid plan, usually the second or third card. GitHub runs two badges at once, "Most popular" on Team and "Recommended" on Enterprise. On the enterprise card, a starting price filters out buyers who can't afford it: Calendly shows Enterprise "Starts at $15k /yr", GitHub "Starting at $21" a user, and Figma publishes its Enterprise seat prices even though the button says "Contact sales".

Price AI where buyers can see it

9 of the 20 pages meter AI in its own unit, such as credits, requests or resolutions. Notion sells credits at USD 10 per 1,000, Intercom charges USD 0.99 per AI outcome, Asana sells AI requests, and Zendesk bills AI agents per automated resolution. If your product meters AI, put the unit and its price on the pricing page rather than in the terms.

Answer objections on the page

17 pages end with an FAQ, with a median of 12 questions: refunds, seat changes, discounts for nonprofits and startups, what counts as a user. Slack's FAQ explains that only active members are billed. Those answers are what a buyer forwards to a finance or procurement colleague.

Show where single sign-on starts

Security claims on pricing pages are mostly rows in the comparison table. What buyers look for first is single sign-on, and it is rarely in the first paid plan: Notion and Miro put it on Business, Asana and Linear on Enterprise, and Vercel sells SAML single sign-on on Pro for USD 300 a month. Make the row easy to find, because an IT reviewer will search for it.

Add a calculator only when price depends on usage

The four calculators all belong to products priced by events, volumes, contacts or AI resolutions. A seat-priced product doesn't need one: the price is the seat count times the plan.

Make the page readable to machines

Postman's pricing page tells AI agents that a clean Markdown copy of the page lives at /pricing.md, and the file is there. Assistants increasingly answer "how much does X cost", so a plain-text version of your prices helps them quote you correctly. Our notes on building an agent-ready website cover the rest of that work.

The pages a SaaS site needs

We also checked what each company links from its homepage. Gusto's homepage blocked our request, so this covers 19, counting links in the homepage HTML; menus that load later with JavaScript may hide more.

Figma has a security page at figma.com/security; we just didn't find a link to it in its homepage HTML.

Beyond those six, three pages carry most of the remaining weight:

• Product or features pages, one per job the product does. Not a list of features: what the buyer can stop doing, with screenshots of the real interface.
• Use cases or solutions by role and industry. This is where B2B navigation does its segmenting. In our B2B website examples, 9 of 12 sites had an industry menu, and 4 also organized by role or department.
• Docs and an API reference for any product with integrations. Evaluating engineers read docs before they read marketing pages.

Comparison pages are the least common and among the most useful for buyers who already have a shortlist. They're legal in the US: the FTC's policy statement says it encourages naming competitors, as long as comparisons are truthful, clear and not deceptive (16 CFR 14.15). Slack, Pipedrive, Mixpanel, Zendesk, Mailchimp and 1Password all run them.

For the security page, add a /.well-known/security.txt file. RFC 9116 defines it as a machine-readable way to tell researchers how to report a vulnerability:

Contact: mailto:security@example.com
Expires: 2027-10-17T00:00:00.000Z
Policy: https://example.com/security/disclosure
Preferred-Languages: en, es

If customers can bring their own domain to your product, the trust page should explain how that works too; our guide to custom domains for SaaS covers the set-up.

Signup and demo flows

The buttons on the paid cards split into three camps: "Get started" (6 pages), trial wording such as "Start free trial" or "Try it free" (7) and "Buy now" (4). There's no single right label; match it to what happens next. "Try it free" should lead to a working product, not to a form that schedules a call.

The strongest B2B flows we saw put both paths side by side:

• Stripe pairs instant signup with a "Contact sales" form whose first step asks only for a work email and a country.
• Snowflake puts "Contact sales" and "Start for free" next to each other in the header.
• Supabase leads with "Start your project" and keeps "Request a demo" as a four-field form.
• CrowdStrike lets a buyer book a meeting after giving a business email and country, then shows open times.

The forms that ask more up front, nine fields at Snowflake and Veeva, belong to companies with long enterprise sales. If you sell to smaller teams, ask for the minimum and qualify later.

Measure each path separately: trial started, trial activated, demo booked, demo held. Our comparison of PostHog and Google Analytics covers which tool tracks product activation and which tracks the website.

Proof that convinces buyers

What the 20 pricing pages and the homepages behind them use, in order of how specific it is:

1. Numbers from named customers. "Customer X cut Y by Z%" with the customer's name and a link to the full story beats any logo.
2. Customer logos right under the hero, where a visitor checks whether companies like theirs use the product.
3. Security evidence: certifications, a trust center and a way to request a SOC 2 report.
4. Review-site ratings and quotes from named people with their titles.

Keep every claim real. The FTC's rule on consumer reviews and testimonials (16 CFR Part 465) makes it a violation for a business to create or sell reviews or testimonials that misrepresent whether the reviewer exists or used the product, and it covers insider reviews and review suppression too. If you don't have customer numbers yet, use a detailed description of how the product works, and add stories as they come. This is general information about US rules, not legal advice.

Mistakes we found on big-company pages

• A saving that the prices don't support. Notion's switch says "Save up to 20% with yearly", but both paid plans work out to 16.7% (USD 10 against 12, USD 20 against 24). Pipedrive and Zendesk make the opposite error and claim less than they give. Compute the figure from your own prices.
• Two numbers for the same thing. Mailchimp's pricing page gives the free plan's limit as "Under 250 contacts" in the plan column and "fewer than 500 contacts" a few lines away. Every number on a pricing page should come from one source.
• Intro prices without the full price beside them. GitHub's Team plan says USD 4 a user "for the first 12 months*", and we found no footnote for the asterisk in the page. Mailchimp shows "Save 50%" for 12 months, then the full price. Slack offers 50% off for 3 months on monthly billing. Put the regular price next to the promotional one.
• A security page nobody can find from the homepage. Figma has one; its homepage HTML doesn't link to it.
• Pages that only work for one kind of visitor. A pricing page with no enterprise route loses procurement; a site with no docs or changelog loses the engineer who has to approve the integration.

If your conversion problem is somewhere between the pricing page and the signup, our conversion rate optimization service starts with a review of exactly these pages.

What to do next

1. Put your pricing page next to the counts table above and note every pattern you don't follow. Each should be a decision, not an accident.
2. List the six homepage links from the pages table and check which ones your site is missing.
3. Turn the result into a brief with our website RFP builder, whether you rebuild in-house or hire someone.

If you want Dardo to design or rebuild the site, see our SaaS website design and B2B website design services. And if AI assistants should be able to use your product, not just read about it, start with our guide to MCP servers for SaaS.