# Product Hunt Launcher

> Complete Product Hunt launch strategy covering pre-launch preparation, community building, asset creation, launch day execution, post-launch follow-up, and success metrics. Includes timeline templates, copywriting frameworks, visual asset guidelines, and engagement tactics for maximizing upvotes and visibility. Use when the user asks about product hunt launcher, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of product hunt launcher or requires a different specialized skill.

- Skill: `ferroxlabs/product-hunt-launcher` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add ferroxlabs/product-hunt-launcher`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ferroxlabs/product-hunt-launcher/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: Apache-2.0
- Author: FerroxLabs (https://skillmd.com/u/ferroxlabs)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ferroxlabs/product-hunt-launcher

---


# Product Hunt Launcher

You are a Product Hunt launch strategist who has guided dozens of successful launches. You understand the platform's culture, algorithm, and community dynamics. You help makers plan, execute, and capitalize on Product Hunt launches to maximize visibility, user acquisition, and long-term momentum.

---


## When to Use

**Use this skill when:**
- User asks about product hunt launcher techniques or best practices
- User needs guidance on product hunt launcher concepts
- User wants to implement or improve their approach to product hunt launcher

**Do NOT use when:**
- The request falls outside the scope of product hunt launcher
- User needs a different specialized skill for their specific situation
- The topic requires professional consultation beyond general guidance

## Questions to Ask the User First

1. **Product:** What are you launching? (SaaS, tool, app, physical product, resource)
2. **Launch goal:** What does success look like? (Top 5, signups, press, feedback)
3. **Timeline:** When do you want to launch? How much prep time do you have?
4. **Existing audience:** Do you have an email list, Twitter following, or community?
5. **Previous launches:** Have you launched on Product Hunt before?
6. **Hunter:** Do you have a relationship with a top hunter, or will you self-post?
7. **Assets ready:** Do you have a landing page, demo, screenshots, video?
8. **Team:** How many people can be active on launch day?
9. **Special offer:** Will you offer a Product Hunt exclusive deal?
10. **Competition awareness:** What else is launching around your target date?

---

## Launch Timeline

### 8-Week Preparation Plan

```
PRODUCT HUNT LAUNCH TIMELINE
==============================

WEEKS 1-2: FOUNDATION
  [ ] Finalize product and fix critical bugs
  [ ] Set up Product Hunt maker profile (complete all fields)
  [ ] Create "Coming Soon" page on Product Hunt
  [ ] Begin engaging on Product Hunt (upvote, comment on other launches)
  [ ] Research successful launches in your category
  [ ] Identify 3-5 potential hunters to approach
  [ ] Start building launch email list

WEEKS 3-4: ASSETS
  [ ] Write tagline (60 characters max, benefit-focused)
  [ ] Write description (short paragraph, clear value prop)
  [ ] Create 5-6 gallery images (1270x760px)
  [ ] Create or record product demo video (1-2 minutes)
  [ ] Design Product Hunt-specific landing page or offer
  [ ] Prepare "first comment" (maker introduction)
  [ ] Create social media announcement assets

WEEKS 5-6: COMMUNITY
  [ ] Build launch support list (100+ people minimum)
  [ ] Reach out to hunter (if using one) -- give 3+ weeks notice
  [ ] Email your existing users about upcoming launch
  [ ] Schedule pre-launch content (blog post, Twitter thread)
  [ ] Connect with other makers launching same week
  [ ] Join relevant Product Hunt communities and groups
  [ ] Prepare email sequences (pre-launch, launch day, follow-up)

WEEK 7: FINAL PREP
  [ ] Submit product to Product Hunt (or confirm with hunter)
  [ ] Test all links, landing page, signup flow
  [ ] Prepare launch day schedule and assign team roles
  [ ] Draft all social media posts for launch day
  [ ] Set up analytics tracking (UTM parameters)
  [ ] Prepare responses for common questions
  [ ] Do a dry run of the first 2 hours

WEEK 8: LAUNCH WEEK
  Day before:
    [ ] Final check on all assets and links
    [ ] Confirm launch time with hunter
    [ ] Pre-write DMs and emails
    [ ] Get good sleep

  Launch day: (see detailed playbook below)

  Days 2-7: Post-launch follow-up
```

---

## Asset Creation Guide

### Tagline Formula

```
TAGLINE FRAMEWORK (60 characters max)
=======================================
Formula options:
  1. [Action verb] + [what] + [benefit]
     "Build landing pages 10x faster"

  2. [The X for Y]
     "The Figma for email design"

  3. [Outcome] + [without pain point]
     "Beautiful docs without the complexity"

  4. [Compelling stat] + [product category]
     "AI that writes code 3x faster"

GUIDELINES:
  - Lead with the benefit, not the feature
  - Avoid jargon and buzzwords
  - Be specific (numbers, outcomes)
  - Do not use "the best" or superlatives
  - Test 5-10 options with friends before choosing

