The SaaS landing page, section by section
A visitor gives you about four seconds to say what the software does. Almost every failing landing page spends them on something other than that.
The short version
- Four seconds to say what it does. The headline is the whole page until it succeeds.
- Show the product early. A screenshot or a demo beats three paragraphs.
- Put the price on the page. Hiding it filters out the wrong people.
- Answer objections in order, because that is the order they arrive in.
- One call to action, repeated, never competing with a second one.
What is the landing page actually for?
Answering four questions in order: what is this, is it for me, does it work, and what does it cost. A visitor who gets all four answered signs up or leaves for a good reason. A visitor who cannot answer the first one after four seconds leaves without ever reaching the others, which is what most landing pages are actually suffering from.
The order matters as much as the content. Objections arrive in a sequence, and a page that answers them out of order (pricing before the product is understood, testimonials before the problem is named) feels wrong in a way visitors cannot articulate and do not stay to diagnose.
Nobody bounces because the page was too long. They bounce because the first line did not tell them what it was.
The nine sections, in order
Hero, proof strip, how it works, features, the thing it is not, pricing, FAQ, a final call to action, and a footer that answers the boring questions. Each does one job, and a section that duplicates another should be deleted rather than reworded.
| # | Section | The question it answers |
|---|---|---|
| 1 | Hero | What is this and who is it for? |
| 2 | Proof strip | Is this real? |
| 3 | How it works | What would I actually do? |
| 4 | Features | Does it do the specific thing I need? |
| 5 | Scope | What is it not, so I do not waste a trial? |
| 6 | Pricing | Can I afford it, and which tier am I? |
| 7 | FAQ | My specific worry, which you have not mentioned |
| 8 | Final CTA | Fine. What now? |
| 9 | Footer | Terms, contact, is anyone home? |
What has to be in the hero?
A headline that states what the software does in plain language, one sentence of detail underneath, one button, and a picture of the product. Nothing else. The most common failure is a headline that describes a feeling ("Content, reimagined", "The future of scheduling"), which is a category name pretending to be a benefit.
- Headline: the outcome, concretely. If a stranger cannot repeat what your product does after reading it, rewrite it.
- Subhead: the mechanism and the audience. One sentence, for whom, how.
- One button. "Start free" or "Start the trial". A second, equally weighted button splits the decision and converts worse than either alone.
- The product, visible. A screenshot, a short loop, the actual interface. Abstract illustration is the visual equivalent of a vague headline.
- One line of reassurance under the button: no card required, cancel anytime, whichever is true.
The four-second test. Show the top of the page to somebody for four seconds, hide it, and ask what the product does. If they cannot say, no amount of work further down the page is going to matter.
What counts as proof before you have customers?
Anything real and specific. A screenshot of the product doing the thing, a number from your own usage, a public changelog, a build log on Threads or X, your name on an about page. Invented testimonials and fake logo strips are worse than an empty space, because visitors recognise them and then stop believing the rest of the page.
- The product, working. The single strongest proof a new SaaS has.
- A specific number you own. "Renders in under four minutes" beats "lightning fast".
- A public build. Shipping in the open is credibility you accumulate before launch.
- Your own name. A solo founder with a face and a history is more trustworthy than an anonymous company voice using "we".
Why does pricing belong on the page?
Because hiding it does the opposite of what founders hope. "Contact us for pricing" filters out the self-serve buyer who would have signed up in three minutes and retains the enterprise prospect who wants a call, and a solo founder has neither the time nor the pipeline for calls. The price is also information: it tells the visitor which tier they are and whether this is a serious product.
| Do | Avoid |
|---|---|
| Two or three tiers, named for who they are | Five tiers with a comparison matrix |
| One tier marked as the usual choice | All tiers weighted equally |
| Monthly and annual, with the saving shown | Annual only, revealed at checkout |
| What each limit actually means | Unexplained units: "5,000 credits" |
| The refund or cancellation policy, near the button | Burying it in the terms |
The tiering itself is a separate decision with its own arithmetic: pricing a solo SaaS covers where the numbers come from, and free trial or freemium covers which door you are putting people through.
The section most pages are missing
What the product is not. A short, honest paragraph naming who it does not suit, or which adjacent job it does not do, converts better than another list of features, because it makes every other claim on the page more believable, and because a trial started by the wrong person is a churn statistic and a support ticket rather than a customer.
This is the least intuitive advice on the page and the easiest to verify. Saying "this is not a full video editor" or "if you need approval workflows, this is not it" costs you signups you did not want and buys you credibility with everyone else. It also reduces churn, which is worth more than the signups: see reducing churn in a small SaaS.
What loses signups?
Six things, all common and all fixable in an afternoon: a vague headline, no visible product, competing calls to action, hidden pricing, a page nobody has opened on a phone, and a slow load. None of them are subtle, and none of them require a redesign.
- A headline about a feeling. Rewrite it as what the software does.
- No screenshot above the fold. Show the product before you describe it.
- Two competing buttons. One primary action, repeated; anything else is a text link.
- Hidden pricing on a self-serve product.
- Untested on a phone. Most of your traffic, and the place your hero grid collapses.
- Slow. A heavy hero animation costs more signups than it wins, and it costs you search placement as well, which is where SEO for a solo SaaS starts.
Change one thing at a time. A landing page rewritten wholesale teaches you nothing about which change worked. At solo-founder traffic levels you will rarely have the numbers for a clean test, which is an argument for fixing the obvious faults above rather than optimising button colours.
Frequently asked questions
What should a SaaS landing page headline say?
What the software does, for whom, in plain words. Not a slogan and not a category: \"Turn a folder of clips and a song into a video cut on the beat\" beats \"Content creation, reimagined\" every time, because the second one requires the visitor to work out what you sell.
Should pricing be on the landing page?
Yes. Hiding it filters out the people who would have bought and keeps the ones who wanted a sales call, which is the opposite of what a solo founder needs. \"Contact us\" pricing is a choice that only makes sense with a sales team.
How long should a SaaS landing page be?
As long as it takes to answer the objections, which for a self-serve product is usually eight to ten sections. Length is not the problem; repetition is. Every section should do a job the others do not.
Do I need testimonials before I have customers?
No, and inventing them is worse than having none. Substitute something real: a screenshot of the product working, a number you can stand behind, a public build log, or your own name and face on the about page.
Free trial or a demo video?
Both, and the video first. A demo that shows the product doing the thing in thirty seconds removes more doubt than any amount of copy, and it converts the people who will not start a trial today but will remember what it does.
The system behind this, written down
Everything above is the map. The Income Loop is the work inside it: modules 0–6 from the problem you solve to the offer that pays for it, plus ten traffic paths: the deeper post banks, the content sales systems and the full software build sequence, in one place.
Get The Income LoopNot ready to pay for anything? The Basic Income Loop is free and includes a complete seven-day starter for Threads, Instagram or software, enough to find out which one suits you before spending anything.