Objective
Grow and activate a product launch waitlist
Create a qualified waitlist with early access, referrals, and a clear launch promise.

Enter the giveaway
Start with the complete working structure, then adjust the language, timing, and incentive to fit your customers and brand.
Best used when
Your team has a specific decision or growth objective and needs a focused artifact to move from planning to launch.
Grow and activate a product launch waitlist
People who want one specific thing that does not exist yet, which is a narrower and far more useful group than a general giveaway reaches. Do not run it at a broad audience: the entry count is supposed to be a demand signal, and a list padded with prize hunters makes that signal worthless.
2 to 6 weeks, opening before the product exists and closing at launch
The share of the waitlist that orders in the first seventy-two hours after launch. Waitlist size is the input, not the result, and conversion is the only number that tells you whether you built demand or curiosity.
Primary action
Enter with email
Bonus actions
Promotion copy
“[Product] is coming, and the waitlist gets it first: join with your email and one person on the list wins theirs free at launch. Refer a friend for extra entries, and we close the list the day it goes on sale.”
Generate a focused variation while keeping the expert-written version available as your baseline.
Add your goal and audience. If AI is unavailable, the complete template on this page still works as a practical starting point.
Your inputs are sent only to generate this result and are not stored by UserLoop.
Three specifics worth checking against your own store before you launch.
Start with the focused version, publish, and let the first answers steer the next iteration.
Say what the product is and what you do not know yet, because a waitlist survives a delayed launch and does not survive a broken promise about a date
Set email as the entry with referral as the only bonus, and keep the form to a name and an address
Email the list at least twice while they wait: the factory photo, the color decision, the packaging. Silence kills a waitlist, time does not
Strong execution usually comes from removing ambiguity and keeping every action tied to the original objective.
Promising a launch date you do not control, when production slips and you can promise the order of events instead
Treating the signup count as the result, when a waitlist that does not convert on day one was a giveaway with extra steps
Going quiet between signup and launch, so a list built in March has to be reintroduced to the product in June
Leaving the waitlist open after launch, which quietly tells the people who joined early that first access meant nothing
There is no threshold worth quoting, because the number that matters is conversion rather than size. Read it against your normal launch: if a list of people who specifically asked for this product converts worse than a routine email to your whole file, the demand you thought you found is not there.
Tell the list in one email, with the reason and a new expectation. A waitlist tolerates delay far better than it tolerates silence, and the people who leave over an honest delay were unlikely to buy anyway. Keep the referral entries valid so nobody feels their sharing was wasted.
Yes, and it should ship at launch rather than before it. Sending a pre-release unit early produces a review of something nobody can buy and puts your only working sample in somebody else's hands during the week you most need it.
That is one of the better reasons to run it. In the emails you send while people wait, ask which version they want and count the replies before the buying decision is locked. Surveys handles the version of that question you ask after they buy, tied to the actual order.
Collect useful customer insight with Surveys and grow your audience with Contests.