67% of B2B buyers prefer a buying experience with no sales rep in it, according to Gartner's survey of 646 buyers run in August and September 2025. For a software company, the website is where most of the evaluation happens, and where a security reviewer, a finance lead and an end user each look for a different answer.
This guide covers what changes when the product is SaaS: the readers, the proof they trust, the extra pages, compliance notes, benchmarks and a 90-day plan. It draws on published buyer research and our own check of 20 SaaS homepages on 13 November 2026.
What changes when a B2B website sells software
Our post on the nine decisions behind B2B website design applies to any B2B company. Software adds three conditions.
The buyer can try before talking. Trials, freemium tiers and interactive demos mean part of the audience wants to start, not to book a call. The site needs a path that ends in the product as well as one that ends in a calendar.
The buying group includes people who never see the homepage hero. Forrester's 2026 State of Business Buying reports 13 internal stakeholders and nine external participants on an average decision. G2 found IT involved in nearly 50% of purchase decisions, and about eight in ten buyers facing stricter reviews from security, legal and compliance teams when they evaluate AI software. Those reviewers land on the security page, the docs and the pricing page.
The shortlist is set early. 6sense's 2025 Buyer Experience Report found first contact at 61% of the buying process, down from 69% in earlier studies, with an average of five vendors evaluated and the top-ranked vendor chosen 77% of the time. TrustRadius found 83% of buyers shortlist three or fewer products.
The page map: what a SaaS site adds
Our B2B SaaS website playbook lists twelve page types. The table below is narrower: the pages a SaaS site adds to a general B2B page map, and who reads each.
| Page | Main reader | What it has to answer | Common miss |
|---|---|---|---|
| Pricing | Champion, finance | What it costs or how the price is built, what each tier includes | No page at all, so the visitor leaves for a review site |
| Integrations | End users, IT | Does it work with the tools we already run, natively or through an API | A logo wall with no detail per integration |
| Trust or security | Security reviewer, legal | Which reports exist, where data lives, how to request documents | A badge on the homepage and nothing behind it |
| Comparison | Champion | How it differs from the tool we use now, honestly | Pages that never admit a trade-off |
| Docs, changelog, status | Technical evaluator | Is the product real, maintained and up | Docs behind a login, changelog last updated a year ago |
| Customer stories | Champion, approver | Has a company like ours done this and what changed | Stories with no numbers and no named role |
Source: Octo Agency page map practice; readers drawn from Forrester 2026 and G2 2025 buying group findings
HockeyStack's 2025 analysis of 31 million visitors across 80 B2B SaaS companies found pricing pages draw 16.5% of all site traffic, against 0.91% for demo pages and 0.76% for case studies. TrustRadius reports that transparent pricing has been buyers' top request of vendors every year since 2023.
What 20 SaaS homepages link to
We fetched the server HTML of 20 B2B SaaS homepages on 13 November 2026, the set from our earlier homepage scorecard, and checked which page types they link to.
| Page type or signal | Homepages | Notes |
|---|---|---|
| Pricing link | 20 of 20 | Including sales-led products such as Okta and Docusign |
| Integrations, apps or marketplace link | 20 of 20 | |
| Customer stories link | 20 of 20 | |
| Trust, security or compliance page link | 18 of 20 | 14 point to a page or subdomain named trust or trust centre |
| Docs, help or developer link | 18 of 20 | |
| Status page or changelog link | 14 of 20 | |
| Comparison or "vs" pages | 9 of 20 | Outreach, Pendo and Snyk link several head-to-head pages |
| SOC 2 claimed on the homepage itself | 9 of 20 | Usually a badge row or a security band |
| G2 named on the homepage | 5 of 20 | Ratings or award badges |
Source: Octo Agency, one curl fetch of each homepage's server HTML and a link and text match, 13 November 2026. Sites: monday.com, ClickUp, Airtable, Zapier, Calendly, Klaviyo, Twilio, Brex, Lattice, Outreach, Apollo, Clay, Retool, Snyk, 1Password, Pendo, Okta, Smartsheet, Docusign, Productboard. A link in the footer counts.
Pricing, integrations and customer story links are table stakes. Security has moved out of the footer: nine of the 20 put SOC 2 on the homepage itself, and 14 point to a page or subdomain named trust or trust centre rather than a single policy page. Comparison pages are the real split. This is a small, well-funded sample, so read it as what mature SaaS sites do, not as a median.
Proof the SaaS audience trusts
We would rank proof in this order.
Reviews on a third-party site. TrustRadius's 2026 report found 74% of technology buyers use reviews to inform a purchase, and ranked user reviews alongside demos, free trials and prior experience as the most influential resources. A badge on your homepage matters less than reviews existing where buyers look.
Customer stories with a number and a role. HockeyStack, an analytics vendor reporting on its own customers' data, found visitors who read a case study before submitting a form are 18% more likely to become an opportunity. Case studies get only 0.76% of traffic, so put a short version of the story on the pricing and demo pages where the traffic already is.
Security evidence a reviewer can use. The AICPA describes SOC reports as CPA-issued reports on a service organisation's controls, covering categories such as security, availability, processing integrity, confidentiality and privacy. The trust page should say which report, the period it covers, how to request it, where data is hosted and which subprocessors you use.
Analyst badges, last. TrustRadius found only 13% of buyers used analyst reports, a 63% fall since 2022.
Compliance notes for the site itself
This is not legal advice. These points come up on almost every SaaS build.
Accessibility. WebAIM's 2026 analysis of the top million home pages found 95.9% with detectable WCAG failures and an average of 56.1 errors per page. Low-contrast text appeared on 83.9% of pages, missing alt text on 53.1% and missing form labels on 51%. WCAG 2.2, a W3C Recommendation since 12 December 2024, added nine success criteria, including target size and focus not obscured. The European Accessibility Act has been enforceable since 28 June 2025; a Travers Smith briefing describes its scope as mainly consumer products and services, including e-commerce, with partial relief for microenterprises. Most pure B2B SaaS marketing sites sit outside it, but enterprise procurement teams increasingly ask, so we would build to WCAG 2.2 AA from the start.
Cookie consent and tracking. If you sell into the UK or EU, analytics and ad tags need a consent decision before they fire. Plan the banner, tag rules and form tracking together.
Security claims. Every claim should match a document you can hand over. A SOC 2 badge shown while the audit is still running will come back in a security review.
The benchmarks to plan against
Our post on B2B SaaS website conversion rate statistics covers the funnel. These are the numbers we would put in a project brief.
| Measure | Figure | Source |
|---|---|---|
| Whole-site visitor-to-form rate | 1.1%, about one form per 91 visitors | HockeyStack, 80 B2B SaaS companies, 2025 |
| Pricing page share of traffic | 16.5% | HockeyStack, 2025 |
| Pricing page conversion | 3.8% average; 2.8% transparent, 4.6% non-transparent | HockeyStack, 2025 |
| Form to pipeline | 17.5% transparent pricing, 10.31% non-transparent | HockeyStack, 2025 |
| Demo page conversion | 5.5% | HockeyStack, 2025 |
| Good Largest Contentful Paint | 2.5 seconds or less at the 75th percentile | web.dev, Google |
| Good Interaction to Next Paint | 200 milliseconds or less | web.dev, Google |
Source: HockeyStack, The State of Pricing, Demo and Case Study Pages, December 2025 (vendor data from its own customers); web.dev, Web Vitals
Hiding the price raises the form rate and lowers the share of forms that become pipeline, so the two models end up close. Measure pipeline, not form fills.
What to skip
Gating shortlist facts. Pricing logic, security summaries and integration detail should be open.
A hero that only says AI. Name the category and who the product is for.
A microsite per persona. Different readers need different pages, not different sites.
Carousels. Rotating quotes hide proof most visitors never wait for.
A chat pop-up on the security page. Reviewers want documents, not a sales conversation.
A 90-day plan for a SaaS site redesign
Days 1 to 30: baseline and page map. Record the current numbers: visitor-to-form rate, pricing page share, form to pipeline, field Core Web Vitals. Ask sales and security which questions slow deals. Write the page map with the pages from the first table, and draft the trust page content with whoever owns compliance.
Days 31 to 60: build. We run a four-week marketing-site process and build marketing sites in Webflow, with product and app work in Next.js. A typical sequence: strategy and copy in week one, design in week two, build in week three, QA, accessibility checks and tracking in week four. Integration and comparison pages go into the CMS.
Days 61 to 90: measure and test. Compare the first 30 days against the baseline on the same definitions. Run the first test on the pricing page, where the traffic is.
What this means for a SaaS marketing lead
The design work that matters most on a SaaS site is a pricing page that explains the price, integration pages with detail, a trust page a reviewer can use and customer stories where the traffic already goes. Our marketing websites service page explains how we scope a SaaS site.


