← All articles

SaaS Homepage Mistakes That Make Products Harder to Understand

A SaaS homepage has one job above all others: help a new visitor understand what the product is, who it's for, and where to go next. Most of the confusion I see comes from pages that were built around the company's own view of the product instead of the visitor's first impression.

Why the homepage is so easy to get wrong

The homepage gets pulled in every direction. Founders want investors to take it seriously, sales wants demos, marketing wants a campaign message, and the product team wants every feature visible. The result is a page that says a little about everything and nothing clearly.

Government usability guidelines for homepages advise communicating the site's purpose and value clearly and prominently, because most visitors spend little time on any one site and shouldn't be expected to dig for its purpose. Nielsen Norman Group's reading research points the same way: visitors scan and read only part of a page. The mistakes below are the ones that most often break those two ideas.

Seven mistakes and how to fix them

1. The hero names a category but not the product's job

"The modern platform for customer success" tells a visitor which shelf you're on, not what you do on it. Fix it by writing the hero as a situation and an outcome: who has the problem and what changes.

Illustrative example, not client copy
Weak

The platform for customer success teams.

Stronger

Spot customers about to churn while there's still time to call them.

2. The logo wall comes before the visitor knows what you do

Customer logos are useful proof, but only after the visitor understands what they're being told your customers use. Put the explanation first, then the logos, and pair them with a specific statement rather than a vague "trusted by" line. Only show logos you have permission to use.

3. A feature grid of vague labels

Twelve icons labeled "Seamless", "Powerful" and "Flexible" explain nothing. Replace each label with a plain description of what the feature lets someone do. If you can't describe the benefit in a sentence, the feature probably doesn't belong on the homepage.

4. Internal vocabulary

Teams that live inside a product start using its terms as if everyone knows them: "workspaces", "boards", "flows", "signals". A new visitor doesn't. Use words from your customers' own reviews and support conversations, and explain a product-specific term the first time it appears.

5. Speaking to every role at once

A homepage that tries to convince the end user, the manager, the IT reviewer and the executive in the same hero convinces none of them. Pick the primary audience for the homepage. Give the others their own sections or pages, such as "For admins" or "Security."

6. Abstract art instead of the actual product

Illustrations of floating shapes and gradients don't help a visitor picture using the product. Show real screens with a short caption of what's happening in them. On Flowdesk, I led the page with a view of the product itself rather than a stock image, so visitors could see the work they'd actually be doing.

7. Competing calls to action

"Get started", "Book a demo", "See pricing" and "Contact sales" all given the same weight make the visitor choose before they know enough to choose. Decide the primary action, make it the most visible button on the page, and let the rest be quieter links.

What about pricing?

Not every SaaS product can list a price, and for complex enterprise products "contact us" is often accurate. But a visitor who can't find any hint of cost or fit will often assume the product isn't for them. Even without a number, you can explain who the product is priced for, what drives the price, and what happens after they get in touch.

A homepage review checklist

  1. Can someone outside the company describe the product after looking at the top of the page for five seconds?
  2. Does the hero name a situation or outcome rather than a category?
  3. Are all product terms either plain or explained?
  4. Is it clear who the homepage is for?
  5. Is there a screenshot or demo of the real product?
  6. Is one action clearly the main one?
  7. If you read only the headings, does the page still tell a story?

If you answered "no" to more than two, start with the hero. A clearer first screen usually does more than adding sections lower down.

Fix the order, not just the words

Many homepages aren't short of good material. They have the right content in the wrong sequence. A simple order that works for many SaaS products is: what it does and for whom, the problem it solves, how it works in three steps, proof, objection handling, then the next step. Rearranging existing sections into that order is often a faster win than rewriting everything.

A note on the evidence: these usability studies are decades old and measure how people behave on pages, not how any one page will convert. Use them as direction, then test your own page. Your numbers will differ.

Sources

  1. U.S. Department of Health and Human Services (2006). Research-Based Web Design & Usability Guidelines, homepage chapter (archived copy).
  2. Nielsen, J. and Morkes, J. (1997). Concise, SCANNABLE, and Objective: How to Write for the Web, and Nielsen, J. (1997). How Users Read on the Web, Nielsen Norman Group.
  3. Nielsen, J. (2008). How Little Do Users Read? Nielsen Norman Group.

Need this done on your own site?

If your homepage needs a rewrite, see my website copywriting and SaaS copywriting.

Talk before the project →