Product Hunt Launch Playbook: The Definitive Guide
I've launched on Product Hunt 30+ times and won #1 Daily on 30 of them. This isn't another generic guide — it's the exact playbook we used at AFFiNE to get 33,000 GitHub stars.
What You'll Learn
This guide consolidates everything I've written about Product Hunt launches into one resource:
| Topic | What's Covered |
|---|---|
| Strategy | Why PH matters, setting goals, timing |
| Preparation | 6-week timeline, assets, community |
| Launch Day | Hour-by-hour tactics |
| Conversion | Turning traffic into users |
| Open Source | Special tactics for OSS projects |
Part 1: Strategy Foundation
Why Product Hunt Still Matters in 2026
Product Hunt isn't a growth channel — it's a validation and momentum accelerator.
The real value:
- 🎯 Targeted audience: Early adopters actively seeking new tools
- 📧 Email capture opportunity: 1,000-3,000 leads from a #1 launch
- 🔗 Backlinks & PR: Featured in newsletters, picked up by media
- ✅ Social proof: "#1 on Product Hunt" badge has weight
What PH is NOT:
- ❌ A sustainable customer acquisition channel
- ❌ A place for "finished" products (early adopters want to discover)
- ❌ Something you can game with fake votes
Deep dive: Product Hunt Launch Strategy: From Zero to #1 Daily
Setting the Right Goals
Stop optimizing for upvotes. Upvotes are vanity metrics.
Your real KPIs:
- Email signups (target: 1,000+)
- Quality comments (engagement signals)
- Conversion rate (visitors → signups)
| Launch Result | Expected Traffic | Realistic Email Capture |
|---|---|---|
| Top 10 | 2,000-3,000 | 200-400 |
| Top 5 | 5,000-7,000 | 500-800 |
| #1 Daily | 10,000+ | 1,000-3,000 |
Part 2: The 6-Week Preparation Timeline
Week 1-2: Foundation
Build your seed audience first. This is the #1 mistake founders make.
You need 400+ supporters before launch:
- Newsletter subscribers
- Twitter followers who engage
- Community members you've helped
- Beta users
Actions:
- [ ] Audit your existing audience
- [ ] Start a "launching soon" waitlist
- [ ] Join 3-5 adjacent communities (Indie Hackers, relevant subreddits)
Week 3-4: Community Building
Product Hunt amplifies momentum. It doesn't create it.
Spend these weeks:
- Helping others in startup communities
- Sharing genuine value (not promoting)
- Building relationships with potential supporters
Checklist: Startup Launch Checklist: 47 Tasks Before, During & After Launch Day
Week 5: Asset Preparation
Your PH listing:
- Tagline: < 60 characters, benefit-focused
- Description: Problem → Solution → Proof
- Images: 4-6 high-quality screenshots or GIFs
- First comment: Your maker story (draft it now)
Your website:
- Clear CTA above the fold
- Email capture form ready
- Fast loading (< 2s)
- Mobile optimized
Week 6: Final Prep
- [ ] Schedule launch for Tuesday-Thursday
- [ ] Brief your supporters (but don't ask for votes yet)
- [ ] Test all links and forms
- [ ] Prepare email automation for new signups
- [ ] Write social media posts for launch day
Part 3: Launch Day Execution
Timing
Launch at 12:01 AM Pacific Time to get the full 24-hour window.
Best days: Tuesday, Wednesday, Thursday
Avoid: Monday (high competition), Friday (low traffic), Weekends
The First Hour (Critical)
- Post your maker comment immediately — Tell your story, not your features
- Notify seed audience — "We just launched, would love your feedback"
- Start responding to comments — Every single one
The Quality Algorithm
Product Hunt's ranking isn't just about vote count. It weighs:
| Factor | Weight | What It Means |
|---|---|---|
| Account age | High | Votes from 6+ month accounts matter more |
| Engagement | High | Comments and time-on-page |
| Authenticity | High | Natural traffic patterns |
| Vote velocity | Medium | Steady growth, not spikes |
What gets you penalized:
- ❌ Mass votes from new accounts
- ❌ Vote exchange groups
- ❌ Asking people to "upvote" (ask for "feedback" instead)
Tactics deep dive: Product Hunt Launch: 7 Tactics That Got Us #1 (30 Times)
Hour-by-Hour Checklist
Hours 1-4 (12am-4am PT):
- Post maker comment
- Notify core supporters
- Respond to early comments
Hours 5-12 (4am-12pm PT):
- Monitor ranking
- Continue engaging
- Share on social (not asking for votes)
- Brief supporters in different time zones
Hours 13-20 (12pm-8pm PT):
- Peak traffic time
- Maximum engagement
- Update maker comment if needed
Hours 21-24 (8pm-12am PT):
- Final push
- Thank supporters
- Plan post-launch follow-up
Part 4: Converting Traffic
Email Capture Strategy
Offer something valuable in exchange for email:
- Free template or resource
- Early access to new features
- Exclusive community access
- Launch discount
Landing page formula:
Headline: Clear benefit
Subhead: How you deliver it
Social proof: Logos, numbers, testimonials
CTA: Single, clear action (email signup)
Post-Launch Email Sequence
Set this up BEFORE launch:
| Timing | Content | |
|---|---|---|
| 1 | Immediate | Welcome + immediate value |
| 2 | Day 2 | Product walkthrough |
| 3 | Day 4 | Case study / social proof |
| 4 | Day 7 | Limited offer |
| 5 | Day 10 | Final CTA |
Part 5: Open Source Special Tactics
If you're launching an open source project, the game is different.
GitHub Stars as Secondary KPI
For OSS, track both:
- Email signups (primary)
- GitHub stars (secondary)
Stars provide:
- Credibility for future fundraising
- Community validation
- Contributor attraction
OSS-specific guide: Product Hunt for Open Source: The Step-by-Step Playbook
Combining PH + GitHub Growth
The AFFiNE playbook:
- Launch on PH → Drive traffic to GitHub
- Hit GitHub Trending → More organic stars
- Leverage stars for press/community building
- Repeat with new features
GitHub growth deep dive: How I Got 33K GitHub Stars: The Complete Marketing Playbook
The Cold Start Problem
Getting your first 1,000 stars is the hardest part.
Phase 1 (0-100 stars): Your personal network
Phase 2 (100-1,000 stars): Content + communities
Phase 3 (1,000+ stars): Organic + viral moments
Cold start tactics: The Cold Start Problem for GitHub Projects: How to Get Your First 1,000 Stars
Part 6: After the Launch
Day 2-7: Follow Up
- [ ] Send thank you messages to top engagers
- [ ] Reply to any unanswered comments
- [ ] Share launch results on social
- [ ] Start nurturing email list
Week 2-4: Capitalize
- [ ] Reach out to people who showed interest
- [ ] Write a "lessons learned" post
- [ ] Plan your next launch (yes, you can launch again)
Long Term
Product Hunt isn't one-and-done. You can launch:
- Major new features
- V2 or rebrand
- Different product angles
We launched AFFiNE multiple times over 18 months.
Complete Resource Library
I've written extensively about each part of this process:
Product Hunt
- Product Hunt Launch: The Complete 2026 Playbook for #1
- Product Hunt Launch: 7 Tactics That Got Us #1 (30 Times)
- Product Hunt Launch Strategy: From Zero to #1 Daily
- Product Hunt for Open Source: The Step-by-Step Playbook
GitHub Stars
- How I Got 33K GitHub Stars: The Complete Marketing Playbook
- GitHub Star Growth: 7 Proven Tactics That Got Us 33k Stars
- The Cold Start Problem for GitHub Projects
- GitHub Repo Promotion: 15 Channels That Actually Drive Stars
General Launch
- Startup Launch Checklist: 47 Tasks
- Open Source Launch Checklist: 127 Tasks
- Developer Marketing Playbook
Key Takeaways
- Prepare 6 weeks ahead — PH amplifies momentum, doesn't create it
- Focus on email capture — Upvotes are vanity, emails are value
- Quality > Quantity — 100 engaged users beat 1,000 random votes
- Engage authentically — Respond to every comment
- Plan for multiple launches — It's a campaign, not a one-time event
Free Resources
📘 Gingiris Launch Playbook — Full open-source guide with templates
📗 Gingiris Open Source Marketing — OSS-specific tactics
📙 Gingiris B2B Growth — PLG and SLG strategies
Questions? Drop a comment below or find me on Twitter @iris_carrot.
Top comments (0)