I’ve launched over a dozen products. The best launches had the shortest checklists. The worst launches were the ones where I tried to get everything perfect before going live. The pattern is clear: less preparation, better outcomes. Not because preparation is bad, but because most pre-launch preparation is about managing your anxiety rather than improving the customer experience.
Here’s the launch checklist I actually use. Twelve items. Some of them will shock you with how basic they are. That’s the point — a launch is not a production. It’s the moment you start learning from real customers.
The 12 Items
1. The sales page is live and the buy button works.
Test this yourself. Test it on mobile. Test it in a different browser. Have one other person test it. That’s enough testing. The number of launches I’ve seen delayed because “the checkout flow needs work” when the actual Stripe checkout was fine is embarrassing.
If someone can find your page, read what you’re offering, click buy, and complete a payment — you’re ready. Ugly is fine. Functional is non-negotiable.
2. The product delivers its core outcome.
Whatever you promised on the sales page, the product must deliver that specific thing. Not everything you plan to build. Not the full vision. The core outcome that someone is paying for.
Test the core outcome with one person before launch. If they can go from purchase to core outcome in a reasonable timeframe without needing your help, you’re ready.
3. You can receive payments and you know where the money goes.
Stripe is connected to your bank account. You understand the fee structure. You know how long it takes for funds to arrive. You’ve accounted for sales tax or VAT requirements (in the EU, this matters from day one for digital products).
This sounds basic but I’ve seen founders launch and then realize they don’t have a Stripe account, or their Stripe isn’t connected to a bank account, or they forgot to enable their preferred payment methods. Test the money flow before launch day.
4. Customers can reach you when something goes wrong.
An email address. A contact form. A chat widget. Something. When a customer has a problem — and they will, because it’s V1 — they need a way to tell you. If they can’t reach you, they’ll ask for a refund (if you’re lucky) or leave a bad review (if you’re not).
Response time matters more than response channel. Responding to every customer email within 4 hours during launch week is more important than having a sophisticated support system.
5. You have a launch message ready for your audience.
If you have an email list, the email is drafted. If you’re launching in a community, the post is written. If you’re doing direct outreach, the message templates are ready.
The message should be: what you built, who it’s for, what problem it solves, the price, and a link. That’s it. No origin story. No feature list. Problem, solution, price, link.
6. You know what success looks like for launch week.
A specific number. “10 sales in the first week” or “25 signups” or “5 customer conversations.” Write it down before launch so you don’t move the goalposts after. This connects to the success metric in your product spec.
7. You’ve told 10 people personally.
Not a mass email. Ten personal messages to people who are either in your target market or know someone who is. “Hey, I’m launching [thing] today. Here’s the link. Would love your support — and if you know anyone who’d benefit, I’d appreciate you sharing it.”
Personal messages convert 5-10x better than broadcast messages at launch. Your first customers will come from personal connections.
8. Analytics are installed.
You need to know how many people visit your page and how many buy. Google Analytics (free) or Plausible (simple and privacy-focused) is enough. Don’t overthink this. You need two numbers: visitors and conversions.
9. You have a plan for the first customer complaint.
Not a support playbook. Just a mental model for what you’ll do when the first person says “this doesn’t work” or “I expected something different.” Your plan should include: respond within 4 hours, apologize, fix or explain, offer a refund if appropriate.
The first complaint is also the first data point about what needs to improve. Treat it as valuable feedback, not a crisis.
10. You’ve decided what you’re NOT going to do in launch week.
Launch week is not the time to add features, redesign the page, or chase new marketing channels. You’re going to want to — anxiety will make everything feel urgent. Decide in advance: launch week is for customer communication, bug fixes, and learning. Nothing else.
11. You have a follow-up plan for buyers.
Within 24 hours of purchase, every buyer gets: a personal thank-you email, a request for initial feedback, and clear instructions for getting support if needed. This takes 5 minutes per customer and sets the tone for the entire relationship.
12. You’re emotionally prepared to be disappointed.
The first week almost never meets expectations. Traffic will be lower than hoped. Conversion will be slower than expected. Some people will visit and not buy. Some will buy and not use it. This is normal. The launch is the beginning of the learning process, not the climax of it.
I’ve launched products to complete silence. I’ve launched products where the first customer took three days to appear. Every time, the slow start was followed by gradual growth — because the product was good and the market was real. The launch day itself is the least important day in the product’s life.
What’s Conspicuously Missing
Notice what’s NOT on this checklist:
- Logo or brand identity
- Social media accounts
- Blog content beyond the launch post
- Press outreach
- Product Hunt listing
- Video demo or walkthrough
- Detailed documentation
- Mobile-optimized experience
- Multiple pricing tiers
- Referral program
- Affiliate program
- Partnership agreements
All of these are fine things to have. None of them are necessary for launch day. Every item you add to the launch checklist is another reason to delay. And every day of delay is a day without customer data, revenue, and learning.
The preparation trap is most dangerous in the days before launch, when anxiety peaks and the temptation to “just add one more thing” is strongest. The 12-item checklist is your defense: if all 12 items are done, you launch. Everything else can be added post-launch.
Launch Day Mechanics
Here’s what launch day actually looks like, hour by hour.
7:00 AM: Final check of the sales page and payment flow. Confirm everything works.
8:00 AM: Send the launch email to your list. Post in your primary community. Send the 10 personal messages.
9:00 AM - 12:00 PM: Monitor for issues. Respond to every question and comment in real time. Fix anything that’s broken immediately.
12:00 PM - 3:00 PM: Second round of outreach. Share in additional communities. Post on social media. Thank early buyers publicly.
3:00 PM - 6:00 PM: Process feedback from the first buyers. Note everything — what they liked, what confused them, what they expected but didn’t get. This is your most valuable data of the entire launch.
Evening: Review the day’s numbers against your success metric. Write down three things that went well and three things to improve. Don’t make any changes to the product today — just record what you learned.
The entire launch day is about communication and learning, not building. If you catch yourself wanting to add a feature or fix something cosmetic during launch day, write it down and do it tomorrow. Today is about being present with your customers.
After Launch: The First Week Protocol
Day 2: Follow up with every buyer. Personal emails. Ask for feedback. Fix any bugs reported on day 1.
Day 3: Analyze which launch channels produced the most conversions. Double down on the best one.
Days 4-5: Based on feedback, identify the single most impactful improvement. Build it if it’s small enough.
Days 6-7: Send a second outreach wave to people who didn’t respond to the first. Ask early buyers for referrals. Update the sales page based on what you’ve learned about what clicks with customers.
By the end of the first week, you should have: your first customers, your first feedback, your first data on what converts, and a clear picture of what V1.1 should improve. That’s the beginning of the weekly ship cycle that drives long-term growth.
Key Takeaways
- 12 items is enough for a launch checklist. Sales page works, product delivers the core outcome, payments flow, customers can reach you, and you’ve told people it exists. Everything else is post-launch.
- Launch week is for communication and learning, not building. Resist the urge to add features or redesign. Be present with your customers.
- The launch day itself is the least important day in the product’s life. The learning that starts on day 2 matters far more than day 1 traffic or sales.
- Tell 10 people personally. Personal messages convert 5-10x better than broadcast messages at launch.
- Be emotionally prepared for a slow start. The first week rarely meets expectations. Growth comes from consistent iteration in the weeks that follow.
