The waitlist, and what it is actually worth
A thousand emails is not a thousand customers, and treating it as one is how founders build the wrong thing confidently.
The short version
- A waitlist measures interest, not demand. An email costs nothing to give.
- Plan for 2–10% converting at launch. Anything more is luck.
- Ask one question beyond the email. It is worth more than the address.
- Email every two to three weeks or the list goes cold and complains.
- The replies are the point. The count is a by-product.
What does a waitlist actually tell you?
That a number of people found your description of a problem interesting enough to spend four seconds on. That is genuinely useful: it is evidence that the problem is legible and that your explanation of it lands. It is not evidence that anyone will pay, because nothing on a waitlist page costs the visitor anything.
This is the distinction that matters, and the one that gets blurred by everybody posting screenshots of signup counts. Interest is cheap and abundant; demand is expensive and rare. A waitlist measures the first and is routinely reported as though it measured the second.
An email address is what people give you instead of money.
Validating a SaaS idea covers what does count as evidence. The short version: a pre-order, a deposit, or somebody describing their current workaround in painful detail. A waitlist signup is a weak signal that becomes a strong one only when you follow it with a conversation.
What goes on the page?
The same thing as a landing page, shorter: what it does, who it is for, one picture of the product or a mockup, and one field. Waitlist pages fail for exactly the reason landing pages fail: a headline that describes a category rather than an outcome, so the visitor cannot tell what they are signing up for.
- A headline stating what the software does, concretely. Not "the future of X".
- One sentence of mechanism underneath: for whom, how.
- Something visual. A screenshot if it exists, a mockup if it does not. Never nothing.
- One field, and one optional question. Every extra required field costs you signups.
- When it is coming, honestly. "Early 2027" beats silence and beats a date you will miss.
- Who is building it. A name and a face convert better than an anonymous company voice.
Everything in the SaaS landing page, section by section applies, at a third of the length. The one addition is the question.
The one question worth asking
"What are you using at the moment?" or "What is the part of this that is painful for you?" (optional, one line, after the email field). It reduces signups slightly and it is the most valuable thing the page produces, because it turns a list of addresses into a list of described problems you can sort, count and build against.
Read the answers weekly, in one sitting. Forty answers to that question is better positioning research than any amount of competitor analysis, and it will frequently tell you that people want a narrower product than the one you are building.
How do you keep it warm?
Email every two to three weeks with something worth reading: progress, a decision you made, a screenshot, a question. A list that hears nothing between signup and launch has forgotten you, and the launch email lands as though it came from a stranger who bought their address.
| When | Content | |
|---|---|---|
| Welcome | Immediately | What it is, when, and a reply invited |
| Progress | Every 2–3 weeks | One screenshot, one decision, one question |
| Early access | 2–4 weeks before | A small group, chosen from the repliers |
| Launch | Day one | Short, one link, a reason to act now |
| Follow-up | Day 4–7 | To non-openers only, different subject line |
The progress emails have a second job beyond retention: every one is an invitation to reply, and the people who do are your beta group, your first customers and the source of every useful thing you will learn before launch. Ask a real question in each one.
What should you expect at launch?
Two to ten per cent of a cold list converting to a paid customer, and that range is wide because list quality varies enormously. A thousand signups from one viral post might produce twenty customers; two hundred from people who described their problem to you might produce forty.
| List of | From | Expect |
|---|---|---|
| 1,000 | A viral post or a launch directory | 10–40 customers |
| 1,000 | Steady content in your niche | 40–100 customers |
| 200 | People you spoke to individually | 20–60 customers |
Which is the argument against optimising for size. A waitlist built from a directory submission is mostly other founders collecting competitors; a waitlist built from people who found you explaining their problem is a customer list that has not paid yet. The second is smaller and worth several times more.
The failure modes
- Treating the number as validation. Building for six months on the strength of a signup count is the most expensive mistake on this page.
- Silence. Four months of nothing, then a launch email, then spam complaints.
- Referral gimmicks. Position-jumping mechanics inflate the list with people who wanted the position, not the product.
- Launching to the list only. A waitlist is one channel, not a launch: how to launch a SaaS is the rest of it.
- Waiting for a round number. The list is not the gate. The product working is the gate.
The version that is actually worth doing
Put up a one-page site the week you start building, ask the one question, email every fortnight, and talk to everyone who replies. Then judge the idea on those conversations rather than on the count, because the conversations are the thing a waitlist is genuinely good at producing, and the number on the page is the part everybody else is looking at.
Done that way it costs an afternoon and a fortnightly email, and it produces the two things a solo founder is actually short of before launch: a small group of people who will use the first version and tell you the truth about it, and a clear description of the problem in other people's words. The first ten customers usually come from that group rather than from the launch: your first SaaS customers is where that goes next.
Frequently asked questions
What is a good waitlist conversion rate?
Plan for 2–10% of a cold waitlist converting to a paid customer at launch, and treat anything above that as a pleasant surprise. A small list built from people who described their problem to you converts far better than a large one collected from a viral post.
How many people should a waitlist have before I launch?
There is no threshold worth waiting for. A hundred engaged signups you have spoken to is more useful than five thousand who clicked once. Launch when the product solves the problem, not when the list hits a round number.
Should I ask for anything besides an email?
One optional question: what are you currently using, or what is the problem you want solved. It costs a small amount of conversion and it is the single most valuable thing on the whole page: it tells you who signed up and why.
How often should I email a waitlist?
Every two to three weeks, with something worth reading. A list that hears nothing for four months does not remember signing up, and unsubscribes and spam complaints spike on the launch email.
Is a waitlist worth building at all?
Yes, but for the conversations rather than the count. The people who reply to your emails before launch are your first customers, your beta testers and your positioning research. The list is the by-product.
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.