TLDR
If your Product Hunt launch is over and the daily signup count fell off a cliff, the right next-week move depends almost entirely on how many upvotes you finished with. Below 100, the problem is usually targeting. Between 100 and 500, the problem is usually distribution. Above 500 with weak signups, the problem is usually conversion. This post is a decision tree for each band, drawn from repeated patterns on r/SideProject and IndieHackers.
Why the problem happens
Product Hunt’s launch model gives every product roughly a 24-hour homepage feature window S-007. The ranking algorithm decays older submissions inside that window S-008. After the window closes, organic discovery on PH falls dramatically — and the founder rarely has a plan for the next day, let alone the next week.
Postmortems on r/SideProject and IndieHackers describe the same arc: the founder spends a month preparing, fires on launch day, answers comments for ~14 hours, and then the calendar opens to a blank week S-001 S-002. The work that turns a launch into a recurring channel — Show HN at the right time, niche-community posts, the IH retrospective, the comparison blog post — is the work that’s hardest to start when you’re tired.
Decision tree by upvote count
The right next-week action depends on the band you finished in. Walk through this top-down.
Band 1 — fewer than 100 upvotes
If you launched and finished under 100, the most common diagnosis is targeting, not the launch itself. The community around r/SideProject and IndieHackers documents this pattern repeatedly: the product was demoed to the wrong audience, or the audience was technically right but the launch page didn’t speak to them S-001.
Next-week actions, in order:
- Write the audience down in one sentence. Who exactly is this for? “Solo founders shipping side projects” is not specific enough. “Solo founders who launched on PH and got under 100 upvotes” is.
- Find three niche communities where that exact audience hangs out. r/SaaS and r/SideProject don’t count — they’re cross-cuts of every product. Look for vertical subreddits, Discord communities, and Slack groups where the audience already discusses the problem your product solves.
- Post the postmortem there. Not “I launched on PH — please upvote.” A real postmortem: what you launched, how many upvotes, what the takeaways were, what you’re doing differently in week 2. Postmortem posts get traction in r/SideProject and IndieHackers S-002; mid-launch ads do not.
- Skip Show HN this week. Show HN with a sub-100 PH result usually doesn’t help — the HN audience is colder than PH, and you don’t have a social-proof signal to lead with.
Band 2 — 100 to 500 upvotes
A 100-to-500 finish means the launch was visible and the audience was roughly right. The diagnosis is usually distribution: you didn’t carry the launch into the next 28 days.
Next-week actions:
- Post Show HN within 24 hours of the PH launch closing. HN’s ranking algorithm rewards timely submissions in the early-US-morning window S-003 S-004. See the Show HN 9 AM ET timing post for the rationale.
- DM the top 10 upvoters individually with a personal note that references their bio or last post. Generic “thanks for the support!” DMs get 0 replies; specific ones get ~30%.
- Write the IndieHackers retrospective. Numbers-led: actual upvote count, actual signups, the source breakdown if you have UTMs, what you’d do differently. IH retrospectives consistently outperform generic SaaS posts in the community S-002.
- Schedule one blog post per week for the next four weeks. Each one targets one long-tail query in your niche. Internal-link them to the launch page.
Band 3 — 500+ upvotes with weak signups
This is the most painful band: high visibility, low conversion. The diagnosis is usually a conversion problem, not a distribution problem.
Next-week actions:
- Audit the launch page above the fold. Do new visitors understand what the product does in 5 seconds? If your headline is “X for Y, with AI” you have a generic-headline problem. Rewrite as a hero: “For [specific role] who hit [specific trigger], do [object] before [consequence].”
- Check your referral source mix. Open Vercel Analytics, Plausible, or PostHog and break signups by referrer S-006 S-014. The PH referrer is usually not the highest-converting channel; the highest converter is often a sub-200-visit niche community.
- Email the warmest 50 signups manually with one question: “What were you trying to do when you signed up?” This is the cheapest qualitative data you’ll ever collect.
- Plan the comparison post. “X vs Y for [specific user]” usually ranks well within 30 days for a product with PH visibility — search intent is already there.
Concrete example
A solo founder finishes a Product Hunt launch with 380 upvotes and 12 paying signups. Daily traffic falls from 9,000 on launch day to 200 by day 3.
- Band: 2 (100–500 upvotes).
- Diagnosis: distribution.
- Day 2 action: Show HN at 9:15 AM ET with the title “Show HN: I built X so I could stop doing Y”. Picks up 60 points and 38 referral visits.
- Day 3 action: IH retrospective titled “Launched X on PH — 380 upvotes, 12 paying signups, here’s the source breakdown”. 14 comments, 3 paid signups from IH.
- Day 4 action: DM 10 PH upvoters individually. 2 replies, 1 signup.
- Day 7 action: Publishes a blog post on the founder’s domain targeting “[X tool] alternative for [specific user]”. Picks up Google traffic over the next 60 days.
This is illustrative, not a measured case study — but the pattern is what the postmortems on r/SideProject, r/Entrepreneur, and IndieHackers repeatedly describe S-001 S-002 S-012.
Common mistakes after a flopped PH launch
| Mistake | Why it happens | What to do instead |
|---|---|---|
| Re-pitching to your full email list | Founder feels the launch was a one-shot | Email only your top 20 warmest contacts, personally |
| Posting in r/SaaS with “I launched today” | Easiest action, lowest signal | Post a postmortem in 3 niche communities, not r/SaaS S-013 |
| Buying ads to “boost the launch” | Feels like control | Spend that money on a designer or copywriter to fix the above-fold conversion |
| Asking for upvotes after the window | Last-ditch attempt at the leaderboard | The launch is over — focus on next-week distribution |
| Writing “lessons learned” Medium posts | Quick to publish, feels productive | Publish on your domain. Medium posts earn no SEO backlinks for you S-002 |
FAQ
Should I relaunch on Product Hunt later? Maybe — PH allows relaunches but the audience is the same. A relaunch only helps if the product changed enough to warrant the new pitch. Most founders should focus on the 28-day recovery first, not a relaunch.
Is Show HN worth it if I got fewer than 100 PH upvotes? Usually no. The HN audience is colder than PH and you have no social-proof signal to lead with. Spend the time on niche-community posts instead.
My launch had 800 upvotes and I’m getting decent signups. Is this still relevant? Yes — the recovery scorecard still applies. The 30-day plan compounds even when the launch went well. Skip Band 1, work Bands 2 and 3.
Can I delete the PH page if the launch flopped? You can hide it, but it’s almost never the right move. The backlink and the social-proof signal (however small) are worth more than the embarrassment of a low upvote count.
Next steps
The Post-launch 7-day recovery scorecard on the homepage is the concrete starting point — the 12 rows are the same actions named above, with leverage scoring. Then read the Show HN 9 AM ET timing rule for the Day 2 action, and the 30-day distribution plan walkthrough for Weeks 2–4.