25 September 2026 · 4 min read
Waitlist to first sale: a one-week launch checklist
A waitlist gives you people to sell to. It doesn't turn them into buyers on its own. Here is the week between a nearly finished product and the first sales.
Short answer
Write the listing in your waitlist's own words, set one price, buy your own product in test mode, make sure every sale lands somewhere you'll see it, email the list on launch day, and ask buyers what they think a week later. If time runs short, protect the test purchase and the follow-up. The first catches a broken download before a buyer does, and the second catches an unhappy buyer before they ask for a refund.
Day 1: Write the listing from your waitlist's words
If your signup form asked what people hoped the product would solve, those answers are your headline and bullets. Use the phrases that come up more than once. By the end of the day the listing should have:
- Headline in the buyer's words
- Three to five concrete bullets (what they get, not how you built it)
- What's in the download or account
- Refund policy in one sentence
Day 2: Price it and prepare the assets
Pick one price. If you're unsure between two, pick the higher one and say what the buyer gets for it. Make screenshots of the real product rather than mockups, and a short screen recording if setup is more than a few steps.
Day 3: Tell the waitlist it's coming
Email the list with the launch date and one specific thing the product does. Ask one question they can reply to. Read the replies closely, because they tell you which words to keep in the listing. A list that has been replying is also in better shape for the launch send than one that hasn't heard from you in weeks.
Day 4: Wire the sale to somewhere you'll see it
Every sale should create a record with the buyer's name, email, product and date, and send a welcome email that says exactly how to start. Lemon Squeezy and Gumroad send receipts, but a receipt isn't onboarding. The free Sale to Notion CRM workflow logs each order to a Notion database and sends the welcome email.
Day 5: Buy your own product
Run a real purchase in test mode, from a different email address, on your phone. Check that the payment works, the receipt arrives, the download link works, the welcome email arrives and isn't in spam, and the sale shows up in your records. Anything on that list that breaks turns into a support email on launch day, so it's cheaper to find it yourself.
Day 6: Prepare for support
Write replies for the three questions nearly every digital product gets: "where's my download", "how do I set this up" and "can I get a refund". Decide your refund answer now, not when someone is annoyed. See running support without a helpdesk for a simple setup.
Day 7: Launch
Email the waitlist before you post anywhere public. They signed up to hear first. Keep the email short: what it is, the price, the link, and when any launch price ends. Then post where your buyers actually are. Watch your inbox and sales records for the first few hours and fix anything broken immediately.
The week after: follow up with buyers
- Day 3 after purchase: send one useful tip for getting more out of the product
- Day 7 after purchase: ask for a one-sentence testimonial and a 1 to 5 rating, and invite complaints too
- Retrospective: list every support question you got and fix the page or doc that caused it
The Testimonial Request Emails workflow sends the day-3 and day-7 emails automatically after each sale.
Questions
How long should I run a waitlist before launching?
There is no fixed length. Keep it open until you have people to email and enough signup answers to write the listing in their words. If you can't yet describe the product using phrases from those answers, keep collecting.
Should I offer a launch discount?
A short, real one (a price that genuinely goes up on a stated date) can help. Avoid fake scarcity and inflated 'was' prices; they cost trust with exactly the early buyers you want to keep.