How to Build a Waitlist for Your App (Step by Step, 2026)
A pre-launch waitlist is the cheapest way to find out if anyone wants your idea before you build it. Here is how to set up a waitlist landing page in an afternoon, and collect answers, not just emails.
Posted by

A waitlist is the cheapest way to find out if anyone actually wants your idea, before you spend three months building it. You put up a single page that explains what you are making, ask people to leave their email, and add one or two questions so you learn who they are and what they want. If people sign up, you have a warm list to launch to. If nobody does, you just saved yourself a quarter of wasted work.
This guide walks through the whole thing, from idea to live page, and it covers the part most founders skip: collecting answers instead of just addresses.
Table of contents
What is a waitlist, and why bother?
A waitlist is a simple pre-launch landing page, sometimes called a coming-soon page, that collects emails from people interested in a product before it launches. It does two jobs at once. It validates demand, because real email addresses from real people are a stronger signal than likes or "that sounds cool" comments. And it builds an audience, so that on launch day you are emailing people who already raised their hand instead of shouting into cold traffic.
The honest catch: a waitlist does not create demand, it measures it. You still have to drive people to the page. More on that below.
Step 1: Write one clear sentence about what you are making
Before any tooling, get the pitch down to a sentence. Not a paragraph, a sentence. "A budgeting app that sorts your spending automatically from your bank feed." "A Mac tool that turns meeting recordings into shareable notes." If you cannot explain it in one line, the page will not convert, because visitors decide in about three seconds whether to bother. Write it the way you would say it to a friend, not the way a press release would say it.
Step 2: Decide the one thing you most want to learn
This step separates a useful waitlist from a vanity email list. Pick the single most important question you have about the idea, and plan to ask it on the signup form. Common ones:
- What do you use today to solve this?
- What is the most frustrating part of that?
- What would make this a must-have for you?
- How much would you expect to pay?
You do not need all of them. One good question, answered by people who cared enough to sign up, is worth more than a spreadsheet of anonymous emails.
Step 3: Put up the page
You have a few options, from most to least work:
- Build it yourself. Full control, but you need a domain, a backend, an email service, a form, and a database before you collect a single name. That is a weekend of plumbing before you have learned anything.
- Use a form builder like Tally or Google Forms. Fast, but it is just a form. No newsletter to follow up, no place for feedback later, and you will be exporting CSVs into another tool the moment you want to email anyone.
- Use a waitlist tool. A purpose-built tool gives you a hosted page, email collection, and the survey questions in one place, usually in a few minutes.
Here is how the three options compare:
| Approach | Time to live | Survey on form | Newsletter follow-up | Feedback later |
|---|---|---|---|---|
| Build it yourself | A weekend+ | You build it | You build it | You build it |
| Form builder (Tally, Google Forms) | Minutes | Yes | No, export elsewhere | No |
| Waitlist tool (e.g. Lighthouse) | ~5 minutes | Yes | Built in | Built in |
Lighthouse is built for exactly this. You name your project, write the one-sentence description from Step 1, attach your question from Step 2 directly to the signup form, and you get a live page at a shareable link plus a QR code, in about five minutes. No backend, no four-tool setup.
Step 4: Collect answers, not just emails
Here is the part worth repeating: an email on its own tells you almost nothing. Anyone will hand over an address to "get early access." It costs them nothing, so it proves nothing.
A free email is a maybe. An answer is intent. Collect intent.
An answer is different. When someone takes ten seconds to tell you what they use today or what they would pay, they are showing real intent. By the time you reach 100 signups with a question attached, you do not just have 100 emails, you have 100 short interviews.
The three questions worth asking
You do not need a long survey. Two or three sharp questions on the signup form do more than a ten-field form nobody finishes. These three pull their weight:
- What do you actually need this to do? This surfaces the real job people want done, in their own words. You will often find the feature you were most excited about is not the one they care about. Their phrasing also becomes your marketing copy later, because it is the exact language your buyers use.
- How much would you pay for this? Uncomfortable, and that is the point. A free email proves nothing. The moment someone picks a price, even a small one, they are telling you whether this is a vitamin or a painkiller. If most people pick "free only," that is a finding you want before you build, not after.
- What has failed you about the tools you use now? This is the goldmine. People will tell you exactly where the existing options let them down, which is the gap your product can own. A waitlist full of "I tried X but it was too bloated and Y was too expensive" is a roadmap.
| What you want to learn | Question on the form | Best question type |
|---|---|---|
| The real need | "What would make this a must-have for you?" | Short text |
| Willingness to pay | "What would you expect to pay per month?" | Single choice (price ranges) |
| Gaps in current tools | "What do you use today, and what frustrates you about it?" | Short text |
Keep it to two or three. The willingness-to-pay question is the one founders skip most and regret most, so if you only add one, add that.
Step 5: Drive traffic to it
A live page with nobody on it validates nothing. If you have no audience yet, you still have to go where your people already are:
- Post it in the communities your users hang out in: relevant subreddits, Discord and Slack groups, Indie Hackers.
- Be a useful reply on X and in forums, then link the page when it actually fits.
- List it on "coming soon" directories like BetaList and a Product Hunt upcoming page.
- Use the QR code for offline reach: a sticker, a flyer, your slide at a meetup, a coworking-space board.
None of this is magic. It is reps. The upside is that even 20 to 30 signups with real answers tells you more than a silent list of 200, and it sharpens how you describe the product everywhere else.
Two optional amplifiers once traffic is flowing: show the signup count on the page as social proof ("47 people already joined"), and add a referral link so existing signups can invite others. Neither replaces real distribution, but both lift conversion.
Step 6: Keep the list warm until launch
The mistake is collecting emails and then going quiet for three months. People forget they signed up, and your launch email lands cold. Send the list an occasional short update: what you shipped this week, a screenshot, a question. A few light touches keep the audience warm so that on launch day they actually open the email.
When you launch, email the whole list at once, and consider dropping a pre-order or payment link in that first message. Money in is the only validation that fully counts, and a warm waitlist is the best place to test it.
How many signups is "enough"?
There is no universal number, but some rough guidance for an indie product:
| Signups before launch | What it usually means |
|---|---|
| Under 20 | Weak signal, or you have not driven enough traffic yet. Keep testing the pitch. |
| 50 to 100 | A real starting audience, especially if the survey answers are specific and consistent. |
| Several hundred+ | Strong demand. Focus shifts to converting them to paid at launch. |
The quality of the answers matters as much as the count. Twenty people describing the exact same pain in their own words is a better sign than two hundred blank emails.
Watch: building a waitlist before you launch
If you would rather see the idea explained, this video covers using a waitlist as a pre-launch validation step for indie projects:
Frequently asked questions
Do I need a finished product to start a waitlist?
No. The point is to put up the waitlist before you build, so you learn whether the idea is worth building at all.
Should I ask for more than an email?
Yes, one question at least. The answers are the real value. Keep it to one or two on the signup form so you do not scare people off, and save deeper questions for a follow-up survey.
What do I do with the emails after launch?
Email them. A waitlist is also your first newsletter list. Tools like Lighthouse let you import your signups straight into a newsletter and send your launch announcement without exporting anything.
Is a free form builder enough?
For pure email capture, yes. But the moment you want to follow up, survey the list, or collect feedback, a form builder leaves you stitching tools together. A waitlist tool keeps it in one place from the start.
A waitlist is the smallest possible experiment that still tells you the truth: do real people want this? Put up one clear page, ask one good question, drive a little traffic, and keep the list warm. You will know within a few weeks whether your idea has a pulse, and you will have your first 100 users waiting when it ships.
Lighthouse lets you build a waitlist with survey questions, a newsletter, and a feedback inbox in one place, free to start. From an indie dev, for indie devs and makers.