SaaS landing page sections that convert

Every list of SaaS landing page sections we found is a list of shapes: hero, logos, features, testimonials, pricing, FAQ, CTA. Copy the shapes and you get a page that has everything and convinces nobody, which is precisely the page a coding agent builds when you ask it for a landing page.

The shapes are downstream of something else. A visitor arrives with a sequence of doubts, they arrive in a fixed order, and a section exists to kill exactly one of them. Get the sequence right and the shapes fall out of it. Get it wrong and no amount of polish helps, because the page is answering questions the reader has not asked yet.

The sequence

1. "What is this?" — the first three seconds, and the only job of the first screen.

One sentence that names the thing and the change it produces, in the reader's words rather than the category's. Deploy previews for every pull request is an answer. The modern platform for engineering velocity is a category, and a reader who cannot tell what you sell leaves before objection two exists. Directly under it: one primary action, and one image or short loop showing the product doing the thing. Not an abstract illustration — the product.

2. "Is this for someone like me?" — the immediate second doubt, and the most-skipped section.

This is what the logo strip is really for, and why an unrecognised logo strip does nothing: the visitor is looking for themselves, not for prestige. Naming the situation works better than borrowing authority — "if you are a two-person team shipping to production daily" identifies the reader more reliably than six grey logos they do not know.

3. "What does it actually do?" — now, and not before.

Three to five capabilities, each shown rather than asserted. The failure mode is universal and worth naming: a grid of nine cards, each with a rounded-square icon, a two-word title and a line of filler. Nine equal cards is the visual statement that you could not decide which capability matters. Three unequal ones say you could.

4. "How is it different from what I'd otherwise do?" — the comparison the reader is running anyway.

They are comparing you to a competitor, to a spreadsheet, or to doing nothing. Doing nothing is usually the one that wins, and it is the one almost no page addresses. If you name the alternative honestly, including where it is genuinely fine, you get the credit for the honesty and the comparison happens on your terms.

5. "Do I believe you?" — proof, and this is where most pages break the law.

A testimonial with a full name, a role, a company and a specific outcome is proof. A star rating and a first initial is decoration, and an invented one is a false review — in the EU that is a banned commercial practice under Annex I of the Unfair Commercial Practices Directive, transposed into national law across the bloc, not a growth tactic with a grey area. If you have no customers yet, say what you have: a public changelog, an open repository, a live demo, your own numbers about your own product. Absence of proof handled honestly costs far less than fabricated proof.

6. "What will it cost, and what am I committing to?" — pricing, with the answer visible.

"Contact us" as the only tier converts self-serve visitors at approximately zero. If pricing genuinely depends on scale, show a starting number and what moves it. The tier the reader should pick is the one that gets the visual weight; three tiers where the middle is marked and slightly larger is a decision, three identical columns is not.

7. "What if I'm wrong?" — the last objection, and the cheapest to answer.

Refund terms, cancellation in one click, no card for the trial, data export on the way out. Every one of these reduces the size of the bet. State them where the decision happens, not in a footer link.

8. The close. One action, repeated, identical to the one in the hero. A second competing action at the bottom reopens a decision the reader had finished making.

The four sections that answer nothing

Cut these and the page gets shorter and better:

• The stat band — "10,000+ users · 99.9% uptime · 4.9/5" — when the numbers are not yours or not verifiable. It kills no objection and it invites the reader to check.
• The nine-card feature grid. See above. It is the shape of an unmade decision.
• The generic FAQ that answers questions nobody asked ("What is [product]?"). An FAQ is useful only when it takes the three real objections you did not fit elsewhere.
• The mid-page newsletter block that interrupts the sequence to ask for something before the reader has been given anything.

What an agent gets wrong

Ask a coding agent for a SaaS landing page and it will return the shapes, in the canonical order, populated with placeholder claims — because that is the median of everything it has read. The tells are consistent: nine features of equal weight, a testimonial with no last name, a stat band with round numbers, an illustration where a screenshot should be, and every section the same height.

None of that is a styling problem, which is why a design skill does not fix it. We wrote about the visual half in why every Claude Code landing page looks the same; this is the other half. The instruction that changes the output is not "make it look better" — it is "for each section, name the objection it kills, and delete the ones that kill none."

If you want that constraint applied by the tool rather than remembered by you, that is what uxgen for SaaS does.

FAQ

How many sections should a SaaS landing page have?

As many as you have objections to kill, which is usually seven or eight. A section that answers no objection is dead weight, and cutting it makes the page both shorter and more convincing.

What goes above the fold on a SaaS landing page?

One sentence naming the thing and the change it produces, one primary action, and one image or short loop of the product doing the thing. A visitor who cannot tell what you sell leaves before any other section gets a chance.

Should a SaaS landing page show pricing?

Yes. Contact-us as the only option converts self-serve visitors at close to zero. If price genuinely depends on scale, show a starting figure and name what moves it.

Why do AI-generated SaaS landing pages look the same?

Because the model returns the median of what it has read: the canonical section order, nine equal feature cards, a testimonial with no last name, a stat band of round numbers, and an illustration where a screenshot belongs. It is a structural default, not a styling choice, which is why a design skill does not fix it.