Product Hunt Launch: The 2026 Playbook for Winning #1
How to run Product Hunt as a campaign — not a one-day event. The 30-day before, during, and after playbook from 30x daily #1 experience.
Key Stats
| Metric | Data |
|---|---|
| Product Hunt #1 Daily wins | 30× |
| Product Hunt Weekly Top 3 | 10× |
| Product Hunt Monthly #1 | 1× |
| PH vote-clearing frequency | Every ~2 hours |
| Safe upvote velocity cap | ≤100/hour |
| Launch day traffic drop (72 hrs) | 80–90% |
| Weekly badge exposure vs. Daily | 7× |
TL;DR
- Treat PH as a 30-day campaign: 2 weeks prep, 1 day launch, 2 weeks follow-through
- The badge — not the traffic — is your real asset. Deploy it everywhere after launch
- Upvote quality beats quantity every time: aged accounts, geographic diversity, ≤100/hour
- Multi-launch is the strategy: 30 launches over 18 months beats 1 “perfect” launch
- Your follow-through in the 72 hours after launch determines whether the spike becomes growth
The Mistake Everyone Makes
Most founders treat Product Hunt as a one-day event. They spend weeks on their listing, rally supporters, hit #1 — and then watch 90% of that traffic disappear within 72 hours, leaving almost nothing behind.
After 30 daily #1 wins, the pattern is clear: founders who win once rarely win again because they’re thinking about launches wrong.
Product Hunt is a campaign platform. The teams that compound value from it don’t launch once — they launch repeatedly, treat each badge as infrastructure, and build a follow-through system that turns a 24-hour spike into 30 days of downstream conversion.
This is that system.
Phase 1: The Two Weeks Before
Week 1: Foundation
Set up your coming soon page immediately. Every person who clicks “Notify Me” gets a push notification on launch day. These are your warmest possible supporters — developers actively looking for new tools who opted in specifically for your product. Start building this list weeks before you’re ready.
Choose your launch window strategically. Not all days are equal:
- For daily #1 only: Friday–Sunday has lower competition but also lower traffic. Net neutral, but easier to win.
- For weekly + daily badge: Tuesday in the 2nd or 3rd week of the month. This gives you the full Mon–Sun weekly window and avoids the concentrated competition of week 1 when experienced teams often launch.
- Watch hunted.space for 2 weeks before your launch. See what the daily top vote counts look like. Calibrate your target.
Select your hunter. The hunter’s primary value is getting you featured quickly — a gold-badge hunter means you appear on the Featured list immediately rather than waiting for manual review. Their follower notifications are secondary.
Look for:
- Gold badge (verified, active hunter)
- Genuine interest in your product category (they’ll write a better intro comment)
- Response rate: send a short, personable email, not a template
Week 2: Asset Preparation
The quality of your PH listing is set in this week. There are no edits on launch day.
Thumbnail (240×240px): Visible on mobile feeds where most votes happen. Test it at small size. Logo alone rarely works — add a one-line descriptor.
Gallery (1270×760px, first image is critical): The first image is what users see before clicking in. It should be a screenshot that immediately shows what the product does, not a branding slide.
Video (60–90 seconds): Show the product working, not a marketing montage. Developers want to see what they’re getting.
Tagline (≤60 chars): Benefit, not feature. “The open-source Notion with local-first storage” not “A powerful note-taking application.”
First maker comment: Write this in the week before. It’s your most important piece of content on launch day. Structure: problem you faced personally → why existing solutions failed → what you built → one honest limitation + what you’re working on → question for the community. The question invites replies, which boost engagement signals.
Phase 2: Launch Day (The 24-Hour Window)
12:01 AM PT — The First Hour
This hour sets your trajectory. Product Hunt’s algorithm weighs early engagement heavily for initial placement.
- Post your maker comment immediately — don’t wait for traffic, post it the moment the listing goes live
- Notify your coming soon subscribers — they opted in; this is expected and welcome
- Send your briefed supporters a single, clear message: “We just launched — here’s the link, any feedback welcome” (never say “please upvote”)
- Begin responding to every comment — even a simple acknowledgment keeps the conversation active
Managing Upvote Velocity
PH clears votes every ~2 hours. What gets cleared:
- Votes from accounts registered less than 2 months ago
- Multiple votes from the same IP range in a short window
- Velocity spikes that don’t match natural traffic patterns
The rule: Keep incoming votes under 100/hour, ensure geographic diversity within each hour. If your first 80 votes all come from the same city in 20 minutes, expect a clearing event.
Spread your outreach by timezone:
- 12:01–4 AM PT: Core team + briefed early supporters
- 4–10 AM PT: European contacts
- 10 AM–4 PM PT: US peak hours (highest PH traffic)
- 4–10 PM PT: Final push, secondary channels
Channel Sequencing
Not all channels work equally well on launch day. From 30 launches of testing:
LinkedIn DM → highest conversion rate. A personal message to a connection who’s a founder or maker gets ~60% reply rate. Filter to people whose LinkedIn shows they’re builders — they have PH accounts and will actually engage with your product.
WeChat startup groups → high conversion for China-based teams. One-on-one DMs within groups convert far better than group announcements. Work through contacts individually.
Reddit → 1% PH upvote conversion, but wide awareness. Post in r/SaaS, r/SideProject, r/indiehackers on launch day. Don’t ask for upvotes — just announce the launch and invite feedback. The Reddit post has value beyond PH votes.
Twitter/X → variable. Your own tweet with real-time metrics (“We just hit 100 upvotes in 3 hours — here’s what we’re building”) outperforms generic launch announcements.
Engagement Is a Ranking Signal
PH’s algorithm doesn’t just count votes — it weighs engagement. Every comment response, every new comment, every reply thread keeps your listing active and signals authentic interest.
Respond to every comment within 30 minutes during peak hours. Even a simple “Thanks — great question, here’s how we approached that:” does two things: it keeps the thread active, and it often prompts the commenter to share the listing.
Phase 3: The 72 Hours After (Most Teams Skip This)
The Badge Deployment Checklist
Within 24 hours of your #1 finish, add the badge to:
- Landing page hero section (not footer — hero)
- GitHub README (converts developer visitors)
- Email footer
- LinkedIn company page
- Pitch deck “traction” slide
- App onboarding flow (“Loved by Product Hunt community”)
The badge has a half-life — it’s most powerful in the first month. Use it aggressively.
The Newsletter Pitch Window
The 72 hours after a #1 finish is your best window for press and newsletter outreach. Your PH ranking is live social proof. A pitch email that says “We just hit #1 on Product Hunt — here’s what we’re building” has a fundamentally different open rate than a cold pitch with no credentials.
Target:
- Developer-focused newsletters in your niche (JavaScript Weekly, TLDR Tech, Changelog, etc.)
- Indie hackers and startup newsletters
- Vertical newsletters in your product category
Keep the pitch under 5 sentences. Link directly to your PH listing, not your homepage.
Reddit Follow-Through
Post a “We just launched” thread in 2–3 relevant subreddits within 48 hours of launch. The PH badge makes this feel credible rather than promotional. Format: what you built, what the response was like on launch day (real numbers if good), what you’re working on next, invitation for feedback.
This is where Reddit converts at a meaningful rate — because you’re not pitching a cold product, you’re sharing the story of a product that already got external validation.
The Multi-Launch Strategy
After your first #1, the natural instinct is to wait for the “next big thing” to launch. That’s wrong.
Every significant product update is a legitimate PH launch:
- Major feature release
- New platform/integration
- V2 or brand refresh
- Different product angle or use case
We launched AFFiNE 30+ times over 18 months. Each launch had a different angle: the initial open source release, the browser extension, the mobile app, the AI features, the collaboration layer. Each reached PH’s daily audience — most of whom had never seen the previous launches.
The compounding effect: Each badge accumulates on your PH profile page. By launch 10, your PH profile shows 10 badges, which makes the listing itself more credible and attracts more organic PH traffic before you even start pushing.
The weekly and monthly badge multipliers (7× and 30× more exposure respectively) mean that consistently executing good-but-not-perfect launches often compounds to more total exposure than one viral launch.
The Budget Question
Under $2K budget? Put it entirely into LinkedIn DM outreach. Three people DMing personalized messages to founders and makers full-time on launch day will generate 200–400 quality upvotes — more conversion-efficient than any paid channel.
$2K–$5K budget? Add 5–8 Twitter KOLs in your product category ($150–300 each). Require them to upvote and comment on PH as part of the deal (get it in writing — most won’t do it unless you make it explicit).
$5K+ budget? Add LinkedIn KOLs in your specific vertical. Vertical KOLs (designers, developers, marketers specific to your category) convert at significantly higher rates than generic tech accounts. One well-matched vertical KOL > ten generic tech accounts.
What not to spend on: Vote-exchange communities and “upvote packages.” PH’s clearing algorithm has gotten significantly better at identifying coordinated voting patterns. The risk of disqualification is real — I’ve watched products get removed from the leaderboard in real time.
Common Mistakes That Cost Rankings
Launching without warming up your PH account. If you’re the maker, your PH account should be active for 2+ months before launch. An account that has never interacted with PH and suddenly starts voting and commenting looks like a bot.
Treating comments as an afterthought. The comment section is a ranking signal. If you post a maker comment and then don’t respond for 4 hours, you’re leaving ranking points on the table.
Not having a post-launch email sequence ready. PH sends you a one-time burst of traffic. If your email capture isn’t live and automated, you’re handing that traffic back to the internet.
Launching on the wrong week. Experienced teams study hunted.space before picking their date. The difference in competition between week 1 (when everyone launches at month start) and week 3 is significant.
📚 Related Reading
More tools → Growth Tools Directory
30次 Product Hunt #1 的完整操作手册。覆盖发布前准备、当天执行、评论话术、猎手选择，一步一步可执行。