How to Write a SaaS Homepage That Converts (Bootstrapped Guide)

A SaaS homepage converts when one specific visitor understands what the product does, why it beats what they use now, and what to click next, all within a few seconds. Pick one audience, write the hero from your customers' own words, show the product, back claims with honest proof, answer the objections that stall signups, and test with five-second tests and free session recordings instead of A/B tests you do not have the traffic for.

Editorial title card reading "How to Write a SaaS Homepage That Converts (Bootstrapped Guide)" beside the orange ZeroRaised mark.

Key takeaways

  • Choose one audience before writing a word. Growth Unhinged's homepage framework opens with exactly that step: "The first step to writing a homepage is choosing an audience."
  • Write the hero from customer interview and review language, not from your head. Copyhackers' Joanna Wiebe puts it bluntly: "Instead of writing your message, steal it."
  • A converting homepage follows a predictable order: hero headline, subhead, one primary CTA, product visual, proof, how it works, objections or FAQ, and a final CTA.
  • With no customers yet, use honest proof: a founder note, a real product demo, specific numbers about the product itself and a clear guarantee or free plan. Never invent testimonials or logos.
  • On low traffic, skip A/B tests. Run five-second tests (Lyssna has a $0 plan with 15 self-recruited responses) and watch real sessions in Microsoft Clarity, which is "Free forever".
On this page 22
  1. TL;DR
  2. What this guide covers (and what it does not)
  3. Step 1: Decide who the homepage is for
  4. Step 2: Mine your customers' words
  5. The section-by-section homepage template
  6. 1. Hero headline
  7. 2. Subhead
  8. 3. Primary CTA
  9. 4. Product visual
  10. 5 to 10. Proof, problem, how it works, features, objections, final CTA
  11. Before and after: a headline rewrite
  12. Honest proof when you have no customers yet
  13. Testing a homepage on low traffic
  14. Where homepage traffic comes from
  15. Frequently asked questions
  16. What should a SaaS homepage headline say?
  17. How long should a SaaS homepage be?
  18. How do I add social proof to a homepage with no customers?
  19. Can I A/B test a homepage with low traffic?
  20. Should the homepage CTA be a free trial, a demo or a waitlist?
  21. Put your homepage in front of real visitors
  22. Sources

Short answer: A SaaS homepage converts when one specific visitor understands, in a few seconds, what the product does for them, why it is better than what they use now, and what to click next. Choose one audience, write the hero from your customers' own words, show the real product, back every claim with honest proof, and answer the objections that stop signups. On bootstrapped traffic, test with five-second tests and session recordings rather than A/B tests.

Tool prices and expert quotes below come from the vendors' and authors' own pages, checked on 7 Nov 2026. The template and advice are ours and are marked as such.

TL;DR#

  • Audience first. Growth Unhinged's homepage framework starts with: "The first step to writing a homepage is choosing an audience" (Growth Unhinged).
  • Steal the words. "Instead of writing your message, steal it," writes Joanna Wiebe of Copyhackers (Copyhackers). Your interview notes and support emails are the raw material.
  • Use a fixed order: hero headline, subhead, one CTA, product visual, proof, how it works, objections or FAQ, final CTA. The template is below.
  • Honest proof beats fake proof. No customers yet? Show the product, the founder and a clear free plan or guarantee.
  • Test cheaply. Lyssna's Free plan is $0 with 15 self-recruited responses (Lyssna pricing). Microsoft Clarity is "Free forever" with heatmaps and recordings (Microsoft Clarity).

Disclosure: ZeroRaised publishes this guide and is a launch site for bootstrapped products. ZeroRaised has no commercial relationship with Lyssna, Microsoft, Growth Unhinged or Copyhackers and earns nothing if you use them. Facts come from the linked sources as checked on 7 Nov 2026.

What this guide covers (and what it does not)#

This is about the words and structure of the homepage. For where to build it, see our best landing page builders for bootstrapped founders. For the next page visitors open, read how to write a SaaS pricing page.

Step 1: Decide who the homepage is for#

Most weak homepages are weak before the first word, because they try to speak to everyone. The Growth Unhinged framework by Kyle Poyar and Anthony Pierri describes the homepage as "a marketing asset" and makes audience choice the first step, then suggests you weigh the options: "Once you've mapped out your audience options, you then can weigh the pros and cons of each to find the right target" (Growth Unhinged).

April Dunford, who wrote the positioning book Obviously Awesome, frames the underlying job on her site: "Positioning defines how our product is different and better than alternatives for a particular set of customers" (April Dunford). The homepage is where that positioning gets written down in public.

Our read: for a solo founder, the right audience is usually the group that already pays you or the group that complained loudest about the problem in your interviews. Write down three things before you open the editor:

  1. Who: the role and situation ("freelance designers who invoice 5 to 20 clients").
  2. Current alternative: what they use today (spreadsheets, a bigger tool, doing nothing).
  3. Why you win: the one difference that matters to that person, not your full feature list.

If you cannot fill in all three, the homepage will not fix it. Go back to conversations first.

Step 2: Mine your customers' words#

