Ways to run the test
How do I build a waitlist before launch?
Updated 19 August 2026 · Thresholds read live from the verdict engine
Short answer
A waitlist page needs one promise, one field and a consent line that says what you will send. Fill it from communities where your audience already gathers, or from paid traffic at roughly $1 to $4 an email, then message the list every two or three weeks so it is still alive at launch. Treat it as reach rather than revenue: cold-sourced lists convert somewhere around 2% to 5% into paying customers on launch day.
What a waitlist is good for, and what it is not
A waitlist buys you three things: an audience on launch day, a channel for asking questions while you build, and a small early signal about the promise. It does not tell you whether people will pay, because an email costs nothing to give and giving it is often just politeness at internet scale.
The failure mode is famous. Founders collect 2,000 signups, take it as proof, build for six months, launch to that list and sell 40 copies. Nothing went wrong in the arithmetic. The list was measuring interest and the launch needed commitment.
The page, and the consent line most people get wrong
Keep the page to one screen. Product name, one-line promise, an image, one email field, one button, and the consent sentence underneath.
- Ask for the email and nothing else. Every extra field costs you signups. A name is optional at best.
- Say what they will get and how often. "One email when it launches, and occasional progress notes" is enough, and it is a promise you have to keep.
- Separate marketing consent from the signup. In the EU and UK, consent has to be specific and freely given, so a pre-ticked box that bundles marketing into the signup is a problem. A clear checkbox for launch news, unticked or plainly labelled, keeps you clean.
- Name who is collecting the data. A link to a short privacy page, and a working unsubscribe in every email you send afterwards.
- Add a honeypot field. An input hidden from humans that bots fill in. It removes most junk signups without a captcha.
- Confirm on the next screen. Tell them what happens next and when. This is also the best place in the whole flow to ask for the second, harder commitment.
Double opt-in (a confirmation click in an email) costs you 10% to 25% of your list and buys you deliverability, since it removes typos and bot addresses. Worth it if you plan to send anything before launch, which you should.
Where the first 500 emails come from
| Source | Realistic yield | Cost | Quality at launch |
|---|---|---|---|
| Paid traffic (Meta, TikTok) | 5% to 15% of visitors | $1 to $4 per email | Weakest. They met you once. |
| A community you belong to | 20 to 200 per post | Your reputation | Strong, if you were a member before you needed something. |
| Your own audience | 1% to 5% of followers | Free | Strongest, and finite. |
| Launch directories and newsletters | 50 to 500 in a spike | Free to $200 | Mixed. Lots of founders, few buyers. |
| Referral loop on the confirmation page | 10% to 30% uplift | Build time | Same as the source it amplifies. |
The referral loop is worth the afternoon it takes. Robinhood's pre-launch list famously grew to about a million people on a queue-position mechanic, where sharing moved you up the line. You will not see numbers like that, but a position counter and a share link routinely add a fifth to a list at no additional media cost.
Keeping the list alive until launch
A list decays. People change jobs, change addresses and forget who you are. A list left silent for six months converts far worse than one that has heard from you every fortnight, and it also lands in spam more often because the addresses have gone cold.
- Send something every two to three weeks. Short. What you built, one decision you are stuck on, one screenshot.
- Ask a question in the first email. "What are you using today?" gets replies, and replies teach you the language for the launch page.
- Give the list a reason to be early. Founding pricing, a lifetime rate, a first-fifty slot. State the terms and honour them.
- Warn them before launch day. One email a week ahead, one on the day. Launch-day sales concentrate in the first 48 hours.
Worked example
What a list is worth on the day
A founder collected 1,400 emails over four months: 900 from $1,800 of ads, 400 from two community posts, 100 from their own audience. At launch they sold a $59 annual plan.
- Launch email open rate: 41%
- Click through to the page: 9% of the list
- Purchases in the first week: 48, which is 3.4% of the list
Revenue was about $2,800 against $1,800 of media spend to build the list. The paid portion roughly paid for itself and the community and audience segments carried the margin. Worth doing, and nowhere near the picture "1,400 people are waiting" paints in your head.
The numbers
Email capture has its own bands in the verdict engine, measured against the visitors who actually reached the email step rather than everyone who landed.
Under 8% means the step is leaking and you are measuring your form rather than your promise. At 25% and above the step is doing its job. This number never decides on its own: a funnel can capture emails beautifully and still fail at the paywall, which is exactly the case where a waitlist would have told you to build.
- Funnel starts before any verdict
- 30
- Below this, don't build
- 1.0%
- At or above this, build
- 2.0%
- Visitors before a segment counts
- 50
How VerifyToLaunch does this
VerifyToLaunch generates a pre-launch waitlist page alongside the funnel, with the consent checkbox, the honeypot and a confirmation screen already in place. Emails land in your dashboard and export as CSV whenever you want them. The funnel itself also collects an email mid-flow, so you get the reach and the commitment number from the same traffic.
We do not send your launch campaign. There is no drip sequence, no broadcast tool and no deliverability management here, so plan on exporting to whatever you use for email. If all you want is a waitlist, a dedicated tool or a $10 a month email platform will serve you better than we will.
Common questions
- How many waitlist signups should I get before building?
- The count matters less than what it converts into. Multiply the list by 2% to 5% for a cold-sourced list, or 5% to 15% for one built from your own audience, and ask whether that many customers justifies the build. A thousand cold emails is usually twenty to fifty buyers.
- What conversion rate should a waitlist page get?
- On cold paid traffic, 5% to 15% of visitors giving an email is a normal range for a single-field page with a clear promise. Warm traffic from a community or your own audience runs several times higher, which is why the two should never be averaged together.
- Do I need double opt-in?
- Not legally in most places, but it protects deliverability by removing typos and bot addresses. Expect to lose 10% to 25% of raw signups to the confirmation step and to gain that back in inbox placement later.
- Is a waitlist enough to decide whether to build?
- On its own, no. It measures curiosity, and curiosity is cheap. Put a price and a commitment step behind the confirmation screen if you want the list and an answer from the same traffic.
Read next
- How many signups mean an idea is worth building?Signups are the wrong unit. Here is how to convert a list into expected buyers.
- What is a fake door test and how do I run one?Offer the thing before it exists, count who reaches for it, and stay on the right side of the ethics line.
- How do I find out if people will actually pay?Three ways to collect a paying signal before you build, and the CAC maths behind the rate.
- How do I validate an app idea?The whole method: pick a commitment that costs the visitor something, buy cold traffic, count who commits.
Collect the list and the answer together
The generated waitlist page handles consent and confirmation, and the funnel behind it asks the harder question at your price. Same traffic, two numbers, one dashboard.
One-time licence, 30-day money-back guarantee