What to Put on Your Waitlist Landing Page (2026)

Most indie waitlist landing pages convert poorly because they look like every other waitlist landing page. The headline is generic, the form is a single email field, the page has no reason for anyone to share it, and the founder cannot understand why a few hundred views produced four signups. This is the layout guide for the version that actually converts.

I have shipped 7 indie apps over 8 years and ended up building two tools for myself along the way: Spaceport, a SwiftUI starter that gets a paid iOS app live in days, and Lighthouse, the launch toolkit this post is mostly about. The structure below is what both products run.

Table of contents

• Why most waitlist pages convert poorly
• The hierarchy of what to put on the page
• The headline: one sentence
• The problem paragraph: two sentences
• The signup form: email + two questions
• The goal counter: the share lever
• Five things to leave off
• Frequently asked questions

Why most waitlist pages convert poorly

The default indie waitlist landing page is a headline, a paragraph, an email input, and a button. That is a placeholder, not a page. It does not give the visitor a reason to sign up beyond curiosity, and curiosity converts at three percent.

A waitlist landing page has two jobs: get someone to enter their email, and give them a reason to share the URL with someone else. Most pages only attempt the first, and most fail even at that. The page below does both.

The hierarchy of what to put on the page

Read top to bottom. Each element does one job. Skip the parts that do not apply, but keep the order:

• The logo and product name (top-left, small)
• The headline (one sentence, biggest text on the page)
• The problem paragraph (two sentences, directly below the headline)
• The signup form (email plus two short survey questions)
• The goal counter (under the form, with a visible bar)
• The social proof element (optional, below the counter if you have any)
• The footer (one line, contact and links)

That is the full page. Total length: under one viewport on a laptop, under two on a phone. If the page scrolls more than that, you have added something that should be on a separate page.

The headline: one sentence

The headline does the heaviest lifting on the page. It has to do three things in one sentence: name the audience, name the problem, and hint at the solution.

The format that consistently works: "[Solution] for [audience] who [problem]".

• A training plan for runners who hate generic plans
• A styling app for women 5'4" and under who can never find clothes that fit
• A waitlist toolkit for indie founders who want survey answers, not just emails

What does not work: clever wordplay, abstract value statements, a single noun ("Runwell"), or a sentence that requires the reader to already know what the product does. The headline is the page's elevator pitch; treat it like the most important sentence you will write all month.

The problem paragraph: two sentences

Directly below the headline, two short sentences that name the specific pain the visitor is feeling right now. Specific beats grand. The point is for the reader to think "they understand exactly what I am dealing with", which is the moment they hand over the email.

A working example: "Every training plan online assumes you care about race times. Most runners actually care about building the daily habit, which no plan accounts for."

Things to skip: market-size statistics ("the running industry is a $4 billion market"), founder credentials ("with 15 years of experience"), and the feature list. The problem paragraph is about the reader, not about you.

The signup form: email + two questions

The signup form is where almost every indie waitlist underdoes itself. The default email-only form gives you a list of addresses with no context. Two short survey questions on the signup turn the list into validated signal.

Pick two questions that segment the audience and validate the pitch:

• One segmentation question. Demographics, size, role, or stage. Helps you understand who is signing up.
• One pain or priority question. Which problem matters most, or what would make them pay. Helps you decide what to build first.

Two questions is the ceiling. Three or four kills the conversion rate. The signup form should still feel like a signup, not like a survey. See why answers beat emails for the why behind this pattern, and how to run a product survey for the question types worth using.

The goal counter: the share lever

A visible "47 of 100 signups" counter does two things at once. It shows social proof (others have signed up), and it gives the visitor a tangible reason to share the URL (the bar moves with them). The counter is the single element most indie waitlists skip, and it is the one that turns a flat landing page into a shareable one.

Format that works: a horizontal bar with the current number on one end, the goal on the other, and the bar filled to the current ratio. One line of mono-spaced text underneath: "signups in the last 7 days: 12" if you have signups, or "be one of the first to join" if the counter is still near zero.

Goal numbers that work for indie launches: 100 (achievable in weeks, the indie standard) or 500 (more ambitious, suitable for products with a real channel). Avoid 1,000 unless you already have a list to seed it. A goal that looks unreachable kills the share lever instead of creating it.

Five things to leave off

What the page does not show is as important as what it does. Five things almost every indie waitlist page includes that hurt conversion:

• The feature list. Five bullets describing what the product does. The reader does not need this on the waitlist page; they need it on the post-launch product page. On the waitlist page, the feature list is a distraction from the signup.
• Pricing. No real pricing on the waitlist page. The waitlist is the validation phase; pricing belongs on the product page after launch. Putting pricing on the waitlist tells visitors you have decided everything already, which removes the reason to give feedback.
• The founder origin story. Useful on an About page, harmful on the waitlist page. The visitor wants to know if the product solves their problem, not why the founder is the right person to build it.
• A long FAQ. A waitlist FAQ should be three questions at most: "when does it launch", "what does it cost", "how is it different from X". Five or more questions suggests the headline and problem paragraph did not do their job.
• Stock photography. The default hero photo of a person at a laptop, the stock illustration of a phone with arrows, the abstract gradient banner. Either ship a real product screenshot or skip the image entirely. Indie audiences smell stock and bounce.

Frequently asked questions

Should I include a video on the waitlist page?

No, not for a waitlist. Video belongs on the post-launch landing page where the product exists. On the waitlist page, a video adds friction: the visitor either watches and gets tired, or skips and feels guilty. A short text page converts better at this stage.

What if my product is technical and needs a diagram?

Use a single ASCII-style or simple line illustration that takes ten seconds to read. If the product genuinely cannot be explained without a diagram, replace the problem paragraph with a one-sentence pitch plus the diagram. Skip the diagram entirely if you are not sure; words convert better than uncertain visuals.

What if I want to charge for early access?

Then it is not a waitlist, it is a pre-order page. Different shape: same headline and problem paragraph, but the form is replaced by a pricing block and a payment button. Pre-order pages convert lower but the signal is stronger (people who pay are real validation).

How does this fit into a fundraising story?

The waitlist page is part of the traction story for the raise. The numbers off the page (signups, survey answers) become the slide that opens the deck. Dedicated platforms for the raise itself, like Funding Banker, a curated investor directory with pitch and outreach tracking, handle the investor side; the waitlist page handles the public side.

What tool should I use to build the page?

For a no-stitching path: Lighthouse hosts the waitlist landing page, the survey questions on the signup, and the goal counter in one place. For a stitched path: Carrd or Framer for the landing, Tally or Typeform for the survey, Mailchimp for the email. See Carrd alternatives for a data-led waitlist for the tradeoffs.

A good waitlist page is small. One headline. Two sentences. A form with two questions. A counter. Nothing else. The pages that try to do more (with feature lists, pricing, founder stories) consistently convert worse than the pages that hold the line. Discipline is the design.

Lighthouse hosts the waitlist landing page with the survey questions on the signup form, the goal counter, and the launch-email tool that comes after. Free trial, indie pricing. From the same indie dev behind Spaceport, a SwiftUI starter kit for shipping paid iOS apps fast.