LaunchRepoShort answer
- Put one clear promise, who it is for and a single email field above everything else. Every extra field costs signups, so ask at most one question.
- Confirm each signup with a link (double opt-in). It keeps typos and fake addresses off the list and gives you a record of who agreed to hear from you.
- Send a welcome message right away and short progress notes while you build, so people still remember you when you open.
- Invite the list before your public launch. Product Hunt does not feature waitlisted products unless people get immediate access, so launch there once anyone can sign up and use it.
The six parts of a waitlist page
This is our own schematic, not a copy of anyone else’s page. The order matters: a visitor should understand the promise and the next step without scrolling.
| Part | Job | Get it right |
|---|---|---|
| 1 Promise | Says in one line what people get once it exists. | Describe the outcome, not the technology. If it takes a second sentence, it is not clear yet. |
| 2 Who it is for | Lets the right people recognise themselves and the wrong ones leave early. | Name a role or situation. A narrower list gives you better feedback and better launch-day users. |
| 3 Honest proof | Answers “why should I believe this will ship?”. | Use only what is true today: a screenshot of the working prototype, your track record, a date. No invented user counts or logos. |
| 4 Form | Collects the email and, if you want, one answer. | One email field, one optional question, one button. A labelled field and an unticked consent box keep it accessible and clean. |
| 5 What happens next | Sets expectations for after the click. | Say what they will receive and roughly when. It lowers anxiety and makes the confirmation email expected. |
| 6 Privacy line | Shows that leaving an email is safe. | Link your privacy policy and say how to unsubscribe. Keep it short and next to the button. |
Waitlist kit generator
Fill in a few facts and get a ready signup form plus the four emails in your own words. Copy them into the email or form tool you already use; LaunchRepo does not collect or store any signups.
Runs only in your browser. Nothing you type is sent or stored.
Preview
Preview only: this form does not send anything.
Form HTML
Emails
Replace the tokens in square brackets with your own links and address, for example [CONFIRM-LINK] with the confirmation link your email tool creates.
The four emails
Four messages cover the whole wait. Each one has a single job, and the reply-to address should reach a real person.
| When | Its job | |
|---|---|---|
| Confirmation | Immediately after signup (double opt-in only) | Proves the address works and that this person wants your emails. Nothing else in it. |
| Welcome | Right after the confirmation click | Repeats the promise, says when you plan to open and asks one question they can answer by reply. |
| Progress update | Only when something real changed | Shows progress with one concrete thing and one change you made because of their replies. |
| Launch invite | The day access opens, before any public launch post | Gives direct access and one first step that shows the promise, then asks for feedback. |
Pick a rhythm you can keep. Two honest updates are better than a weekly newsletter that stops after three issues.
Consent and email rules
A waitlist is a list of personal data used for email. These are the rules that shape the form and the four emails above.
Quotes are the original English wording, copied from the pages listed under Sources and checked on September 30, 2026.
Consent and email
| Rule | Official wording | What it means for you |
|---|---|---|
| GDPR, recital 32 | Silence, pre-ticked boxes or inactivity should not therefore constitute consent. | The consent box must start unticked, and a signup needs an active click. The generator never pre-ticks anything. |
| GDPR, Art. 7(1) | the controller shall be able to demonstrate that the data subject has consented to processing of his or her personal data | You need a record of who agreed. A confirmation link (double opt-in) plus the signup time is a common, simple way to keep one. |
| GDPR, Art. 7(3) | It shall be as easy to withdraw as to give consent. | Leaving must be as easy as joining: one unsubscribe link in every email after the confirmation. |
| CAN-SPAM (USA) | Your message must include your valid physical postal address. | Commercial emails, such as the launch invite, carry a postal address. The kit adds a [POSTAL-ADDRESS] line for it. |
| CAN-SPAM (USA) | You must honor a recipient’s opt-out request within 10 business days. | Unsubscribes have to take effect quickly. Use a tool that removes people automatically. |
| Gmail sender guidelines | Marketing messages and subscribed messages must support one-click unsubscribe, and include a clearly visible unsubscribe link in the message body. | For larger sends, Gmail expects one-click unsubscribe. Most email tools add the needed headers; keep the visible link too. |
The form itself
| Rule | Official wording | What it means for you |
|---|---|---|
| HTML email field | The input value is automatically validated to ensure that it's either empty or a properly-formatted email address | type="email" lets the browser catch obvious typos before submit, without any script. |
| Labels (W3C WAI) | Whenever possible, use the label element to associate text with form elements explicitly. | Each field gets a visible label linked by for/id, so screen readers announce it and a click on the text focuses the field. |
This is a practical summary of the texts quoted here, not legal advice. Check the rules for the countries you collect emails in.
Turning the list into users
The list only pays off if you invite it at the right moment. Product Hunt’s own rules make the order clear.
| Rule | Official wording | What it means for you |
|---|---|---|
| What Product Hunt does not feature | Waitlisted products (unless immediate access is provided) | A launch that only collects emails will not be featured. Launch there once people can actually use the product. |
| Available products only | We only feature products that are currently available. | Same rule from the other side: Product Hunt is for launch day, the waitlist is for the time before it. |
| Common pre-launch mistake | Asking your community to join only on the day of your launch and not before. | Gathering your people before launch day is exactly what a waitlist is for. |
- Open to the list firstSend the launch invite a few days before any public launch. Early users find the rough edges while you can still fix them quietly.
- Fix what they reportAnswer every reply personally in the first days. That feedback is the real reason to have a list.
- Then go publicLaunch on Product Hunt and elsewhere once access is open to everyone. Tell your list the date so the people who like the product can follow along, without asking anyone for upvotes.
- Keep the list aliveAfter launch the list becomes your first customer newsletter. Keep the promise from the signup page: useful and not too often.
What to measure
Count a few numbers from the first signup on. They show whether the promise is working long before launch day.
| Number | How to count it | What it tells you |
|---|---|---|
| Signups per week | New confirmed addresses per week, with where they came from. | Which channels bring interested people, not just visitors. |
| Confirmed share | Confirmed addresses divided by form submissions. | A low share points to typos, fake signups or a confirmation email that lands in spam. |
| Answers to your question | Share of signups who answer the question or reply to the welcome email. | How strongly people care, and in their own words. |
| Invited people who start | On launch day: invited addresses that complete the first step in the product. | The only number that shows the waitlist turned into users. |
We publish no benchmark rates here: they depend on your audience and channel. Compare your own weeks with each other.
Sources
Every rule and figure on this page comes from one of these pages. We read all of them on September 30, 2026; the middle column shows a last-update date only where the page itself gives one.
FAQ
- Do I need a waitlist at all?
- Not always. If people can use the product today, let them sign up for the product instead. A waitlist makes sense while you are still building and want to learn who is interested and why.
- Should I use double opt-in for a waitlist?
- In most cases, yes. A confirmation link keeps typos and fake addresses off the list and gives you a record of consent, which the GDPR asks you to be able to show. The generator adds the confirmation email when you tick the option.
- How many fields should a waitlist form have?
- One email field and at most one optional question. Every extra field makes signing up harder, and one good answer per person tells you more than a long survey nobody finishes.
- Can I launch on Product Hunt with a waitlist?
- You can post it, but Product Hunt does not feature waitlisted products unless immediate access is provided. Invite your list first and launch on Product Hunt once anyone can sign up and use the product.
- Does this generator store my signups?
- No. It only creates text in your browser: a form and four emails. You paste them into the form or email tool you already use, which then stores the signups.