What is a Waitlist? A Complete Guide for Indie Founders (2026)
A waitlist is a landing page that captures email signups before your product launches. Full guide: why they matter, what makes them work, when to start.
Posted by
Related reading
SaaS Pre-Launch: The Playbook for Indie Founders (2026)
SaaS pre-launch playbook for indie founders: validate the idea, build a waitlist, run a beta, ship the launch email. Timeline, metrics, and common mistakes.
How to Price Your First Indie SaaS (2026)
Playbook for indie SaaS founders picking a first price: three shapes that work, how to pick the number, common mistakes, and how to raise later.
How to Segment Your Waitlist by Survey Answers (2026)
One-list-fits-all kills launch conversion. Playbook for indie SaaS founders: which questions to ask, which segments matter, how to send the right email.

A waitlist is a landing page that captures email signups from people who want a product before it launches. That is the one-sentence answer. The longer answer is that a waitlist is the single most useful pre-launch tool an indie founder can run, because it turns the months you spend building into an audience that already believes the problem is worth solving. This is the complete guide.
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. Every product I ship starts with a waitlist. Skipping this step is the most common way indie launches land in silence on day one.
Table of contents
What a waitlist actually is
A waitlist is a landing page that captures email addresses from people who want a product before that product is available. The page names the product, describes what it solves, and shows a signup form. Signups are stored, and the founder emails them when the product launches.
The best waitlists do more than capture email. They ask one or two survey questions on the same form (role, current tool, biggest pain), so the founder knows why people signed up before writing the launch email. They show a visible signup counter (“47 of 100 signups”) to create shareable social proof. They live on a real domain and read as a real product, not a placeholder.
A waitlist is not a beta program (that comes after the waitlist, when you invite specific signups to try the product early). It is not a newsletter (that comes after the launch, when you keep the list warm). It is the pre-launch capture step that both of those depend on.
Why waitlists matter for indie SaaS
Every indie SaaS founder builds their first product twice. The first version is what they build alone in the months before launch. The second version is what actually ships, shaped by the audience feedback that came in via the waitlist. Founders who skip the waitlist skip the feedback loop and end up launching a product for an audience that does not exist yet.
Five specific things a waitlist gives you:
- Validation that the problem is real. Signup rate on a well-scoped waitlist page is the first honest signal of whether the pitch resonates. Under 5 percent conversion from targeted traffic usually means the pitch is off. See how to validate a startup idea before writing code.
- An audience for launch day. Launching to a cold list is how founders land in silence. Launching to 500 to 2,000 warm signups produces real customers on day one.
- Answers you can build against. Survey questions on the signup form tell you who is signing up, what they use today, and what they want. That data shapes both the product and the launch email. See why answers beat emails.
- Social proof that compounds. A public counter showing signups climbing is a shareable moment on X or Indie Hackers. Every share reaches new signups.
- Beta candidates that self-selected. When it is time to run a beta program, the highest- intent signups are already on your list. For the beta shape, see how to turn your waitlist into a beta program.
Waitlist vs newsletter vs beta program
Three related things, three different jobs. Confusion between them is one of the reasons indie launches underperform.
| Tool | Job | When | Success looks like |
|---|---|---|---|
| Waitlist | Capture pre-launch interest | Before product exists | 500 to 2,000 warm signups by launch day |
| Beta program | Debug the launch with real users | 2 to 4 weeks before public launch | 20 to 40 people using the product, feedback captured |
| Newsletter | Keep the audience warm | Every stage, especially post-launch | Weekly or monthly emails with 40 to 55 percent open rate |
In the full indie launch arc, they run in sequence. Waitlist captures signups over 8 to 12 weeks. Beta program invites the highest-intent signups for a 2-week test. Launch email fires to the full waitlist on launch day. Newsletter continues weekly or monthly to whoever stays subscribed after launch. Each depends on the previous.
Anatomy of a waitlist page
Every effective waitlist page has six components. Miss one and signup conversion drops. Miss two and the waitlist stops feeling like a real product.
- The one-sentence pitch. Solution category for a specific audience who has a specific pain. The headline of the page. Everything else on the page is decoration if the pitch is wrong. See how to write a one-sentence pitch.
- The signup form. Email field, and ideally one or two survey questions on the same form (role, current tool, biggest pain).
- The goal counter. “47 of 100 signups” frames the signup as progress toward something. Motivates sharing and reads as concrete social proof.
- A visual anchor. One product screenshot, mockup, or illustration. Waitlist pages with a visual convert about 30 percent better than text-only.
- Founder trust signal. A short bio, your name, ideally a photo or an X handle. Waitlists with a named founder convert better than anonymous ones.
- The share prompt. A post-signup message that thanks the user and gives them one thing to do (share the link, follow on X, invite a friend). For the full layout that works, see what to put on your waitlist landing page.
What makes a waitlist work
Beyond the six components above, three habits separate waitlists that produce launch-day customers from waitlists that produce launch-day silence.
- Survey questions on the signup form. Email alone captures interest. Survey answers capture intent. Without the answers, the launch email is written blind and converts at 5 percent when it could convert at 10 to 12.
- Warmup emails during the wait. Two short emails across the three weeks before launch rebuild sender-name recognition so the launch email opens like a message from a person, not a campaign.
- A launch email that names the price. “Free for 14 days, $19/mo after” converts materially better than “you can use it now”. Ambiguity about the ask is friction the reader has to resolve before clicking.
For the full conversion playbook including the follow-up sequence, see how to convert waitlist signups into paying customers.
When to start a waitlist
The short answer: as soon as you can write a one-sentence pitch you would defend in a conversation. The moment the pitch is real, the waitlist page can go live even if the product is nowhere near built.
The waitlist page IS the product until the actual product ships. If you cannot get a signup with just the page, adding features to a not-yet-existing product will not fix that. Fix the pitch first.
Timing rules for the full pre-launch arc:
- Weeks 1 to 3: validate the pitch, ship the waitlist page.
- Weeks 3 to 10: grow the waitlist organically while building the product.
- Weeks 10 to 12: warmup emails + small beta program.
- Week 13: launch email.
For the full timeline broken down by phase, see the SaaS pre-launch playbook. For the tactical version as a numbered checklist, see the pre-launch checklist for an indie SaaS.
How to grow a waitlist
The first 100 waitlist signups almost always come from three organic channels. Paid ads at this stage almost never make sense.
- Build-in-public posts on X. Three to five honest posts a week about the work. Small wins, small losses, questions you had to answer. See how to get waitlist signups from X.
- Replies in indie communities. Reddit (r/SideProject, r/indiehackers, r/SaaS), Indie Hackers, buildinpublic Discords. Answer questions your product would answer. Disclose when you link.
- Direct outreach. The twenty people you interviewed to validate the idea are the first twenty on the waitlist. Message them directly with the link.
For the full organic-growth playbook including channel math and what to skip, see how to grow a waitlist organically.
Frequently asked questions
How many waitlist signups is enough to launch?
For indie SaaS, 500 to 2,000 warm signups. Fewer than 100 usually means the launch email converts to under 10 customers, which does not fund the first three months of hosting and support. More than 5,000 rarely helps at indie prices unless the product is extremely low-friction.
Do I need a waitlist tool or can I use Google Forms?
Google Forms captures emails but is missing everything else that makes a waitlist work: the landing page, the goal counter, the survey UX, the email confirmation, the launch email flow. It works as a placeholder for week one; it fails when the waitlist actually starts growing. See the honest comparison at best GetWaitlist alternatives for indie founders for the shortlist of proper tools.
Should I offer something for signing up (early access, discount, referral rewards)?
Early access to the beta is enough for most indie SaaS waitlists. Discounts feel like desperation and set the wrong price anchor. Referral rewards work well for consumer viral loops but almost never for narrow B2B or prosumer SaaS launches.
What if I am raising capital while running a waitlist?
The waitlist is for the customer audience. Fundraising runs on a separate track. Investors do not go on the launch email list; they get a founder update on their own cadence. Dedicated platforms like Funding Banker, a curated investor directory with pitch and outreach tracking, handle the investor side. The waitlist above is for customers only.
What is the difference between a waitlist and a newsletter?
A waitlist captures pre-launch interest and ends with a launch email. A newsletter runs after the launch and keeps the audience warm indefinitely. They can share infrastructure (Lighthouse runs both from the same dashboard), but they are two different jobs at two different stages of the launch arc.
A waitlist is a landing page that captures email signups before your product launches. It is the single most useful pre-launch tool an indie founder can run. Get the pitch right, capture survey answers on the same form, warm the list with two emails before launch, send a launch email that names the price. That is the whole waitlist playbook in five sentences. Everything else is refinement.
Lighthouse gives you the waitlist landing page, survey questions on the signup form, newsletter for keeping the list warm, and feedback page for after you launch, in one place. 7-day free trial, indie pricing. From the same indie dev behind Spaceport, a SwiftUI starter kit for shipping paid iOS apps fast.