How to Use a Waitlist to Validate Demand
By Omar Zidan, Founder
An email address in a database is not validation. It is the cheapest signal to fake with a decent landing page and a Twitter thread. Founders launch a landing page, collect two thousand emails, and spend six months building a product nobody buys. To validate demand, a waitlist must cost the user something. That cost can be time, money, or social capital. If a visitor is not willing to pay one of those prices, they are not a potential customer. They are a tourist.
The Baseline Math of a Standard Waitlist
Let us look at the arithmetic of a standard, email-only waitlist. Lenny Rachitsky tracks consumer app metrics and notes that a typical waitlist converts at around 10 percent to 20 percent for free products. For B2B or paid products, the number drops significantly. Assume you collect 10,000 emails on a simple landing page. You might think you have a guaranteed user base. You do not.
When you finally launch, the first hurdle is deliverability. Spam filters, corporate firewalls, and promotional tabs will swallow 15 percent of your list immediately. You are left with 8,500 emails in actual inboxes. A generous open rate for a product launch is 40 percent, leaving you with 3,400 people who even see your message. Of those, perhaps 15 percent click the link to your app. You now have 510 warm visitors. If your product requires a paid subscription, a standard conversion rate from a warm visitor to a paid user is 3 percent. You have just turned 10,000 waitlist signups into 15 paying customers. The raw signup number is a vanity metric. You cannot take it to the bank, and you certainly should not use it to justify quitting your day job. You must force the drop-off to happen before you build the product, not after.
The Time Cost: Qualifying Questions
You make a waitlist mean something by adding friction. The simplest friction is a qualifying questionnaire. Superhuman famously used this method before opening their premium email client to the public. They did not just ask for an email address. They asked what browser the user preferred, what email client they currently used, and what keyboard shortcuts they relied on.
You must do the same. Ask three specific questions. First, ask what tool they currently use to solve the problem. Second, ask how much they pay for it. Third, ask what their biggest frustration is with that current tool. You can build this using Tally or Typeform. Pass the email address from your landing page directly into the form via URL parameters so the user does not have to type it twice.
If a user cannot be bothered to type out a twenty-word answer, they do not have a burning problem. They will not survive your buggy version one. You will lose 70 percent of your signups by adding this form. That is the entire point. The 30 percent who remain represent genuine demand signals. You can read their answers, identify your exact ideal customer profile, and build exactly what they are asking for. If you see that 80 percent of your qualified signups point out the exact same missing feature in a competitor, your product roadmap writes itself.
The Money Cost: Small Deposits
The ultimate validation is a credit card swipe. If you want to know if people will pay for your product, ask them to pay for it before it exists. You do this by asking for a small, refundable deposit. Tesla validated the Model 3 by taking a thousand-dollar deposit years before production began. You can validate your software by taking a ten-dollar deposit.
Set up a Stripe payment link. Offer a compelling trade. Tell visitors that a ten-dollar deposit secures them a lifetime 50 percent discount when the product launches, or guarantees them access to the first beta cohort. If they pay, you have absolute proof of life. If you get 100 people to pay ten dollars, you have infinitely more validation than 10,000 free email signups.
If you build the product and it fails, you refund the money. If you decide not to build it, you refund the money. The deposit filters out the aspirational users and leaves only the desperate ones. A user willing to open their wallet for a promise is a user who will tolerate early bugs and provide actionable feedback. It also changes the psychology of the launch. When you email a free waitlist, you are asking for a favor. When you email a deposit list, you are delivering on a promise.
The Social Cost: Referral Mechanics
If you cannot ask for money, ask for social capital. A referral mechanic forces users to spend their reputation to get your product. Robinhood pioneered this by showing users their exact place in line, and moving them up thousands of spots if they invited a friend. You do not need a custom engineering team to build this. Tools like Prefinery or Viral Loops handle the mechanics out of the box.
The metric you are looking for here is the viral coefficient, commonly called the k-factor. You calculate the k-factor by multiplying the number of invitations sent per user by the conversion rate of those invitations. If 100 users sign up, and they collectively invite 20 friends who also sign up, your k-factor is 0.2. A k-factor above 0.15 on a waitlist is a strong demand signal. It means the problem is painful enough that people are willing to annoy their colleagues to solve it faster. If your k-factor is zero, your product is either a secret or a vitamin. Neither is a good foundation for a new business.
Matching Friction to the Market
The type of friction you apply depends entirely on your market. Business-to-business and consumer waitlists behave differently. In a consumer market, attention spans are short and alternatives are plentiful. A consumer waitlist relies heavily on the referral mechanic. You want social proof and virality. If you are building a new social network or a personal finance tracker, a money deposit will likely kill your conversion rate completely. Instead, you force the social cost. You make them tweet about the product to gain access.
In contrast, a business-to-business waitlist should almost never use a referral mechanic. Professionals do not want to spam their colleagues with untested software. For B2B products, the time cost and the money cost are your best tools. A founder looking for a new tax reconciliation tool will happily fill out a ten-minute questionnaire if they believe it will save them hours of manual data entry later. They will also happily expense a ten-dollar deposit. You must match the friction to the audience.
Sourcing the Initial Demand Signals
Before you can put up a waitlist, you need a hypothesis. You need to know what landing page to build. You do not get this by guessing. You get it by finding places where people are already asking for a solution. You look for demand signals in forums, Reddit threads, and GitHub issues.
If you do not want to scrape these corners of the internet manually, you use Unthinkable. It is an iOS app that surfaces business ideas directly from real demand signals across the web. Once you see a pattern of people asking for a specific workflow automation or a missing API, you build the landing page for that exact missing piece. You use their exact words in your headline. Then you drop the link back into the conversation. You do not need to spend money on ads to test a waitlist. You just need to put the right friction in front of the right audience.
Executing the Launch
When you finally ship, you must execute the launch correctly to preserve the validation you worked so hard to measure. Never blast your entire waitlist at once. You will have onboarding bugs. If you send 1,000 emails on day one, 1,000 people will hit the same broken authentication flow, and you will burn your best leads.
Divide your waitlist into cohorts of 50. Send the first 50 emails on a Tuesday morning. Watch them click through. Watch them fail. Fix the bugs on Wednesday. Send the next 50 emails on Thursday. By the time you reach the users who paid a deposit or referred friends, your onboarding must be flawless. Measure the activation rate of each cohort separately. The users who filled out the long-form questionnaire should activate at 40 percent or higher. If they do not, your product does not solve the problem your landing page promised to fix. You validated the demand, but you failed the execution.
Concierge Onboarding for High-Intent Users
For your highest friction signups, do not rely on automated emails at all. Use concierge onboarding. If someone paid a deposit, send them a personal email asking to book a fifteen-minute call. Superhuman did a 30-minute video call for every single waitlist activation in their early days.
You watch them share their screen. You watch them try to navigate your interface. You will see exactly where they get confused. This does not scale, which is exactly why you do it. You are not trying to scale yet. You are trying to turn a validated demand signal into a successful, paying customer. A waitlist is only a proxy for demand. The only true validation is retention. By forcing friction at the signup stage, you ensure that the people you onboard are the ones most likely to stick around. When you sit on a call with a user who paid a ten-dollar deposit six months ago, and you watch their face light up when your software solves their problem, you will know the waitlist did its job.
Questions
How long should a waitlist remain open before launching?
Do not keep a waitlist open for more than three months. Demand goes stale quickly, and users will simply find an alternative solution if you take too long to ship. If you need more time to build, launch a closed beta to a small cohort to maintain momentum.
What is a good conversion rate for a paid waitlist?
A standard email waitlist converts at around 10 percent to 20 percent for free products. If you require a deposit upfront, you can expect 60 percent to 80 percent of those users to activate when the product launches. The upfront friction drastically increases the final conversion rate.
Should I use a double opt-in for a waitlist?
Yes, you must use double opt-in. Spam bots will fill a single opt-in form with thousands of fake emails, ruining your metrics and destroying your sender reputation. A double opt-in ensures the email is real and the user has enough intent to click a confirmation link.
How do I keep a waitlist warm while building the product?
Send a plain text update every three weeks. Share a screenshot of the product, explain one technical hurdle you overcame, and remind them of the problem you are solving. Do not send marketing fluff or heavily designed newsletters.