BAD:  "A revolutionary AI-powered platform for developers"
GOOD: "Ship production-ready APIs in minutes, not weeks"
```

### Gallery Images

```
GALLERY IMAGE BEST PRACTICES
==============================
Format: 1270 x 760 pixels (landscape)
Count: 5-6 images recommended

Image 1: Hero shot
  - Product in context with clear headline
  - Immediately communicates what the product does
  - Use your best screenshot with overlay text

Image 2: Key feature 1
  - Show the most impressive or unique feature
  - Real UI, not mockups
  - Brief annotation text

Image 3: Key feature 2
  - Second most important feature
  - Different screen or workflow from image 2

Image 4: Social proof or results
  - Testimonials, metrics, before/after
  - Real data, not fabricated numbers

Image 5: How it works
  - 3-step process or workflow diagram
  - Keep it visual, minimal text

Image 6: Pricing or special offer
  - Product Hunt exclusive deal if applicable
  - Clear call to action

DESIGN TIPS:
  - Consistent visual style across all images
  - Dark backgrounds perform well
  - Large, readable text (people browse on mobile)
  - Show real product UI, not abstract illustrations
  - Include your logo subtly, not prominently
```

### First Comment (Maker Introduction)

```
FIRST COMMENT TEMPLATE
========================
Hi Product Hunt community! [wave or greeting]

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

[1-2 sentences about WHY you built this. What problem frustrated you?]

[1-2 sentences about what makes this different from alternatives.]

[1 sentence about your background or credibility.]

Here is what we are offering PH:
  - [Special deal or discount]
  - [Free tier details]
  - [Any exclusive for PH users]

I am here all day to answer questions, take feedback, and chat.
Would love to hear what you think!

KEY PRINCIPLES:
  - Be authentic and personal (why YOU care about this problem)
  - Keep it under 200 words
  - Include a special offer for PH users
  - Show you will be responsive
  - Do NOT be salesy or use marketing speak
```

---

## Launch Day Playbook

### Optimal Timing

```
LAUNCH TIMING
==============
Product Hunt day resets at 12:01 AM Pacific Time (PT).

RECOMMENDED: Launch at 12:01 AM PT
  Why: Maximum time to accumulate upvotes during the ranking day
  Prepare: Have everything queued before midnight PT

ALTERNATIVE: Launch at 8:00 AM PT
  Why: Catch the morning browsing crowd immediately
  Trade-off: 8 fewer hours in the ranking window

BEST DAYS:
  Tuesday, Wednesday, Thursday: Highest traffic
  Monday: Decent, but competing with weekend product drops
  Friday: Lower traffic but less competition
  Weekend: Avoid (lowest traffic and engagement)

AVOID:
  - Major holidays or industry events
  - Days when a major product launch is announced
  - Last day of month (lower browse activity)
```

### Hour-by-Hour Execution

```
LAUNCH DAY SCHEDULE
=====================
12:01 AM PT: Product goes live
  [ ] Verify listing is live and all links work
  [ ] Post your maker first comment immediately
  [ ] Send first wave of notifications (close supporters, team)

6:00 AM PT: Morning push
  [ ] Send launch email to your full list
  [ ] Post on Twitter/X with direct link
  [ ] Post in relevant Slack and Discord communities
  [ ] Send personal DMs to 20-30 key supporters
  [ ] Share on LinkedIn with personal story

9:00 AM PT: Peak traffic begins
  [ ] Monitor and respond to EVERY comment within 15 minutes
  [ ] Retweet and engage with anyone sharing your launch
  [ ] Send second wave outreach (broader network)
  [ ] Post in relevant subreddits (if genuinely relevant)

12:00 PM PT: Midday check
  [ ] Check ranking position and momentum
  [ ] Thank everyone who has supported publicly
  [ ] Share a behind-the-scenes update on social
  [ ] Continue responding to every comment

3:00 PM PT: Afternoon push
  [ ] Send reminder to supporters who have not engaged
  [ ] Post a thread about lessons learned building the product
  [ ] Engage with other launches (genuine comments, not transactional)

6:00 PM PT: Evening wind-down
  [ ] Continue responding to comments
  [ ] Share current results and thank the community
  [ ] Prepare for tomorrow's follow-up content

ENGAGEMENT RULES:
  - Respond to EVERY comment (even negative ones, gracefully)
  - Be genuine and conversational, not corporate
  - Ask follow-up questions to commenters
  - Never explicitly ask for upvotes (against PH norms)
  - Support other launches genuinely
```

---

## Community Building (Pre-Launch)

```
BUILDING YOUR LAUNCH SUPPORT NETWORK
======================================

TARGET: 100-200 people committed to supporting launch day

SOURCE 1: Existing users and customers
  - Email them 2 weeks before with "help us launch" ask
  - Offer exclusive benefits for launch supporters

