You've seen the playbook. Build a one-page site. Put up a "join the waitlist" box. Post it on Twitter. Get a thousand emails. Launch to a flood of users.
It works sometimes, and it's been part of indie product lore for a decade. But the gap between the waitlists that work and the waitlists that produce a thousand cold emails and zero customers is wide, and the difference isn't the page. It's the loop the page sits inside.
A waitlist before launch is one of the highest-payoff moves an indie founder can make, if you do it right. This post is what "right" looks like: what to put on the page, how much friction to weight in, and the follow-up sequence that turns a signup into a first paying user.
What a waitlist is for (and what it isn't)
A waitlist is two things at once.
It's a distribution lever. The page exists, you can share the URL, friends can forward it, it shows up in search if it lives long enough.
It's a signal collector. Every signup is a data point. Who they are, where they came from, what they wrote in the optional "what would you use this for" field. By the time you launch, you have a list of warm prospects and a rough picture of who actually wants the thing.
What a waitlist is not:
- A guaranteed audience on launch day. The "thousand emails, ten percent convert" math assumes a relationship you may not have actually built. Most cold waitlists convert at 1 to 3% when you do email them.
- A substitute for shipping. Sitting on a waitlist for nine months while you "perfect the product" usually means the audience forgets you. Three months is the outer edge of attention.
- A marketing checkbox. Putting up a waitlist page because "that's what you're supposed to do" produces a dormant page with no signups.
If you're going to do a waitlist, do it because you want both the distribution and the signal. If you only want one, there are cheaper ways.
The page: one promise, one input
The waitlist page that converts has one promise the visitor can grasp in five seconds and one input box they can fill in five more.
The promise is the headline. Not the product name; the thing the product does, framed for one person.
Weak headlines:
Introducing Habitor: the smarter way to build habits.
Strong headlines:
Build one habit a month. We'll handle the reminders, the streak math, and the gentle nag when you slip.
The second one tells you what the product does, what it asks of you, and what it gives back. The first tells you nothing.
Below the headline, one input. Email address, button, done. Not a phone number. Not a "tell us about yourself" form. Not a four-step onboarding. The job of the page is to capture interest; depth comes in the follow-up.
Three optional things, used sparingly:
- A "what would you use this for?" textarea, marked optional, below the email. Maybe 20% of signups will fill it in; those answers are gold for the product roadmap.
- A social proof slot. Once you have a few hundred signups, add "Already 432 people on the list." Don't fake numbers; users smell it.
- A "where did you hear about us" select. Useful for tracking which channels work. Optional.
That's the page. Add a third element and you start losing signups to friction.
How much friction is the right amount
There's a counterintuitive truth about waitlists: a tiny bit of friction increases the quality of your signups.
A pure "email box, button" gets you the most signups, but a chunk of them are accidental, drive-by interest. Three months later when you email them, they don't remember signing up.
A small extra step (a confirmation email, a one-line "tell us what you'd use this for" field, even a polite "we'll email you when we launch, here's roughly when" expectation-setter) filters out the casual signups. You get fewer total emails but higher-quality ones. People who took 20 extra seconds are more likely to open the launch email.
The threshold is: if a real person genuinely interested would still complete the step, the friction is fine. If a real person interested might bail, it's too much.
What's "fine":
- A double opt-in confirmation email
- An optional "what would you use this for" textarea
- A "we'll email you within the next few months" timing expectation
What's "too much":
- A required phone number
- A required role/company size dropdown for a consumer product
- Three pages of survey before signup
- An invite-code requirement for the first 100 signups (this works rarely; usually it just kills signups from people who would convert)
If you're between two friction levels, pick the slightly more friction one. The signups you lose are the signups you wouldn't have converted anyway.
The follow-up loop: where waitlists actually win or lose
This is the part most indie founders skip and where the difference between 1% and 30% conversion lives.
The naive plan: collect emails. Launch. Email everyone "We're live!" Wait.
The conversion rate on that pattern is around 1 to 3% on a cold list, which is actually worse than a good organic launch with no waitlist.
The plan that works: collect emails. Then talk to those people across the months before launch.
A minimal follow-up sequence:
- Day 0 (signup): a personal-feeling welcome email. "Thanks for signing up. We're building [thing]. Here's roughly when we expect to launch and what early access looks like." Honest. Personal voice. Reply-able to the founder's actual inbox.
- Roughly monthly between signup and launch: one short update email per month. What you shipped, what you learned, what's next. Five paragraphs maximum. Not a press release. The point is to keep the relationship warm so the launch email isn't from a stranger.
- Two weeks before launch: an "early access opens [date], here's what to expect" email. Sets the date in their calendar.
- Launch day: a clean "we're live, here's the link, here's the price, reply to this if you hit issues" email.
- Three days after launch: a "still on the fence?" email to anyone who hasn't clicked through.
If you've done the monthly updates, the launch email converts dramatically better than a cold one. Common numbers I've seen for indie SaaS launches with this loop in place: 15 to 30% click-through on the launch email, 5 to 12% to a paid plan within a week. Numbers vary by category, but the shape is consistent: warm waitlists outperform cold waitlists by an order of magnitude.
A worked example
Real shape, anonymised. Indie founder building a tool for freelance designers. Waitlist runs for four months.
Month 0: launches the waitlist page. Headline: "Stop chasing invoices. Let your contract chase them." Shares on Twitter (heavy designer audience), gets 180 signups in week one.
Month 1: writes a 6-paragraph update. What's been built, one decision they reversed, a small mock of the dunning email flow. Sends to 240 signups (more have come in). 45% open rate, two reply with feature requests.
Month 2: another update. Beta is open to first 20 signups; a real screenshot is included. Tells the rest "you're on the list; we'll get to you." 38% open rate, three replies, four signups churn out (which is fine).
Month 3: launch. Two weeks notice email. Launch day email. 300 signups now. 22% click through to the pricing page, 8% take a paid plan in week one. 24 paying users from the waitlist alone.
Compare that to "180 signups, silence for 4 months, single launch email": that pattern usually produces 2 to 6 paying users on the same starting list, not 24.
The follow-up loop is the work. The page is easy.
Capture all of this in the spec
A waitlist isn't just a marketing page; it's a small product, and like any product, it benefits from being specified before it's built. The signup endpoint, the welcome email, the monthly digest, the analytics events for tracking signup source, the unsubscribe link, GDPR-friendly storage of email addresses. All of it.
If you've planned out the full product in Draftlytic, the waitlist is usually one section: a pre-launch landing page with a single CTA that writes to an email list. Specifying it next to the rest of the build means the AI tool wires the form, the email provider, and the analytics from one consistent spec, instead of you bolting a separate waitlist tool on later.
Most indie founders treat the waitlist as a checkbox and then wonder why launch day was quiet. The waitlists that produce a real launch crowd are the ones with a real relationship behind them: a clear promise, a short signup, and three or four honest emails between signup and launch. That's the loop. Build that, and the page does the work it was meant to.