The fastest route to a homepage that sounds right is to stop inventing copy. In her review mining guide, Joanna Wiebe writes: "Review mining data should write your copy, you shouldn't write copy," and "When you go through user reviews one by one, what's really important to your prospects rises to the top" (Copyhackers).

A bootstrapped founder has three good sources:

  • Interview notes. If you ran calls like those in our guide to customer discovery interviews, your notes already hold the pain in the customer's phrasing.
  • Support emails. Find the sentence people use to describe the problem.
  • Competitor reviews. Low-star reviews show what the alternative gets wrong.

How to process it, in about an hour:

  1. Paste every useful line into one doc.
  2. Group lines under four headings: pain, desired outcome, objection, reason they chose you.
  3. Mark phrases that appear more than once or are unusually vivid.
  4. Use those exact phrases for the headline, subhead, section headings and FAQ.

Our read: if a phrase came from three different people, it belongs above the fold.

The section-by-section homepage template#

This is the order we recommend for most bootstrapped SaaS products. It is our template, built for self-serve products with a free plan or trial. Each section answers one question a visitor has.

#SectionVisitor question it answersWhat to write
1Hero headlineIs this for me, and what do I get?Outcome for a specific person, in their words
2SubheadWhat is it, exactly?Product category plus how it works, one or two sentences
3Primary CTAWhat do I do now?One button, specific verb, risk reducer underneath
4Product visualIs it real? What does it look like?Real screenshot or short loop of the core workflow
5ProofCan I trust this?Testimonials, numbers, founder note (honest only)
6ProblemDo they get my situation?The pain in customer language, short
7How it worksIs it hard to start?Three steps from signup to first result
8Key features as outcomesWill it do what I need?Three to five features, each tied to a result
9Objections and FAQWhat could go wrong?Price, switching, data, support, cancellation
10Final CTAReady?Repeat the primary CTA with the same wording

1. Hero headline#

The headline's job is to make the right visitor think "this is for me". Our formula:

[Desired outcome] for [specific audience], without [the main pain of the current alternative].

The audience or the "without" can move to the subhead; the outcome cannot. Avoid slogans like "The future of work" that a visitor cannot act on.

2. Subhead#

The subhead says what the product is and how it delivers the headline. If the headline is the promise, the subhead is the mechanism. One or two sentences, and name the category so visitors can file you: "an invoicing app", "a status page tool", "a Chrome extension".

3. Primary CTA#

One primary button, not three. Use a verb that describes what happens next ("Start free", "Create your first invoice") rather than "Submit" or "Learn more". Directly under it, add a single risk reducer you can honour, such as "No card required" or "Free plan, cancel anytime". If your offer is a trial or freemium, our pricing page guide covers how to frame it; on the homepage, state it in one line and move on.

4. Product visual#

Show the real product doing the core job. A screenshot of the main screen with one annotation, or a short silent loop of the key workflow, beats an abstract illustration. Our read: if a visitor watches only this, they should understand what the product does.

5 to 10. Proof, problem, how it works, features, objections, final CTA#

  • Proof: put your strongest single piece close to the hero (see honest proof below).
  • Problem: two to four short lines in your mined phrases, so visitors recognise themselves.
  • How it works: three steps from signup to first result, which quietly answers "is it hard to set up?".
  • Features as outcomes: "Automatic reminders, so you stop chasing late payments." Leave the full list to docs.
  • Objections: answer what you heard in interviews: price, importing data, cancelling, support. For a solo founder, "You email me, the founder, and I reply" is a real selling point.
  • Final CTA: repeat the primary CTA with the same wording and risk reducer.

Before and after: a headline rewrite#

This is an illustrative, fictional example, not a real product or test result.

Imagine "Ledgerly", an invoicing tool for freelancers. The founder's first draft:

Before: "Ledgerly: smart, modern invoicing for the future of work." Subhead: "An all-in-one platform that empowers you to manage your business."

The interview notes keep repeating two phrases: "I hate chasing clients for money" and "I just want to get paid without awkward emails". The rewrite:

After: "Get paid on time without chasing clients." Subhead: "Ledgerly is an invoicing app for freelancers. Send an invoice in two minutes and it follows up automatically until the client pays." CTA: "Send your first invoice free" with "No card required" below.

What changed:

ElementBeforeAfter
AudienceImplied "everyone"Freelancers, named in the subhead
Outcome"Smart, modern" (vague)Paid on time
PainNoneChasing clients
Mechanism"All-in-one platform"Automatic follow-ups
Source of wordsFounder's headCustomer interviews
CTAGenericSpecific first action plus risk reducer

Honest proof when you have no customers yet#

New products have no logos or reviews. That is fine; inventing them is not. Fake testimonials and made-up user counts destroy trust the moment someone checks. Use proof you can stand behind:

  • A founder note: your name, face and why you built it. Proof a reachable human is behind it.
  • The product itself: a real demo video or screenshot proves it exists and works.
  • Specific, true facts: "Exports to CSV and PDF", "Open source on GitHub".
  • Beta user quotes, with permission: two or three real quotes with name and role beat none.
  • Risk reversal: a free plan, no-card trial or clear refund policy lets visitors try instead of trust.
  • Public build history: a changelog shows the product is alive.

