What Pages Does a SaaS Marketing Website Need at Launch?

A new SaaS product doesn't need a 30-page site. The pages that matter at launch, what goes on each, and what can wait.

At launch, a SaaS marketing website needs five to seven pages: a homepage, a product page, pricing, a sign-up or demo page, one page for your main use case, an about page and the legal pages. Everything else can wait until you know what visitors ask about.

The short answer

  1. Homepage
  2. Product or features
  3. Pricing
  4. Sign-up or book a demo
  5. One use-case or audience page
  6. About
  7. Privacy policy and terms

What goes on each page

Homepage

Say what the product does and who it's for on the first screen, in plain words. Then show the product: a screenshot or short video of the real interface. Add the one or two problems it solves, any proof you have, and one main call to action that repeats down the page.

Product or features

Group features by the job they do for the user. Each group gets a short heading, two sentences and a screenshot. If you have three features, one page is enough.

Pricing

Show your plans, what each one includes, and what happens after a free trial. If you sell on custom quotes, say so and explain what the price depends on. Visitors who find no pricing at all often go and compare with a competitor who shows some.

Sign-up or demo

Keep the form short. Ask only what you need to create the account or book the call. If there is a sales call, say what happens on it and how long it takes.

One use-case page

Pick the audience or use case most of your early customers share, and write one page for them in their own words. It's the page you send in outreach, and it often ranks for longer searches before your homepage does.

About

Who the founders are, why the product exists, and how to reach you. Early buyers are choosing the team as much as the product.

Privacy policy and terms

You need both before you take payments or collect personal data.

What can wait

  • A blog, until you have something to publish every month
  • A separate page for every feature
  • Integration directories, comparison pages and a help center
  • Case studies, until customers agree to be named

Add these once you see what visitors search for and what sales calls keep asking about.

Common mistakes

  • Writing about the technology instead of the user's problem
  • Showing abstract illustrations instead of the product
  • A different call to action in every section
  • Launching the site months before or after the product

Build the site and the product together

The marketing site and the product should look like they come from the same company. When one team designs both, the brand, the screenshots and the sign-up flow line up, and the site can go live the same week as the product.

If the product isn't built yet, our Zero to MVP sprint covers discovery, brand, product design and a deployed product in four weeks, so the site has a real product and brand to show from launch day. If your product is already live and the site needs work, read What makes a great website for a B2B SaaS product.

FAQ

How many pages does a SaaS website need at launch?

Five to seven: home, product, pricing, sign-up or demo, one use-case page, about, and the legal pages. Add more once you know what visitors look for.

Should an early-stage SaaS show pricing?

If you can, yes. Even a starting price or a short explanation of what the price depends on helps visitors decide whether to sign up or book a call.

Do I need a blog at launch?

No. Start one when you can publish regularly on questions your customers ask.

Building a new product? See how Zero to MVP works.

Hitomi Abiko

Author

Hitomi Abiko

Read More