Guide 02

Hacker News & Product Hunt Launch Guide

A comprehensive guide to launching developer tools on HN and Product Hunt. From understanding the platforms to executing successful launches.

Part 1: Hacker News Fundamentals

Understanding Hacker News

HN is not a marketing channel — it's a community of builders who share and discuss interesting things. Your content needs to genuinely interest this audience.

What works:

What doesn't work:

Part 2: The HN Launch Formula

Launch Timeline

The Tailscale Framework

Tailscale consistently hits the front page. Here's their pattern:

Problem → Obvious Solution → Why Obvious Solution Fails → Product → How It Works

This structure:

Title Strategy

The Power of Understatement:

Tested variations:

Winner: The understated, story-like title.

Best practices:

Content Structure

  1. Create something that doesn't feel promotional — Your post should teach, share, or inform first.
  2. Explain benefits through problems — Don't list features. Explain the pain you solve.
  3. Go deep with new information — HN readers want substance. Don't hold back.
  4. Satisfy curiosity about "how it works" — Not "how to gain X by using Y" but rather "How to build Y from scratch"
  5. Write dev-to-dev, conversational — Use technical jargon. Don't dumb it down.

Post Length

Some of the best launches are long.

fly.io example: Hundreds of words explaining the technical approach in detail.

Rule: Use 700 words if that's what it takes to explain your approach properly. Better too thorough than too thin.

Part 3: Preparing for Launch

GlassFlow Case Study

They reached #1 on Show HN and stayed there for 12+ hours. Key learnings:

  1. Follow the guidelines exactly — Use the format that works, the right tone of voice.
  2. Spend the biggest chunk on the problem — Explain the problem and why obvious solutions don't work.
  3. Prepare for success — The last thing you want is hitting the front page with a bad experience waiting.
  4. Explain how it works in detail — What you tried, why it didn't work. "Hacker to hacker."

Before launch, audit:

The Preparation Timeline

GlassFlow took a week to rework their post based on feedback:

  1. First draft (too high-level)
  2. Feedback round
  3. Rewrite to more technical, straightforward explanation
  4. Final review
  5. Launch

Don't rush this process.

Part 4: Writing Your Show HN

HN Post Anatomy

The Information Flow

Lead with:

Then:

End with:

Tone Calibration

Do:

Don't:

Part 5: Reddit/HN Cross-Posting

The Reddit-Then-HN Trick

Post first on relevant subreddits to:

Then bring a refined version to HN.

Part 6: Product Hunt Launch

The PH Playbook (Matteo Tittarelli)

This playbook has gotten 3 tools to #1 of the day/week.

Pre-Launch (2-4 weeks before)

  1. Build your hunter network
    • Identify relevant hunters
    • Reach out early
    • Prepare materials for them
  2. Prepare assets
    • High-quality screenshots
    • Product video (short, punchy)
    • Compelling tagline
    • Description that hooks
  3. Seed your launch
    • Tell your community
    • Email your users
    • Prep social posts

Launch Day

  1. Timing
    • Launch at 12:01 AM PST (PH resets at midnight Pacific)
    • Have team ready for early hours
  2. First hour is critical
    • Activate your network
    • Respond to every comment
    • Share on social immediately
  3. Throughout the day
    • Continuous engagement
    • Cross-post updates
    • Thank supporters

Post-Launch

  1. Follow up
    • Thank everyone who supported
    • Share results
    • Announce what's next
  2. Convert interest
    • Special offers for PH audience
    • Capture leads
    • Nurture relationships

Part 7: Launch Weeks

The Supabase Model

Why launch weeks work:

Launch Week Structure

Day by day:

Content for each day:

Learnings from Resend

Part 8: Advanced Strategies

Prepare for Success, Not Just Launch

The GlassFlow lesson: They prepared their entire developer journey before launch because they knew the worst thing would be hitting #1 with a bad experience.

Before any launch:

  1. Audit your core developer journey
  2. Test signup → first value
  3. Ensure docs are solid
  4. Have support ready
  5. Prepare for traffic spike

The "Launch Then Iterate" Trap

Don't:

Do:

Engineering-as-Marketing for Future Launches

Create free tools that build reputation before your product launch:

When you launch the paid product, you already have credibility.

Quick Reference: Launch Checklist

Pre-Launch (2 weeks before)

Launch Day

Post-Launch

Resources & Further Reading

Hacker News Strategy

Product Hunt

Case Studies

Podcasts