Four hundred people joined your waitlist. What do you now know?
You know four hundred people typed an email address into a box. That is a real fact and it is worth something. It is also the entire fact, and most of what founders do next assumes it was a larger one.
We sell waitlist software, so this is an odd thing to lead with. It is also the reason the product
exists in the shape it does, and it is enforced in the codebase: scripts/check-copy.mjs scans every
file in this repository against a list of sentences we are not allowed to write, and phrases about
signups establishing demand are on it. The guard exists because those sentences are the ones you
reach for when writing a headline, and a company that sells evidence-gathering should not oversell
what its own evidence is.
What the number actually contains
A signup is one person's decision at one moment, made under conditions that will never repeat: they had just read your landing page, they were in the mood, and it cost them nothing.
Three things are already true of that number before you do any analysis.
Some of those addresses are not people. Disposable domains, bots that fill forms because forms exist, and — the moment you add a referral mechanic — people gaming a queue position. If you do not verify, you do not know your denominator. Double opt-in is the cheap fix and it is free on every plan, including the free one, precisely because a product that let you build strategy on an unverified count would be selling you a worse number than you had before.
The cost of signing up was zero and the cost of buying will not be. Everything you infer has to survive that gap.
Your traffic source is doing most of the work. Four hundred signups from a post that went well on one forum tells you about that forum. The same four hundred from cold search tells you something much closer to what you wanted to know. If you are not tracking where they came from, the number has no denominator and no context.
The stated-price question, and its exact limits
Ask people what they would pay, and some will tell you. It is the single most useful question a signup form can carry, and it is routinely over-read.
A stated price is a statement, not a payment. Nobody on a waitlist has transacted. The gap between what people say they would pay and what they do pay is well known to anyone who has run both and it runs in one direction. That does not make the answer worthless — it makes it a comparative instrument rather than an absolute one.
What it is genuinely good for:
- Ranking. If the $19 answers outnumber the $9 answers three to one, that ordering is informative even though neither number is a forecast.
- Finding the cliff. The point where willingness falls off a shelf is usually visible, and it is usually not where you guessed.
- Segmenting. The people who said $49 are a different population from the ones who said $9, and the difference between what those two groups wrote in the free-text box is often the most valuable thing on the whole form.
What it is not good for: putting a number in a financial model. Osokoro shows a recommendation
alongside these answers and it carries a disclaimer saying, in as many words, that it is not a
guarantee of demand, revenue or future purchases. The thresholds behind that recommendation are in
VERDICT_THRESHOLDS in packages/domain/src/validation.ts, and the product links to them from the
page, because a heuristic that will not show its cutoffs is asking for more trust than a heuristic
deserves.
The evidence that actually survives
Ranked by how much it tells you, weakest first:
- A signup. Somebody typed an address.
- A verified signup. The address exists and its owner clicked a link. You now have a person.
- An answer to a specific question. What they are using today, what it costs them, what broke last week. Free text here beats every multiple choice, because the words they choose are the words your landing page should use.
- A stated price. Comparative, per above.
- A referral. They put their own reputation in front of someone they know. This is the first signal on this list that costs the person anything.
- A reply to an email you sent them. Effort, unprompted, weeks later.
- Money. Not available from a waitlist, by construction.
Most founders optimise position 1 and read the result as though it were position 6. The interesting work is moving people down the list, and the useful thing about a waitlist is that it is a mechanism for doing exactly that — not an oracle you consult at the end.
The uncomfortable one: silence is data
The clearest signal a waitlist produces is usually the one nobody counts. If you send a real email to four hundred verified addresses and almost nobody replies, opens, or clicks, you have learned something sharper than any of the positive numbers, and it is available weeks before launch.
That is the argument for lifecycle email being part of a waitlist product rather than something you bolt on later. A list you never write to is a list you never tested.
Worth flagging: the shared sending domain works on every plan. Everything includes one custom sending domain and Studio allows several; add the domain, publish its DKIM records, and mail stays on the shared domain until verification completes.
What to do on Monday
- Turn on double opt-in. Know your denominator.
- Ask one free-text question about what they do today. Read every answer yourself, all of them, and do not summarise until you have.
- Ask a price question, and treat the shape of the distribution rather than its mean.
- Tag your sources. A number without a source is a number about your friends.
- Write to the list within two weeks, with something real, and count replies rather than opens.
None of that tells you to build. It gives you a set of facts that are actually facts, which is a better position than the one where a large number on a dashboard did your thinking for you.