Waitlist: Collecting Emails Before Launch and What the Count Means
A waitlist is a list of people, usually email addresses, who asked to be told or let in when a product is ready. It lets you invite users in batches and gives you a first audience on launch day. The signup count is weak evidence of demand, because joining costs nothing, so measure how many invited people actually use the product.
What is a waitlist, and what is it for?
A waitlist is a promise in two directions. The visitor promises nothing except an email address. You promise to get in touch when something exists. It serves three jobs, and a good one serves at least two: to hold the people who are interested while you build, to let you admit users in controlled batches so that you can watch each group, and to give you an audience to tell on launch day.
Do not confuse it with a launch. A waitlist page is a place to leave an address, and a launch is a place to use a product. That difference matters on some platforms. The Show HN guidelines on Hacker News list sign-up pages and newsletters as off topic, and say not to post landing pages, because readers cannot try them. We read that page on 13 November 2026. If your product exists only as a waitlist, hold your public launch until a person can use something.
Three kinds of waitlist, and which one you have
| Kind | What you tell people | Best when | Watch for |
|---|---|---|---|
| Notify me | “We will email you once, when it opens” | The product is a few weeks away and you want a first audience | People forget why they signed up |
| Invite queue | “We admit people in batches; you will get an invitation” | You can only support a few users at a time | A queue with no visible movement feels like a closed door |
| Early access list | “Join to try it before everyone else” | A working version exists and you want feedback | It blurs into a closed beta, so say which one it is |
Name the kind on the signup page. “Join the waitlist” invites people to imagine something, and “We will email you once, when it opens, and never otherwise” tells them what they get.
Example: a language-exchange app and its first 200 emails
An invented maker is building an app that pairs people to practise a language by voice. A landing page collects 200 emails. The count feels good, and it is not a result. Joining took ten seconds and no commitment. The first email is the real test, and the maker sends one that asks a single question: “Which language would you practise first, and how many minutes a week do you have?”
Thirty people reply, with specifics. Those thirty are the real waitlist. They get invited first, in batches of ten, and the maker watches what each batch does. By the time the doors open to everybody, there are a dozen people who have already used the product and can say so in a public comment. The signup count was never the signal. The replies were.
What should you measure instead of the count?
- First-email response. How many people open it, and how many reply to a direct question? Replies are far stronger evidence than signups.
- Invite acceptance. Of the people you invite, how many create an account within a few days?
- Activation. Of those, how many do the one thing the product is for? This is the number to improve.
- Source. Which channel brought the people who activated? Tag each signup link.
The validate app idea tool and the how to validate an app idea guide help you decide what evidence of demand to look for, and the waitlist to launch plan lays out a schedule from first signup to opening day.
How do you run one without annoying people?
- Say what they will receive and how often. Then do exactly that.
- Confirm the address. A confirmation email catches typos and shows who really wanted in.
- Write to them within a few weeks. A list that hears nothing for months forgets you, and a first message after a long silence needs to remind them who you are.
- Give them a way out. An unsubscribe link in every message is both courteous and expected.
- Collect only what you need. An email address is enough to start. Anything more is a reason to leave the form.
The beta invite email template has wording for the first message to the people who joined.
What goes wrong with waitlists?
The main error is treating the count as validation and building for months behind it. A second is silence: people who signed up in March and hear nothing until October will not remember why. A third is publishing a waitlist as if it were a launch. When the product exists, move people in, and launch your product free so there is a public page they can open. If you are looking for something to build behind a waitlist, the ideas board lists what others want made.
Related terms: an early access programme gives chosen people the product itself, a soft launch is a quiet release that often starts from the list, and an open beta removes the gate.
Frequently asked questions
What is a waitlist?
It is a list of people, usually email addresses, who asked to be told or let in when your product is ready. It lets you admit users in batches, gives you an audience on launch day and gives you a group to ask questions before you build further.
Does a long waitlist prove people want my product?
Not by itself. Joining takes seconds and costs nothing, so a large count can sit beside weak demand. Stronger evidence is replies to a direct question, invitations accepted and invited users who do the product’s main action. Treat the count as a starting audience, not a verdict.
Can I post my waitlist as a Show HN?
No. The Show HN guidelines list sign-up pages and newsletters as off topic and say not to post landing pages, because readers cannot try them. Wait until people can use something, then post it. Until then, share the waitlist with your own contacts or in communities that allow it.
How often should I email a waitlist?
State the plan on the signup page and keep to it. A first message within a few weeks, then updates when something real changes, works better than silence followed by a flood. Always include an unsubscribe link and make the reason for each email obvious.
How is a waitlist different from a beta?
A waitlist holds people who have not yet used the product, and a beta lets chosen people try an unfinished one. Many makers move people from the first to the second. Be clear on the signup page which one you are offering so that people know what to expect.
Written by Post your build ideas with AI assistance and edited for this site. Where a page names another product, the facts came from that product’s own pages on the date shown above; terms change, so check them before you rely on them. About the publisher.