What should a SaaS product page say above the fold?

Who the product is for, what it concretely does, proof that it works for people like the reader, and one clearly labelled way to try it. Vision, founder story and roadmap can live further down the page.

Why should I avoid the word platform on my website?

Investors read it as expansion potential, but buyers read it as vague, expensive and hard to implement. Replace it with the specific thing the product does for the specific person reading the page.

Should a startup put its founder story on the homepage?

It can be on the site, and it can be on the homepage, but not first. A buyer needs to know what the product does and whether it fits their situation before they care why you built it. Lead with the buyer, then tell your story.

What should a call-to-action button say on a product page?

Exactly what will happen when it is clicked and roughly how long it takes: book a twenty-minute demo, start a thirty-day trial with no card, or see pricing. Generic labels like get started or contact us leave the buyer guessing and cost you people who were ready to act.

Why your product page reads like your pitch deck, and why that’s a problem

Two documents, two readers

A pitch deck has one reader: an investor who is deciding whether a market is big, a team is credible and a timing is right. The deck sells a thesis. It leads with the size of the problem, describes the product in a slide or two, and spends the rest of its length on why this company, why now, and how far it could go.

A product page has a different reader entirely. It is one person, with one job, who has a specific problem this week. They are not evaluating your market. They are evaluating whether you are better than the spreadsheet, the incumbent tool or the intern they use today, and whether switching is worth the disruption. They will give you a few seconds on the first screen before deciding.

These two readers want almost opposite things. The investor wants breadth and ambition. The buyer wants narrowness and certainty. A page written for one will fail the other, and after a round closes, the deck’s language is what everyone on the team has memorized. So it ends up on the website.

The tells

You can usually spot a product page that was written from a deck in the first scroll. Look for these:

Market-size language. “A large and growing category,” “a massive opportunity in an underserved market.” No buyer has ever cared how big your market is. It tells them you are talking to someone else.
“Platform.” Investors like platforms because they imply expansion. Buyers hear it as “does many things vaguely, probably expensive, probably needs an implementation project.”
Transformation verbs. Revolutionize, reimagine, transform, unlock, empower. Each one is a space where a specific verb should be.
The founder story above the fold. Why you started the company is a fine thing to have on the site. It is not the first thing a buyer needs, and when it leads, it signals that the company is still the hero of the story.
Vision before function. “The future of field operations” as a headline, with what the product actually does revealed three screens later, if at all.
Logos of partners and investors where customer proof should be. Who funded you is deck material. Who uses you is page material.

We see this pattern on software company sites across Atlantic Canada, and it is not a sign of bad writing. It is a sign that the website was written in the same month as the raise, by the same people, with the same document open.

What a buyer needs in the first screen

The first screen of a product page has to answer four questions, in roughly this order, without scrolling on a laptop and with one scroll on a phone.

Who is this for? Named plainly enough that the right reader thinks “that’s me” and the wrong reader leaves without wasting either of your time. Naming the role and the situation does both.
What does it do? A concrete verb and a concrete object. It schedules crews. It reconciles invoices. It tracks compliance evidence. Not what it enables, what it does.
Proof it works. A named customer, a specific outcome in that customer’s words, or a screenshot of the actual product doing the actual thing. Not a logo wall with no context.
How to try it. One action, clearly labelled with what will happen when they click it. “Start a free trial, no card” or “Book a twenty-minute demo” or “See pricing.” Not “Get started,” which could mean anything.

Everything else (the story, the roadmap, the vision for the category) belongs further down or on another page. It can stay. It just cannot go first.

A rewriting exercise

Take an invented product to make this concrete: a piece of software for independent trucking companies that handles driver hours, inspection records and the paperwork regulators ask for. Call it Haulbook. Here is the kind of first screen it would have if it were written from the deck:

Before: “Haulbook is the intelligent fleet compliance platform revolutionizing how transportation companies manage risk. Founded by industry veterans, we’re building the operating system for the next generation of logistics. Get started today.”

Every tell is present. Platform, revolutionizing, operating system, founder credentials, a call to action with no stated outcome. A dispatcher at a twelve-truck operation outside Moncton reads this and learns nothing about whether it will help her with the inspection audit next month.

Here is the same product, written for her. After:

Driver logs, inspection records and audit paperwork for small trucking fleets, in one place. Haulbook replaces the binder and the spreadsheet so you can pull a clean record for any truck or driver in under a minute. Used by fleets of five to fifty trucks across the Maritimes. Book a twenty-minute walkthrough, or start a free thirty-day trial with no card.

Notice what changed. The audience is named (small trucking fleets). The function is concrete (logs, inspections, audit paperwork in one place). The status quo is named (the binder and the spreadsheet). The proof is specific to her situation (fleets like hers, in her region). And the action tells her exactly what she gets if she clicks.

Notice also what did not change: nothing about the product. The rewrite required no new features, no new design and no new photography. It required deciding who the page was for.

Do it to your own page

Print your homepage. Cross out every sentence that could appear in a deck without edits. What is left is your starting material. If nothing is left, start with the four questions above and write one sentence for each.

The “what happens next” problem

There is a second failure that often rides along with the first. The buyer reaches the end of the page, is interested, and cannot tell what will happen if they act. “Get started” could mean a signup form, a sales call, a waitlist or a credit card. “Contact us” could mean a reply tomorrow or a reply never.

Uncertainty here costs you people who were ready to move. Fix it by stating the next step and its cost in time: “Book a demo: twenty minutes, we’ll show you your own data.” “Start a trial: full product, thirty days, no card, cancel in one click.” “Request pricing: we reply the same business day.” Then make sure that is actually what happens, because the first broken promise is also the last.

For companies selling outside the region, which is most software companies in Atlantic Canada, this matters more than it would locally. A buyer in Calgary or Chicago has no relationship with you and no reason to extend you the benefit of the doubt. The page is the whole relationship until the first call.

What to do first

Open your homepage and your pitch deck side by side. Highlight every phrase that appears in both. Those phrases were written for an investor, and they are now the first thing your buyers read. Rewrite the first screen using the four questions (who it is for, what it does, proof it works, how to try it), name the thing you replace, and make the button say what will happen when it is clicked. Leave the rest of the site alone until that screen is right.