Hacker News Launch Strategy

Show HN is the highest-upside single launch channel for technical founders. Here's how to do it right.

Why HN Matters

A front-page Show HN post can drive 1,000-10,000 visitors in 24 hours. More importantly, HN attracts early adopters, technical decision-makers, and the kind of people who recommend tools to their organizations.

HN traffic converts differently from other sources — it's curious, skeptical, and if you earn their respect, deeply engaged. Some of the most successful SaaS companies got their first traction from Show HN posts.

The bar is high. The community is experienced and difficult to impress. But the upside is significant enough to be worth doing correctly.

How Show HN Works

"Show HN" is a specific submission type for projects you've built. The rules are simple:

Your post must start with "Show HN:"
It should be something you personally made
No upvote brigading, no gaming the system

Posts are ranked by upvotes, comments, and time — the algorithm is not public, but recent posts and engagement velocity matter. Your best window to gain traction is the first 2-4 hours.

The Show HN Title Formula

Your title determines your click-through rate. HN titles that work:

The anatomy of a strong Show HN title: Show HN: [Product] — [what it does in plain English]

Principles:

Be literal and specific. HN users don't respond to marketing language.
Lead with what it does, not what category it is
Include the key differentiator if it's genuinely interesting
No adjectives like "powerful," "amazing," "game-changing"
Under 80 characters ideally

Strong examples:

"Show HN: A CLI tool that converts any website to markdown"
"Show HN: AI writing tool that scores your draft against competitor content before publishing"
"Show HN: Open-source content calendar built for solo founders"

Weak examples:

"Show HN: The best AI writing platform" (too vague, too promotional)
"Show HN: FastWrite — revolutionary AI content marketing" (marketing speak)
"Show HN: I built a thing that helps you write content" (too vague)

Generate candidates:

Write 10 Show HN title options for [product].

Product: [description]
Key differentiator: [what makes it technically or practically interesting]
What it literally does: [plain English description]

Requirements:
- Start with "Show HN:"
- Under 80 characters
- Specific and literal
- No marketing adjectives
- The most interesting/unique aspect should be in the title

Pick the 3 best and explain what makes them more compelling than the others.

The HN Submission Body

HN submissions don't have body text in the traditional sense — you post a link and a title. But your first comment matters enormously. Post it immediately after submitting.

Your first comment should:

Explain what you built and why (1-2 paragraphs max)
Be honest about the stage you're at
Ask a specific question or invite specific feedback
Be written for an HN audience: technical, skeptical, curious

Write the first comment for my Show HN submission about [product].

This will be the first thing HN users see in the comments. It should:
- Explain what prompted me to build this (specific, honest)
- Describe what the product does and for whom (clear, jargon-free)
- Acknowledge the current state (beta, early, fully launched)
- Invite specific feedback (ask a question they'd actually want to answer)
- Be 150-250 words

Do NOT:
- Sound like a press release
- Use marketing language
- Make claims you can't back up
- Ask for upvotes (this is against HN rules)

Tone: honest founder talking to a curious technical community

HN Timing

Best time to submit: 8-10am US Eastern Time on a weekday. This catches both East Coast and West Coast US audiences during active hours, and gives European audiences time to see it before end of their day.

Avoid: Friday afternoons, weekends, US holidays. These produce lower engagement windows.

Day selection: Tuesday-Thursday is optimal. Monday people are catching up; Friday people are checking out.

Engaging with HN Comments

HN comment engagement is the most important variable you control.

Respond to every comment within 30 minutes during the first 4 hours. Comments beget comments — active threads stay visible longer and gain more upvotes.

How to respond well:

To skeptical comments: Take them seriously. If someone says "X already does this," don't get defensive — explain your differentiation specifically and honestly. If they're right, acknowledge it.

To critical comments: This is HN's most valuable signal. Thank them genuinely, explain your reasoning, and if they've identified a real problem, say so. Authentic engagement often turns critics into fans.

To technical questions: Answer in detail. HN audiences appreciate depth. This is not the place for marketing one-liners.

To supportive comments: A brief, genuine thank you. Then add something useful — a follow-up insight or invitation to try it.

Never:

Argue
Delete comments
Ask people to upvote
Respond defensively to criticism

The HN Mindset

HN users are:

Technically sophisticated (don't talk down to them)
Skeptical of marketing claims (be honest about limitations)
Interested in how things work (share technical decisions)
Responsive to authenticity (be a human, not a brand)
Annoyed by fluff (cut everything that's not essential)

The founders who do best on HN are the ones who show up as genuinely curious, honest about where they are, and respectful of the community's time.

Show HN vs. Ask HN

Show HN (recommended for product launches): "Here's something I built"

Ask HN (for feedback/validation before launching): "I'm thinking about building X — does this problem resonate with you?"

If you're very early (pre-product), Ask HN can generate valuable feedback. If you have something to show, use Show HN.

What to Do if Your Post Doesn't Get Traction

It happens. HN is competitive and timing-dependent.

Wait 6 months and try again. Most successful HN stories include multiple failed attempts. The community rotates, timing matters, and sometimes you just get unlucky.

Change the angle. The same product can be submitted with different titles that emphasize different aspects. What's the most technically interesting aspect of what you built?

Post something adjacent. A "how I built X" technical article often performs better than a product launch. If you write about the engineering decisions, performance optimizations, or architectural choices in your product, the technical depth attracts HN engagement.

Engage with other posts. Building karma and reputation on HN makes your future submissions more credible.

Post-HN: Converting Traffic to Signups

HN traffic arrives fast and curious. Your landing page needs to handle it:

Fast load time. HN visitors are not patient. Under 2 seconds.
Clear value proposition above the fold. They came from a technical description — your landing page should match that specificity.
Easy signup. Email + password only. Any friction here loses the HN visitor.
Technical credibility signals. If your product is technical, showing that you understand the domain matters.

Monitor your analytics in real-time during an HN post. Watch the signup rate by hour — this tells you whether your landing page is handling the traffic effectively.

Deliverable

Show HN title (3 candidates, with chosen option)
First comment written and ready to post immediately
Launch day monitoring plan (who's watching HN comments)
Analytics tracking for HN-sourced traffic and signups

What's Next

Move to Press and Creator Outreach — for earned media coverage beyond communities.