Our read: once you have five paying customers, ask each for a one-line quote about the result they got. Replace your weakest proof element first.

Testing a homepage on low traffic#

A/B testing needs volume. With a few hundred visitors a month, two versions of a headline will usually look different by chance. Use qualitative methods instead.

MethodToolCost (checked 7 Nov 2026)What it tells you
Five-second testLyssnaFree plan $0/mo with 3 seats and 15 self-recruited responses; Growth $166/mo; panel responses priced separatelyWhether a stranger can say what you do after a glance
Session recordings and heatmapsMicrosoft Clarity"Free forever", with "No limits on traffic"Where real visitors scroll, click and drop off
Customer read-throughA call or email$0Whether your wording matches theirs

Prices from Lyssna pricing and Microsoft Clarity. Lyssna says panel responses are "priced separately on all plans", so the $0 plan works best when you send the test link to your own audience.

Lyssna describes the method in one line: "Five second tests help you measure what clicks and what gets missed" (Lyssna). Clarity says its heatmaps show "where they click, scroll and drop off" (Microsoft Clarity).

Our suggested low-traffic routine:

  1. Five-second test the hero. Then ask "What does this product do?" and "Who is it for?". If most answers are wrong, rewrite the headline and subhead.
  2. Watch 20 Clarity sessions. Note where people stop scrolling and whether anyone reaches the CTA.
  3. Read the page to two customers. Ask which line sounds like them and which sounds like marketing.
  4. Change one section at a time and log what changed and when, so you can compare signups month to month.

Our read: if testers cannot say what the product is, fix the subhead before anything else.

Where homepage traffic comes from#

A converting homepage still needs visitors. A launch is a good stress test, since it sends strangers who know nothing about you. See our free marketing channels for bootstrapped makers.

Frequently asked questions#

What should a SaaS homepage headline say?#

It should say what the product helps a specific person achieve, in words that person would use. A useful formula is outcome plus audience plus the difference from the alternative, for example "Send invoices that get paid on time, without chasing clients" for freelancers. Then use the subhead to say plainly what the product is and how it works.

How long should a SaaS homepage be?#

Long enough to answer the questions that stop a visitor from signing up, and no longer. For most bootstrapped SaaS products that is eight sections: hero, product visual, proof, problem, how it works, key features, objections or FAQ, and a final CTA. Cut any section that does not answer a real question a prospect asked you.

How do I add social proof to a homepage with no customers?#

Use honest proof: a short founder note with your name and face, a real screen recording of the product, specific facts about what it does, quotes from beta users with their permission, and a clear free plan, trial or refund policy. Do not invent testimonials, user counts or customer logos.

Can I A/B test a homepage with low traffic?#

Usually not in a meaningful way, because a few hundred visitors a month is rarely enough to tell two versions apart. Use qualitative tests instead: five-second tests on a tool like Lyssna, which has a $0 plan with 15 self-recruited responses, plus free session recordings and heatmaps in Microsoft Clarity.

Should the homepage CTA be a free trial, a demo or a waitlist?#

Match it to how people buy. Self-serve products under a few hundred dollars a year usually suit Start free or Start a free trial. Higher-priced or complex products can justify Book a demo. Pre-launch products can use Join the waitlist. Pick one primary CTA and repeat the same wording throughout the page.

Put your homepage in front of real visitors#

ZeroRaised is a launch directory for products built without institutional VC. When your new homepage is live, submit your product for free and see how launch-day visitors respond. For more guides on growing without investors, join the ZeroRaised newsletter.

Sources#

Frequently asked questions

What should a SaaS homepage headline say?

It should say what the product helps a specific person achieve, in words that person would use. A useful formula is outcome plus audience plus the difference from the alternative, for example "Send invoices that get paid on time, without chasing clients" for freelancers. Then use the subhead to say plainly what the product is and how it works.

How long should a SaaS homepage be?

Long enough to answer the questions that stop a visitor from signing up, and no longer. For most bootstrapped SaaS products that is eight sections: hero, product visual, proof, problem, how it works, key features, objections or FAQ, and a final CTA. Cut any section that does not answer a real question a prospect asked you.

How do I add social proof to a homepage with no customers?

Use honest proof: a short founder note with your name and face, a real screen recording of the product, specific facts about what it does, quotes from beta users with their permission, and a clear free plan, trial or refund policy. Do not invent testimonials, user counts or customer logos.

Can I A/B test a homepage with low traffic?

Usually not in a meaningful way, because a few hundred visitors a month is rarely enough to tell two versions apart. Use qualitative tests instead: five-second tests on a tool like Lyssna, which has a $0 plan with 15 self-recruited responses, plus free session recordings and heatmaps in Microsoft Clarity.

Should the homepage CTA be a free trial, a demo or a waitlist?

Match it to how people buy. Self-serve products under a few hundred dollars a year usually suit Start free or Start a free trial. Higher-priced or complex products can justify Book a demo. Pre-launch products can use Join the waitlist. Pick one primary CTA and repeat the same wording throughout the page.