Build the Pre-Launch List First
A launch with no audience is just a press release into the void. The work that makes launch day land happens in the weeks before it, when you build a list of people who already know what you are making and want to be told when it ships. This is the difference between launching to a room and launching to an empty hallway.
Start collecting interested people the moment you have something to point at, even a one-page description. A simple waitlist, a build-in-public thread, a small community where your buyers already gather. You are not trying to build a huge list. You are trying to build a list of the right people who will show up on the day and give you the early momentum that algorithms and humans both reward.
Treat the list as a relationship, not a database. Email it occasionally with progress, ask questions, share a rough demo. People who feel involved before launch are the ones who upvote, comment, share, and buy on the day. A cold list that hears from you once, at launch, performs like no list at all.
- Stand up a waitlist or signup page as soon as you can describe the product in one sentence.
- Email the list two or three times before launch with real progress, not hype.
- Find the two or three places your buyers already gather and become a useful regular there.
- Ask early people what would make this a must-have. Their words become your launch copy.
Pick a Launch Date and Work Backward
Set a real date and tell people. A public commitment turns a vague someday into a deadline, and a deadline is what forces you to cut scope to what actually matters for launch. Without a date, the product is never quite ready, because there is always one more thing.
Working backward from the date, build a short checklist of what genuinely has to be true on the morning of launch. The product does the one core thing without breaking. Pricing and payment work end to end. The landing page answers who it is for and why it matters in the first screen. You have your launch assets written in advance: the Product Hunt copy, the email, the social posts, the replies to obvious questions.
Resist the urge to add features in the final week. The week before launch is for testing the path a real user takes, fixing what breaks, and writing copy, not for new code. A launch that goes out with one solid feature beats one delayed for a month chasing a second.
- Announce a date publicly so the deadline is real.
- Write all launch copy a week early so the day itself is execution, not drafting.
- Walk through signup, payment, and the core action yourself, on a clean account, the day before.
- Freeze the feature set. The final week is for fixing and testing, not building.
Launch Day: Concentrate Attention, Do Not Spray It
Launch day works because you point everyone at the same moment. Pick the channels where your buyers actually are and hit them in a coordinated burst rather than trickling out posts over a week. For a developer or maker tool, Product Hunt and Hacker News can drive a real spike. For a niche audience, the right subreddit, Slack group, or Discord often beats both. Email your pre-launch list early in the day so your warmest people create the first wave of activity.
On Product Hunt specifically, the early hours decide the day. Launch at the start of the day in your platform's time zone, have your first comment ready explaining why you built it, and ask your list to come engage rather than just upvote. Genuine comments and conversation matter more than a pile of silent votes. Be present all day to reply to every question and piece of feedback fast.
Match the message to each place. Communities punish a copy-paste promo and reward a story, a problem you hit, a thing you learned. Lead with the problem you solve, show the product doing it, and make it dead simple to try. Your job on the day is to be everywhere your launch is being discussed, answering and thanking people, not to post once and walk away.
- Choose two or three channels where your buyers actually are, not every channel that exists.
- Email your warmest list first to seed early momentum.
- On Product Hunt, launch early, post a strong first comment, and reply to everything.
- Rewrite the pitch for each community. Lead with the problem, not the feature list.
Post-Launch Is Where the Real Work Is
A launch spike is rented attention. Most of the people who showed up will never come back unless you give them a reason and a path. The week after launch is where you turn a one-day number into actual customers, and it is the part almost everyone neglects because the dopamine of launch day is over.
Reply to every signup, every comment, and every piece of feedback while the iron is hot. Watch what new users actually do. Where do they get stuck? Where do they drop off before reaching the point where the product is useful? The post-launch window is your richest source of real usage data you have ever had, and it is fleeting. Talk to the people who tried it and the people who bounced.
Then keep launching. A single launch is one event, but the same product can be launched again to different audiences, on different platforms, with a new angle, a new feature, a case study, a milestone. The founders who treat launch as a repeatable motion rather than a one-time event are the ones who compound attention instead of spending it all in a day.
- Personally reply to early signups and feedback in the first 48 hours.
- Instrument the funnel so you can see where new users drop off and fix it.
- Convert launch-day interest into a real conversation. Ask why they signed up and whether it delivered.
- Plan the next launch. New feature, new audience, new platform. Launching is a motion, not a moment.
Measure What Actually Matters
Upvotes and visitor counts feel good and tell you almost nothing about whether you built something people want. The honest scoreboard for a launch is further down the funnel: signups from the traffic, activation (how many reached the point where the product delivered value), and retention a week or two later. A launch that drove a thousand visitors and three retained users is a signal, and the signal is that the problem or the product is not landing.
Decide your launch metrics before the day so you are not rationalizing afterward. A reasonable set is visitors, signup rate, activation rate, and week-one retention. Compare them against what you expected. If traffic was strong but signups were weak, your landing page or positioning is the problem. If signups were strong but retention collapsed, the product is not yet solving the problem well enough to keep.
This is where launching connects back to validation. A launch is a high-resolution test of demand. If the numbers are weak across the board, the responsible move is not to launch harder. It is to go back, talk to the people who did not convert, and decide honestly whether to fix the product, change the audience, or kill the idea before sinking more time into it.