What a waitlist means
A waitlist is a queue of people who have asked for access to a product before it is generally available. "Waitlist" and "wait list" mean the same thing, and the one-word spelling is what product companies use.
Being on a waitlist means you have given an email address and are waiting for an invitation, which the company sends in batches as it opens capacity. A waitlist launch is an announcement whose call to action is that queue. The product itself opens later.
What a waitlist launch is for
A general-availability launch converts attention into usage, and the measure is signups who did something. A waitlist launch converts attention into intent, and the measure is a list of people who said they want this before they could have it.
Those are different products and they need different launches. The first has to answer "is this any good". The second has to answer "is this worth waiting for", which is a harder question because the reader cannot check.
Two situations make a waitlist correct. Capacity, where letting everyone in genuinely breaks something. And readiness, where the product works for a narrow set of use cases and a flood of the wrong users would produce a wave of accurate bad reviews.
One situation makes it wrong: using a waitlist as a marketing device on a product that would have worked fine for everyone. Readers can tell, and it converts curiosity into mild irritation. If you can let people in, let them in.
What to show when nobody can use it
The hard constraint is that your strongest asset, someone trying it, is unavailable. What replaces it is other people's experience of it.
- The artefact. The output the product produced. A diff, a generated file, a completed task. It is inspectable even by someone who cannot run it.
- A real run, with the failures in. A screen recording of the product working, including where it struggles, is more persuasive than a polished film and takes an afternoon. More on that trade here.
- Early users, in their own words. A handful of people already inside, posting what they did with it. This is the single most effective asset a waitlist launch has, and it requires letting a few people in early specifically so they can say something.
- The limitation. Saying plainly what it does not do yet is the most credible thing on the page, and it filters the queue towards people who will be happy when they arrive.
The pattern underneath all four is that a use case someone can picture themselves copying does more than any claim about capability. That mechanism is here, and it matters more in a waitlist launch than anywhere else, because copying is the only thing your reader can do with the information.
Scarcity works, and it expires
Seeing something you cannot have is a genuine driver. Somebody who reads a use case, wants to try it and finds a queue will often join, follow the account, and keep watching. That is the mechanic a waitlist is buying.
It has a short half-life. Scarcity is interesting while a person still remembers wanting the thing, and most people forget inside a fortnight. A queue that is not moving stops being exclusive and starts being evidence that the company is not shipping.
So the design decision that matters is throughput. A waitlist you invite from weekly stays credible. A waitlist that has not moved in two months has become a list of people who will not remember you when the email arrives.
The four days after
The signup curve on a waitlist launch is steep and short. Most of what you will get arrives while the launch is still being discussed, which is a window of days rather than weeks.
One client added more than 10,000 waitlist signups in the four days after their launch. What decided whether that was worth anything was what reached those 10,000 people over the following fortnight, and how quickly the first of them got in.
Two things are worth having ready before launch day, because neither can be built during it:
- A first invitation batch that goes out inside a week. Even a small one. It converts the list from a promise into a functioning queue and gives you early users who can post about it.
- Something to send everyone else. A note that acknowledges them, sets an expectation about timing, and gives them one interesting thing. Silence after signup is the most common way this is wasted.
Feeding the queue
Treat the list as an audience rather than a database. Something every week or two, aimed at making the wait feel like access.
| Send | Why it works |
|---|---|
| Use cases from people already inside | Renews the reason they joined, and it is the content they cannot get anywhere else. |
| A decision and the reasoning | Being told why you built something a particular way makes a person feel early rather than queued. |
| A limitation you fixed | Shows movement, and is more believable than a feature announcement. |
| Position in the queue | Concrete, honest, and gives a reason to open the next one. |
The same material works publicly. Every one of those posts is worth amplifying, which keeps the account warm between the launch and general availability rather than going quiet for a quarter. That gap is where most waitlist launches lose whatever they built, and it is entirely avoidable.
Questions we get asked
Should we launch to a waitlist or to general availability?
If you can let people in, let them in. A waitlist is correct when capacity, cost or reliability genuinely limits how many users you can support, and it is a mistake when it is used as a marketing device on a product that would have worked for everyone. Readers can tell the difference and resent the second one.
How many signups should a waitlist launch produce?
It is a function of qualified reach and how much friction sits between the post and the form. One client added more than 10,000 waitlist signups in the four days after their launch. The number that matters more is what share of the list is still opening your emails a month later, because a queue that goes cold converts at close to nothing.
What do we send the waitlist after launch?
Something every week or two that makes the wait feel like access rather than a queue. Use cases from people already inside, a decision you made and why, a limitation you fixed. The purpose is that when the invitation arrives the person remembers signing up and still wants it.