Key takeaways
- A seed-stage B2B SaaS site needs five to seven pages: homepage, product, pricing or demo, about, one proof page and the legal basics.
- After Series A, add pages for buyers who aren't ready for a demo: solutions by role or industry, integrations, customer stories and a security page.
- Every page should answer one question a buyer asks before talking to sales. If you can't name the question, the page doesn't belong in the sitemap.
- Show at least how pricing works, so buyers don't have to guess what you cost before they book a demo.
- Build repeating pages as CMS templates. Kolibri's marketing published 30+ ebooks and articles in under 8 months with no developer.
What pages should a B2B SaaS website have?
A B2B SaaS website needs pages that answer the questions buyers ask before they talk to sales: what it does, who it's for, what it costs, whether it works and whether it's safe. The number of pages grows with your stage, but those questions don't change.
This is how the structure typically grows:
My note: When I plan a SaaS sitemap, I start from the questions a buyer asks before a demo, not from the pages competitors have. Every page has to answer one of those questions. If we can't name the question, the page doesn't go in.
We've built sites for 100+ startups across fintech, SaaS and AI, including US SaaS and AI teams like Sessionboard, GovOS and Personal AI. That's why we start every sitemap from buyer questions, not from a competitor's navigation.
What does a seed-stage SaaS website need?
Five to seven pages, each doing one job. At seed, the site has two readers: investors checking whether the company is credible, and early customers checking whether the product solves their problem.
- Homepage: what the product does, for whom and the main result, in the first screen. Then how it works, proof and one clear call to action.
- Product or “How it works”: the three or four things the product does, shown with real screenshots or short demos, not abstract illustrations.
- Pricing or “Book a demo”: even without public prices, explain how pricing works and what a demo includes.
- About: the team, why you started and who backs you. At seed, the team is part of the product.
- One proof page: a customer story, pilot results or logos with a quote. One real story beats a page of logos.
- Legal: privacy policy and terms. Enterprise buyers check them during procurement.
Our Launch projects for early-stage teams are built around this logic: a sharp site that goes live from 3 weeks and makes investors and first customers take the company seriously. Centinel, an AI accounting startup, launched that way in 3 weeks and booked 5 enterprise leads in its first month.
What should you add after Series A?
Pages for buyers who aren't ready for a demo yet. After a Series A, the sales team grows, buying committees get bigger and more people research you before anyone fills in a form.
- Solutions pages by role, industry or use case, so a finance lead and an IT lead each find their own reason to buy. Build them as one CMS template, not one-off pages.
- Integrations: a page or a CMS collection listing the tools you connect with. Buyers want to know the product works with the tools they already use.
- Customer stories: a library filtered by industry or company size, with a number in every story.
- Security: certifications, data handling and who to contact. This page shortens security reviews. Our guide to fintech website design shows how trust pages work in a regulated market.
- Blog or resources: content that answers buyer questions and brings in search traffic between campaigns.
This is the stage our Transform projects are built for: a site of 8 to 20 pages on one shared design system, delivered from 8 weeks, that the marketing team runs on its own afterward.
What does a growth-stage SaaS website add?
Pages that win against competitors and in new markets. By Series B, buyers compare you with two or three alternatives, and the site has to help them choose.
- Comparison pages (“Your product vs Competitor”) that are honest about where each option fits. They answer a question buyers search for and AI assistants are often asked.
- A trust center that grows from the security page: certifications, uptime, subprocessors and policies in one place.
- Localized pages for new markets, starting with the homepage, pricing and key solutions pages.
- Careers, because candidates research the company as carefully as buyers do.
At this stage, the website is a product with its own backlog. Long SaaS partnerships, like our 2+ years with Sessionboard, an event tech company in Florida, are ongoing work rather than one-off builds, because a growth-stage sitemap is never finished.
Should a B2B SaaS website show pricing?
Yes, at least how pricing works. When a site shows no pricing information at all, buyers have to guess, and the guess rarely works in your favor.
You don't need every number on the page. Pick the level that fits your sales motion:
- Self-serve or product-led: show full prices and plans.
- Sales-led with a clear entry point: show a starting price and what drives the cost, like seats, usage or modules.
- Enterprise only: explain what's included, how pricing is calculated and what a typical rollout looks like, then offer a call.
The worst option is a “Contact sales” button with nothing else. It answers no question and filters out no one.
What are the most common B2B SaaS website structure mistakes?
Most structure problems come from adding pages without a reason or building them in a way nobody can maintain. These are the ones to check first:
- Copying a competitor's sitemap. A larger competitor's navigation reflects its sales team, its markets and its history. Copy it and you get pages without content and menus that hide the one thing your buyers need.
- Splitting features across too many pages too early. At seed, a buyer has to click through five feature pages to understand one product. One clear product page does the job better until each feature has its own buyers.
- Building solutions pages as one-off designs. Every role or industry page gets its own layout, so adding the next one means a new design and a developer. Build one template and fill it from the CMS.
- Treating the security page as an afterthought. It goes up the week a large customer asks for it, with whatever the team can write in a day. A simple page with your certifications, data handling and a contact person saves time in every security review that follows.
- Letting the navigation grow by addition. Each new page gets its own menu item until the header has nine links. Group pages under clear menus like Product, Solutions and Customers, and review the navigation every time you add a section.
Our tip: Before adding any page, write down the buyer question it answers and the page that currently answers it, if any. If an existing page already does the job, improve that page instead of adding a new one.
How should a SaaS site be built so marketing can add pages?
Build the structure as templates and components, not as a fixed set of pages. Most of the pages that come after Series A repeat: solutions, integrations, customer stories, comparisons. Each should be a CMS collection with one template, so a new page takes a form and an image, not a developer.
In Webflow, that means:
- CMS collections for every page type that repeats, with fields marketing understands.
- A component library that marketing can combine into new landing pages without breaking the design.
- Navigation that can grow, with a Solutions or Product menu ready for more items before you need them.
- SEO built into the templates, including titles, descriptions and schema bound to CMS fields.
Webflow is pushing further in this direction with Source, its new platform where marketing teams and AI agents build and run the site together. It's still in limited preview, and in our guide to Source by Webflow we cover what it could change for SaaS marketing teams.
The return shows up after launch. On Kolibri, we set up a modular CMS and visual system, and the marketing team published 30+ ebooks and articles in under 8 months without a developer. Across our handoffs, teams see up to 40% fewer developer tickets, because marketing can publish and edit on its own.
How do you plan the structure for your next stage?
List the questions your buyers ask before a demo, check which ones your site answers today, and add pages only for the gaps. At seed, keep it to 5-7 pages that explain the product and prove the team. After Series A, add solutions, integrations, stories and security as CMS templates. At growth stage, add comparison, trust and localized pages.
If you're planning the structure for your next round, our SaaS website team builds it in Webflow, from the sitemap to a CMS your marketing team runs on its own.
