---
title: "Product Hunt Launch Playbook"
description: "**Day 14: Account & Asset Preparation**"
type: skill
canonical_url: https://claudary.paisolsolutions.com/skills/product-hunt-playbook
source: "Claudary"
difficulty: intermediate
author: "Claude Code Knowledge Pack"
date: 2026-07-10T11:37:05.411Z
license: CC-BY-4.0
attribution: "Product Hunt Launch Playbook — Claudary (https://claudary.paisolsolutions.com/skills/product-hunt-playbook)"
---

# Product Hunt Launch Playbook
**Day 14: Account & Asset Preparation**

## Overview

# Product Hunt Launch Playbook

## 2-Week Preparation Timeline

### Week 1 (14-8 days before launch)

**Day 14: Account & Asset Preparation**

- Create or update Product Hunt maker profile with real photo, bio, and social
  links
- Prepare all visual assets:
  - Gallery images: 5-6 images (1270x760px), first image is most important
  - Logo: 240x240px, clean on white background
  - Animated GIF: optional but significantly boosts engagement
- Write tagline (60 char max) — focus on benefit, not feature

**Day 13: Hunter Selection**

- Option A: Self-hunt (fine if you have a network; no algorithmic penalty)
- Option B: Find a hunter with 1,000+ followers

**Hunter Outreach Template:**

```
Subject: Would you hunt [App Name] on Product Hunt?

Hi [Hunter Name],

I've been following your Product Hunt activity — you clearly have great taste in [category] products.

I'm launching [App Name], which [one-sentence value prop]. [One specific metric or proof point, e.g., "We have 2,000 beta users with 45% D7 retention."]

I'd love for you to hunt it. I have all assets ready and a community of [number] people prepared to support the launch.

Would you be open to a quick 10-min call this week?

[Your name]
[Link to app / landing page]
```

**Day 12-10: Build Activation List**

- Compile a list of 50-100 people who will authentically engage on launch day
- Sources: beta users, Twitter/X followers, newsletter subscribers, friends in
  tech, indie maker communities
- Prepare a short, personalized message for each (do NOT send identical
  messages)
- Do NOT ask for upvotes — ask people to "check out the launch and share
  feedback"

**Day 9-8: Prepare Launch Day Content**

- Write the maker's comment (see template below)
- Draft 5 social media posts (Twitter/X, LinkedIn, Instagram, Threads, Mastodon)
- Prepare an email blast to existing users/newsletter
- Write a blog post about the launch story

### Week 2 (7-1 days before launch)

**Day 7: Select Launch Day**

- Best days: Tuesday, Wednesday, Thursday
- Avoid: Monday (competition from weekend buildup), Friday-Sunday (lower
  traffic)
- Check Product Hunt upcoming page for major competing launches
- Avoid Apple event days, major holidays, or big tech news days

**Day 5: Test Everything**

- Verify App Store / Play Store links work
- Test all gallery images render correctly
- Confirm landing page loads fast and has clear CTA
- Ensure the app is stable — no known crashes

**Day 3: Pre-notify Key Supporters**

- Send personal messages to activation list: "Launching on Product Hunt this
  [day]. I'll share the link early morning — would love your genuine feedback."
- Brief any team members on the plan

**Day 1 (Launch Eve):**

- Schedule social posts for launch morning
- Prepare email blast, ready to send
- Get a good night's sleep — launch day is long

## Launch Day Execution

### 12:01 AM PT — Go Live

- Post goes live (either you or your hunter publishes)
- Immediately post the maker's comment (see template below)
- Share the direct Product Hunt link — NOT a redirect or shortened URL

### 6:00-7:00 AM PT — Morning Push

- Send activation messages: "We're live on Product Hunt! Would love your
  thoughts: [link]"
- Send email blast
- Post on social media
- Share in relevant Slack/Discord communities (where allowed)

### Throughout the Day

- Respond to EVERY comment on the Product Hunt page within 30 minutes
- Share progress updates on social media ("We're #3 on Product Hunt right now!")
- Thank people who share or comment, personally
- Do NOT ask for upvotes — this violates PH guidelines and can get you penalized

### 11:59 PM PT — Day Ends

- Voting period ends at midnight PT
- Post a thank-you update regardless of ranking

## Maker's Comment Template

Post this as the first comment immediately after launch:

```
Hey Product Hunt! 👋

I'm [Name], the maker of [App Name].

**Why I built this:**
[2-3 sentences about the personal problem or frustration that led to building the app. Make it relatable and specific.]

**What it does:**
[3-4 bullet points of key features — focus on outcomes, not features]
- [Outcome 1]
- [Outcome 2]
- [Outcome 3]

**Where we are:**
[1-2 sentences about traction, beta feedback, or early results. Include specific numbers if possible.]

**What's next:**
[1-2 sentences about upcoming features or roadmap items you're excited about.]

I'd love to hear your feedback — especially about [specific aspect you want feedback on]. I'll be here all day responding to comments!

[Optional: special offer for PH community, e.g., "Use code PRODUCTHUNT for 50% off the first year."]
```

## Post-Launch Follow-Up (Days 2-7)

**Day 2:**

- Write a "lessons learned" Twitter/X thread about the launch
- Follow up with everyone who commented — thank them, answer questions
- Analyze traffic sources in your analytics

**Day 3-5:**

- Write a blog post: "How we launched on Product Hunt: results and lessons"
- Share results transparently (upvotes, traffic, signups, revenue impact)
- Connect with other makers who launched the same day

**Day 7:**

- Compile final metrics: upvotes, comments, website traffic, signups, downloads
- Identify which activation channels drove the most engagement
- Document lessons learned for future launches

## Common Mistakes to Avoid

1. **Asking for upvotes** — Product Hunt detects and penalizes this. Ask for
   "feedback" instead.
2. **Using URL shorteners** — PH may flag these. Use the direct producthunt.com
   link.
3. **Launching with bugs** — The PH audience is tech-savvy and will call out
   issues publicly.
4. **Ignoring comments** — Not responding makes the launch look abandoned.
5. **Launching on Friday** — Weekend traffic is significantly lower.
6. **Sending identical mass messages** — PH detects coordinated voting.
   Personalize outreach.
7. **Not having a special offer** — PH community expects an exclusive deal or
   discount.

---

Source: [Claudary](https://claudary.paisolsolutions.com/skills/product-hunt-playbook) · https://claudary.paisolsolutions.com