Launches that land: Product Hunt and beyond
A real launch checklist. Why most launches flop, what changed in 2026, and the alternatives worth picking instead.
Most Product Hunt launches flop because the launcher believed the day-of upvote churn was the strategy. Refresh the leaderboard, ping the group chat, beg cousins for accounts. Then it ends, the product sits at #14, and they wonder what happened. The actual launch playbook is 80% what you do before launch day. The day itself is just the visible 20%.
Here's what the pre-launch six weeks actually look like.
Six weeks out: build the list
The single biggest predictor of a decent launch is whether you have a list of people who already said they want this. Email signups from a coming-soon page. Twitter followers who replied to your build-in-public posts. Anyone who said "tell me when it's live" in a DM. Save those names somewhere countable.
200 to 500 names is enough. You don't need a newsletter empire. You need a small group of people who will actually open one email when it lands.
If you don't have a list yet, that's your job for the next two weeks. Post about the problem you're solving, not the product. Ship a coming-soon page with one email field. Reply to every adjacent thread on Twitter and Reddit where the problem comes up.
Three weeks out: pick the date
Don't launch on a Monday. People are buried in inbox triage. Don't launch on a Friday. Engagement craters by 2pm. Don't launch the day Apple is announcing anything, or the day a major model drops, or any US holiday.
Tuesday, Wednesday, or Thursday is the safe window. Pick one and put it on the calendar. Tell yourself it's not moving.
One week out: prep the assets
Three things, and only three:
- A 60-second demo video that shows the actual product working. Not a branded animation, not a logo morph, not a guy with a headset talking over slides. The cursor moves, the form submits, the result appears. People click play to see if it works, not to see your motion graphics budget.
- A tagline that says what it does in 8 words or less. If you can't, you don't understand the product yet. Cut adjectives first.
- Three screenshots that aren't all hero shots. One of the empty state, one of the product mid-use with real data, one of the result. Carousels with stylized gradient backgrounds get scrolled past.
The day before: warn the list
Send one email. "We go live tomorrow at 8am PT, here's the link, one click to support if you want to." That's it. No long story, no founder journey. The story comes later. Right now you need a button.
Launch day tactics
Post early in San Francisco morning, around 12:01am Pacific. The queue resets at midnight PT, which means an early post gets the most accumulated hours on the front page.
Reply to every comment in the first four hours. Be specific. If someone asks about pricing, answer in a sentence and link to the page. If someone shares a use case you didn't think of, say so out loud. The PH algorithm reads engagement, not just votes.
Do not beg for upvotes. PH penalizes "please upvote" posts and your hunters know. Thank people specifically when they comment. Share the launch link with your list and your network, but say "if you find it useful" not "I need votes."
The honest reality of Product Hunt in 2026
It's a smaller deal than it was three years ago. The community fragmented. AI-product saturation flattened the front page. A good launch gets you maybe 2,000 to 5,000 site visits and 50 to 200 trials. Top of the day gets you a feature in the daily email blast and a badge for your footer. That's nice. It's not life-changing.
Plan for nice. Anyone telling you otherwise is selling you a launch service.
Alternatives worth considering
Hacker News (Show HN). If your product is technical and the audience is engineers, this can outperform PH for actual conversions. A single thoughtful comment from someone respected in the space can drive more sign-ups than 200 PH votes. The bar is higher: weak demos get buried in an hour. Solid ones can drive traffic for two days.
Reddit niche subs. r/SaaS and r/SideProject are the obvious ones. The non-obvious one is your specific industry sub, where the audience actually has the problem. Smaller reach, much higher relevance, much higher trial-to-paid rate.
Indie Hackers. Friendly audience, decent conversion for B2B and bootstrapped tools. Won't 10x your traffic but will get you the first real conversations with peers who'll later send referrals.
Beehiiv newsletter sponsorship. Paid, but the math often works. A relevant newsletter blast to 30,000 in-niche readers can outperform a top-3 PH launch for some products. Pick newsletters where the audience already buys things.
Twitter or X with a hook tweet. Depends entirely on your network. If you've been building in public for six months, the launch thread is the highest-leverage channel you have. If your account has 200 followers, this is not the move.
Post-launch: the part nobody screenshots
The launch is one data point. It's not a finish line.
Most paying customers come from week 2 to week 12 after launch. Through SEO once Google indexes your page. Through word of mouth from someone who tried it. Through second-touch from people who saw the launch but weren't ready to buy that day. They circle back when the problem actually bites.
Keep posting. Keep talking to users. Keep shipping. The launch was the door. The work is everything that happens after you walk through it.
Up next
You've got a launch plan. You're going to need a price tag on the product when people land. The next guide in this category, "Picking your first price," covers how to set one without doing six months of pricing research you don't have time for.