How to use a launch checklist without letting it run you
Most launch checklists fail in the same way: they are a list of everything anyone has ever done before a launch, which makes them impossible to finish and therefore easy to abandon. This one is ordered by when the work actually happens, so you can see what is due now and ignore the rest until it matters.
The single most useful property of a checklist is that it moves decisions out of launch week. Nearly everything that goes wrong on launch day was decided — or not decided — three weeks earlier.
The six phases
1. Foundation
The unglamorous infrastructure: a domain, a landing page, analytics that genuinely record visits, and error tracking. Founders skip error tracking constantly and then spend launch day learning about failures from strangers on the internet. Set it up while it is boring.
Decide pricing here too, even if version one is free. "Free for now" is a pricing decision; making it deliberately is very different from drifting into it.
2. Product readiness
The phase that decides whether the launch is worth doing. Two items matter more than the rest: cutting scope, and watching five strangers use the product without helping them. Watching in silence is genuinely uncomfortable and it is the highest-value hour in this entire list. Every place they hesitate is a place your launch-day traffic will hesitate, except that traffic will simply leave.
Empty states deserve their own mention. A new account with no data is the first thing every single visitor sees, and an unhandled empty state looks exactly like a broken product.
3. Launch assets
Your tagline, logo, screenshots, and demo video are the entire product for anyone scrolling a directory. A few rules that consistently hold:
- The tagline says what it does. Not what it feels like, not a pun. Someone skimming forty products gives you about two seconds.
- Screenshots show the product with data in it. An empty dashboard tells nobody anything.
- The demo video starts immediately. No logo animation, no "hi, I'm…". Show the thing working in the first three seconds.
4. Audience
The phase people wish they could skip, and the one that most determines the outcome. You cannot manufacture an audience on launch day; you can only call in one you already built. Two weeks of being genuinely useful in the places your users already gather is worth more than any amount of launch-day posting.
Line up ten people who have agreed to look on the day. Not fifty who might. Ten confirmed beats fifty hopeful, and the first hour of momentum is what decides whether anyone else sees you at all.
5. Launch day
Submit early, comment immediately, email your list within the hour, and then spend the day replying to people. Replying to the critical comments matters more than replying to the kind ones — everyone reads how a founder handles criticism.
Do not buy votes. Every directory worth launching on can see it, the penalty is removal, and the reputational cost outlasts the launch by years.
6. After the launch
The week after is where the value actually gets collected. Thank people individually. Put your badge up. Write every piece of feedback in one place, then ship one visible fix within 48 hours — nothing converts launch-day curiosity into actual users like watching a founder respond to what people said.
Then work out which channel sent you real users, as opposed to the one that sent the most traffic. They are frequently not the same channel, and knowing the difference is worth more than the launch itself.
What a launch is actually for
A launch is not a growth strategy. It is a concentrated burst of attention that buys you three things: your first real users, honest feedback from people with no reason to be kind, and a permanent, linkable page that keeps sending you traffic long after the day itself.
Judge it on those three, not on where you placed. Plenty of products that finished outside the top five had a far better week than the one that won.