product-hunt-launch

---
name: product-hunt-launch
parent: ccc-marketing
brand: Kevin Z's CC Commander
description: "Complete Product Hunt launch playbook: pre-launch community building, launch day execution, post-launch conversion. Includes timeline template from T-30 to T+7."
version: 1.0.0
tags:
  - product-hunt
  - launch
  - go-to-market
  - community
  - startup
---

# Product Hunt Launch Playbook

Complete Product Hunt launch strategy — from 30 days before launch to 7 days after. Covers hunter selection, community building, launch day execution, and post-launch conversion.

## When to Use

- You're launching a new product or major feature on Product Hunt
- You want to maximize upvotes, comments, and visibility on launch day
- You need a structured timeline to coordinate your team
- You want to convert Product Hunt traffic into long-term users
- You're evaluating whether Product Hunt is the right channel for your product

## Should You Launch on Product Hunt?

**Good fit:** Developer tools, SaaS, design tools, AI products, productivity apps, indie hacker projects, browser extensions, mobile apps with tech-savvy audiences.

**Poor fit:** Local businesses, enterprise-only products (no self-serve), physical products (unless tech-adjacent), products requiring long sales cycles.

**Prerequisite check:**
- [ ] Product has a free tier or trial (PH audience expects to try before committing)
- [ ] Landing page converts (PH sends traffic — if your site leaks, upvotes don't matter)
- [ ] You can dedicate a full day to launch engagement
- [ ] You have at least a small community or network to amplify

## Timeline: T-30 to T+7

### T-30 to T-14: Foundation

**Community Building**
- [ ] Create/optimize your Product Hunt maker profile (bio, links, avatar)
- [ ] Start engaging on Product Hunt daily — upvote, comment on other launches genuinely
- [ ] Join 3-5 relevant Product Hunt collections and communities
- [ ] Build a launch waitlist (email or landing page with "notify me" CTA)
- [ ] Identify and engage with 50-100 active PH community members in your niche

**Hunter Selection**
- [ ] Decide: self-hunt or get hunted by a top hunter
- [ ] If using a hunter: reach out to 3-5 hunters with large followings (5K+)
- [ ] Provide hunter with: product access, talking points, assets
- [ ] Confirm hunter availability for your target launch date

**Asset Preparation**
- [ ] Draft tagline (max 60 chars — this is the most important copy you'll write)
- [ ] Write product description (keep it concise, benefit-focused, no buzzwords)
- [ ] Create gallery images (5 images max, 1270x760px):
  - Image 1: Hero shot — what the product does in one glance
  - Image 2: Key feature #1
  - Image 3: Key feature #2
  - Image 4: Social proof or stats (if available)
  - Image 5: Pricing or CTA
- [ ] Record demo video (optional but highly recommended, 1-2 minutes max)
- [ ] Prepare Product Hunt-exclusive offer (discount, extended trial, bonus feature)

### T-14 to T-7: Preparation

**Content & Social**
- [ ] Write 3-5 teaser posts for Twitter/LinkedIn (don't mention PH yet)
- [ ] Draft launch announcement posts for all social channels
- [ ] Write a "behind the scenes" or "why we built this" blog post
- [ ] Prepare email to your waitlist/newsletter announcing the launch
- [ ] Create shareable graphics for supporters to post

**Team Coordination**
- [ ] Assign launch day roles:
  - **Captain** — monitors PH page, responds to all comments
  - **Social lead** — posts updates, engages on Twitter/LinkedIn
  - **Support lead** — handles signups, onboarding issues, bugs
  - **Outreach lead** — DMs supporters, coordinates amplification
- [ ] Brief everyone on timeline and responsibilities
- [ ] Set up a war room channel (Slack/Discord) for real-time coordination

**Technical Readiness**
- [ ] Load test your site/app (PH traffic can spike hard)
- [ ] Set up analytics tracking (UTM: `?ref=producthunt`)
- [ ] Prepare onboarding flow optimized for PH visitors
- [ ] Create a PH-specific landing page or banner (optional but effective)
- [ ] Test signup flow end-to-end
- [ ] Set up real-time monitoring (uptime, error rates, signup funnel)

### T-7 to T-1: Final Prep

- [ ] Finalize all PH listing assets and submit as a draft
- [ ] Schedule social posts for launch day (but keep the PH link manual — add after going live)
- [ ] Draft your "first comment" (see template below)
- [ ] Send preview to 10-20 trusted supporters — ask them to upvote and comment on launch day
- [ ] Confirm hunter is ready (if using one)
- [ ] Test PH listing in draft/preview mode
- [ ] Prepare a "launch day" email draft for your list
- [ ] Get 8 hours of sleep the night before

### T-0: Launch Day

**Timing Strategy**
- Launch at **12:01 AM PT** (midnight Pacific) — maximizes the 24-hour window
- If you can't stay up: **6:00 AM PT** is the next best window (catches early risers)
- **Best days:** Tuesday, Wednesday, Thursday (avoid Monday/Friday — lower engagement)
- **Avoid:** Major tech events, Apple keynotes, holidays, other hyped launches

**Hour 0-1: Go Live**
- [ ] Publish the listing (or confirm hunter published)
- [ ] Post your first comment immediately (see template)
- [ ] Verify all links work (product, website, social)
- [ ] Send launch email to your waitlist/newsletter
- [ ] Post on Twitter with PH link
- [ ] Post on LinkedIn
- [ ] Share in relevant Slack/Discord communities (where self-promotion is allowed)
- [ ] DM your inner circle (20-30 people) with a personal ask to upvote + comment

**Hour 1-6: Momentum Building**
- [ ] Respond to EVERY comment on Product Hunt within 30 minutes
- [ ] Share real-time progress on Twitter ("We just hit #3! Thank you!")
- [ ] Send second wave of outreach to broader network
- [ ] Monitor for bugs and fix immediately
- [ ] Post behind-the-scenes content (screenshots of traffic, team reactions)
- [ ] Engage with other launches happening today (genuine comments, not quid pro quo)

**Hour 6-12: Sustain**
- [ ] Continue responding to all PH comments
- [ ] Share user testimonials or interesting comments as social posts
- [ ] Send a mid-day email update if you have a large list
- [ ] Reach out to tech journalists/bloggers covering your space
- [ ] Update the listing description if you're getting common questions

**Hour 12-24: Close Strong**
- [ ] Final push on social media
- [ ] Thank supporters publicly
- [ ] Share final position/stats teasers
- [ ] Respond to any remaining comments
- [ ] Capture screenshots of your ranking for later use

### First Comment Template

The first comment is your pitch. It sets the tone for the entire discussion.

```markdown
Hey Product Hunt! 👋

I'm [Name], [role] at [Product].

**Why we built this:**
[2-3 sentences about the problem you experienced personally. Make it relatable, not corporate.]

**What it does:**
[1-2 sentences. Clear, specific, no jargon.]

**What makes it different:**
- [Differentiator 1 — be specific]
- [Differentiator 2 — compare to status quo, not competitors]
- [Differentiator 3 — something surprising or delightful]

**Product Hunt exclusive:**
[Your special offer — discount, extended trial, lifetime deal, bonus feature]

I'll be here all day answering questions. Would love your feedback — what's the first thing you'd use this for?
```

### T+1 to T+3: Post-Launch Follow-Up

- [ ] Post a "thank you" with results on Twitter/LinkedIn
- [ ] Email everyone who signed up on launch day with onboarding tips
- [ ] Write a "Product Hunt launch retrospective" blog post (great for SEO + credibility)
- [ ] Reply to any remaining PH comments you missed
- [ ] Follow up with journalists/bloggers who showed interest
- [ ] Reach out to PH users who left detailed comments — they're your warmest leads
- [ ] Collect and organize user feedback from PH comments
- [ ] Update your website with the PH badge and final ranking

### T+3 to T+7: Conversion & Learning

- [ ] Analyze signup-to-activation funnel for PH cohort
- [ ] Identify drop-off points and optimize onboarding
- [ ] Send a follow-up email to PH signups who haven't activated
- [ ] Compare PH user behavior to other acquisition channels
- [ ] Document what worked and what didn't for future launches
- [ ] Reach out to top commenters for testimonials or case studies
- [ ] Add PH badge permanently to your landing page footer
- [ ] Plan your next PH launch (major update, new product, etc.)

## Engagement Rules

### Do
- Respond to every single comment — even simple "congrats" comments get a thank you
- Be genuine and personal in responses (no copy-paste replies)
- Ask follow-up questions to drive conversation
- Share transparently about your journey (people love founder stories)
- Upvote and comment on other launches (community karma matters)

### Don't
- Ask people to "please upvote" (against PH guidelines, community frowns on it)
- Send mass DMs asking for upvotes (PH detects and penalizes this)
- Use upvote-exchange groups or services (PH's algorithm catches this and will shadowban your product)
- Argue with negative feedback — acknowledge, thank, explain your perspective
- Spam communities with your PH link (earn the right to share by being a genuine member first)
- Create fake accounts to upvote (PH will remove your listing entirely)

## Metrics to Track

| Metric | Where to Find | What It Tells You |
|--------|--------------|-------------------|
| Upvotes | PH dashboard | Community reception |
| Comments | PH dashboard | Engagement depth |
| PH ranking (final) | PH page | Relative performance |
| Website visits (ref=producthunt) | Analytics | Traffic generated |
| Signups from PH | Your app analytics | Conversion from traffic |
| Activation rate (PH cohort) | Your app analytics | Quality of PH traffic |
| Press/blog mentions | Google Alerts | Amplification effect |
| Twitter impressions (launch day) | Twitter analytics | Social amplification |
| Email list growth | Email platform | Long-term value capture |

## Tagline Writing Guide

Your tagline is 60 characters. It's the single most important piece of copy.

**Formula:** `[What it does] for [who]` or `[Outcome] without [pain]`

**Good examples:**
- "Design emails people actually open" (benefit-focused)
- "Git for designers" (analogy-based)
- "Turn any API into a database" (transformation)
- "The open-source Calendly alternative" (positioning)

**Bad examples:**
- "Revolutionizing the future of work" (vague, buzzwordy)
- "AI-powered next-gen platform" (meaningless)
- "The best tool for teams" (too generic)

**Test your tagline:** Show it to 5 people who don't know your product. If they can't explain what it does after reading the tagline, rewrite it.

## Post-Launch: Converting PH Traffic

Product Hunt traffic is high-intent but short-lived. You have 48-72 hours to convert.

1. **PH-specific landing page** — Acknowledge they're coming from PH, show the exclusive offer prominently
2. **Simplified signup** — Reduce friction (social login, no credit card required)
3. **Immediate value** — First screen after signup should deliver an "aha moment" in under 60 seconds
4. **Follow-up sequence** — 3 emails over 7 days: welcome, key feature highlight, offer expiry reminder
5. **Community invitation** — Invite PH users to your Discord/Slack — they're early adopters who give feedback

## Budget Considerations

| Item | Cost Range | Notes |
|------|-----------|-------|
| Top hunter outreach | $0 (relationship-based) | Some charge $500-2K, but best hunters work for free with great products |
| Gallery design | $0-500 | DIY with Figma/Canva or hire on Fiverr |
| Demo video | $0-1,000 | Screen recording with Loom (free) or polished with editor |
| PH-exclusive offer | Variable | Discount/extended trial cost to you |
| Social ads (boost) | $0-500 | Optional — organic is usually enough |
| Total typical budget | $0-2,000 | Most successful launches spend under $500 |

## Anti-Patterns

- Launching without a free tier or trial (PH audience will not pay to try)
- Launching on Friday or Monday (lower traffic, weaker competition day = weaker signal)
- Not responding to comments (makes you look unengaged, hurts ranking)
- Asking for upvotes explicitly (community backlash + algorithmic penalty)
- Launching before product is stable (PH traffic will expose every bug)
- Treating PH as a one-time event (build ongoing PH community presence)
- Ignoring the post-launch window (most value comes from follow-up, not launch day)
- Over-investing in upvotes, under-investing in conversion (1000 upvotes and 0 signups = failure)