How to structure a SaaS website

A SaaS website needs a home page that names the user and the outcome, a page for each main use case, a pricing page with plain numbers, an integrations page, real customer proof and docs. Pick one call to action, a trial or a demo, to match how you sell.

Many SaaS sites grow one page at a time. A page is added for every feature and a menu item for every page, and a visitor who wants to know whether this is for them has to dig. A planned structure fixes that before the site gets large.

01. Which pages does a SaaS site need?

A small team can launch with a fraction of this: home, one or two use case pages, pricing, an about page and a contact or demo page. Add the rest as customers ask for it.

02. What belongs on the home page?

1. A headline that names the user and the outcome, such as who it is for and what changes for them.
2. One line on how it works.
3. Proof: real customers, real numbers you can back up, or a clear statement of what happens when someone starts.
4. Three or four outcomes, each tied to a use case page.
5. A pricing teaser.
6. The one call to action, repeated.

Lead with what the product does for the user. A list of features is easier to write and harder to understand.

03. How should the menu work?

Keep the main menu to five or six items: Product, Pricing, Integrations, Customers and Resources, with the call to action as a button. Put everything else in the footer. Fewer choices make the next step clearer.

Pick the call to action to match how you sell. A self serve product usually offers a free trial. A product with a longer buying process, a higher price or a team decision usually offers a demo. Showing both on every page splits attention.

04. What does a good pricing page do?

Visitors who leave the pricing page with unanswered questions rarely come back. Show plans in plain numbers, say who each plan is for, list what is included and what is not, and answer the questions people always have: billing, cancelling, limits, security and support. Where prices depend on usage, explain how and give an example.

If you cannot publish a price, say what drives it and how to get one fast. A page that says only Contact us invites a quick exit.

05. How do you keep trial users engaged?

Many sign ups stop after the first visit. Plan the first week: a welcome message, one clear first step, a follow up that offers help, and a nudge when someone stalls. An assistant built on your documentation can answer product questions during the trial, using only the pages you have approved, and send anything else to your team.

06. How do you get named by AI tools?

When people ask an AI tool for software in your category, you want to be in the answer and not a competitor. Say clearly what the product does and who it is for, publish honest comparison pages, keep your pricing public, and be present on the review and directory sites your buyers read. Our post on getting recommended by AI chatbots covers the full list.

07. Which mistakes show up most often?

• A headline full of jargon.
• Feature lists with no outcomes.
• Pricing hidden behind a form.
• Logos or reviews the company cannot back up.
• A sign up form that asks for too much.
• A menu that mirrors the org chart.

Frequently asked questions

How many pages should a SaaS site have?

As many as your buyers need and no more. On our SaaS page we show CredBlaze, a task and rewards platform, with a 15 page marketing website. A new product can start with five or six. If you are still shaping the product itself, read how to scope an MVP first.

Should the call to action be a trial or a demo?

A trial suits self serve products. A demo suits higher priced products with a longer buying process. Choose one as the main action.

Do I need a blog?

Only if you will publish useful articles regularly. A neglected blog hurts more than none.

Will a help assistant answer only from our documentation?

Yes. It answers from the pages you approve and routes everything else to your team.