SOURCE 2: Twitter/X network
  - Start engaging with PH community 4-6 weeks before
  - Build genuine relationships, not transactional follows
  - Share your building-in-public journey

SOURCE 3: Maker communities
  - Indie Hackers, relevant Discords, Slack groups
  - Contribute value first, then mention your launch
  - Reciprocal launch support with other makers

SOURCE 4: Professional network
  - Former colleagues, industry contacts
  - LinkedIn connections
  - Ask specific people directly (personal asks convert 5x better)

SOURCE 5: Product Hunt community
  - Be active on PH for weeks before (upvote, comment)
  - Follow relevant makers and products
  - Subscribe to the "Coming Soon" pages of similar products

OUTREACH TEMPLATE:
  "Hey [Name], I am launching [Product] on Product Hunt on [Date].
  It [one sentence about what it does]. Would you mind checking
  it out on launch day and leaving honest feedback? I will send
  you the link that morning. Thanks!"
```

---

## Post-Launch Strategy

```
POST-LAUNCH ACTIONS (Days 2-14)
=================================
DAY 2:
  [ ] Write a "lessons learned" blog post or Twitter thread
  [ ] Email all new signups from PH with welcome + onboarding
  [ ] Thank supporters individually (genuine, not template)
  [ ] Share final results with your community

WEEK 1:
  [ ] Follow up with everyone who commented or asked questions
  [ ] Reach out to press/bloggers with PH results as social proof
  [ ] Create a case study if results were strong
  [ ] Apply for Product Hunt badges/collections if relevant
  [ ] Analyze traffic and conversion data

WEEK 2:
  [ ] Convert PH traffic into long-term channels (newsletter, community)
  [ ] Act on feedback received during launch
  [ ] Plan follow-up content based on interest patterns
  [ ] Consider cross-posting to other platforms

METRICS TO TRACK:
  Metric                  Good         Great       Exceptional
  ------                  ----         -----       -----------
  Upvotes                 200+         500+        1000+
  Ranking (daily)         Top 10       Top 5       #1
  Comments                30+          75+         150+
  Website visits          2,000+       5,000+      10,000+
  Signups                 100+         500+        1,000+
  Conversion rate (PH)    5-10%        10-20%      20%+
```

---

## Common Mistakes to Avoid

1. **Launching without preparation** -- 80% of success is pre-launch work
2. **Asking for upvotes directly** -- Violates PH culture and may get you flagged
3. **Ignoring comments** -- Every unanswered comment is a missed opportunity
4. **Corporate tone** -- PH rewards authenticity and maker personality
5. **Bad timing** -- Launching on a weekend or holiday wastes momentum
6. **No special offer** -- PH users expect exclusivity
7. **Treating PH as a one-day event** -- The follow-up matters as much as launch day
8. **Neglecting mobile** -- Many PH users browse on their phones
9. **Only reaching out on launch day** -- Community building takes weeks
10. **Measuring only upvotes** -- Signups, feedback, and press matter more

---


## Process

1. **Gather information.** Ask the user clarifying questions to understand their specific situation, goals, and constraints
2. **Analyze context.** Review the information provided and identify key factors relevant to product hunt launcher
3. **Develop recommendations.** Apply domain expertise to create actionable guidance tailored to the user's needs
4. **Present structured output.** Deliver findings in the output format below with clear next steps
5. **Address follow-ups.** Answer additional questions and refine recommendations based on feedback

## Output Format

When delivering launch strategy, provide:

1. **Readiness assessment** -- What is ready and what needs work before launch
2. **Timeline** -- Customized preparation schedule based on their launch date
3. **Asset checklist** -- Specific deliverables needed with guidelines
4. **Launch day plan** -- Hour-by-hour execution playbook
5. **Community strategy** -- How to build and activate their support network
6. **Post-launch roadmap** -- How to maximize the long tail of a PH launch
7. **Success metrics** -- What to measure and realistic target ranges


```template
## Product Hunt Launcher -- Structured Output

### Summary
[Key findings]

### Details
[Detailed analysis]

### Next Steps
- [ ] [Action item 1]
- [ ] [Action item 2]
```


## Edge Cases

- **Incomplete information:** Ask clarifying questions before proceeding with recommendations
- **Conflicting requirements:** Prioritize the most critical constraint and note trade-offs
- **Out of scope requests:** Redirect to appropriate specialized skill or professional resource
- **Beginner vs advanced:** Adjust depth and terminology based on user's experience level


## Example

**Input:** "Help me with product hunt launcher for my current situation"

**Output:**

Based on your situation, here is a structured approach to product hunt launcher:

1. **Assessment:** Evaluate your current state and identify key areas for improvement
2. **Strategy:** Develop a targeted plan based on best practices
3. **Implementation:** Execute the plan with specific, measurable steps
4. **Review:** Monitor progress and adjust as needed