Hacker News Launch Guide

Hacker News is one of the highest‑leverage places to launch a developer‑focused or technical product. A single successful post can drive thousands of qualified visitors, thoughtful feedback from world‑class builders, and long‑term credibility for your startup. This Hacker News launch guide breaks down exactly how to prepare, post, and engage so you can maximize your chances of hitting the front page.

Note: For maximum launch impact, combine your HN launch with other platforms like Product Hunt, Reddit, and other product launch channels.

How Hacker News Works (In Practice)

Before you launch, get clear on how HN actually behaves:

• Front page is earned, not gamed: Upvotes matter, but so do early click‑through, time on page, and comment quality
• Titles are everything: Clear, honest, specific titles outperform clever or clickbait ones
• Show HN vs standard post: Use “Show HN: …” when you’re explicitly showing something you built
• Early momentum window: The first 30–60 minutes after posting determine whether you climb or disappear
• Culture first, promotion second: HN readers smell pure marketing instantly—lead with utility and honesty

Choose the Right Post Type

Hacker News has three main ways to launch. Picking the right one improves your odds and keeps you aligned with community expectations.

• Show HN: Best when you built something and can demo it today. Use this for dev tools, apps, or open source.
• Ask HN: Best when you want feedback before or during a build. Use it to validate positioning or collect use cases.
• Standard link post: Best when you have a blog post, research, or a detailed launch write-up that stands alone.

A quick decision rule:

• If the product is live and you want users, choose Show HN.
• If the product is early and you want guidance, choose Ask HN.
• If you have a deep technical write-up, a link post can work.

Getting Ready for a Hacker News Launch

Lock in the basics before you ever hit “submit”:

• Pick the right day and time: Weekdays, 9–11am Pacific time generally work best for Show HN posts
• Ship a fast landing page: Simple, fast, and focused on the problem you solve (HN readers care about clarity)
• Create a founder account you’ll keep: Use your real name; add a short, honest bio and website link
• Clarify your one‑sentence pitch: “We help [who] do [what] so they can [outcome]”
• Align your analytics: Make sure you can track HN traffic separately (UTM, dedicated page, or link)

Two-Week Pre-Launch Checklist

Use this as a step-by-step plan that removes last-minute chaos.

• Day -14 to -10: Read 20-30 recent Show HN posts. Note titles, top comments, and the landing page layout that gets the most praise.
• Day -9 to -7: Draft your HN title ideas (5-10). Build a short first comment. Test your landing page on desktop and mobile.
• Day -6 to -4: Ship a small, visible improvement that you can mention in the post (performance, new integration, or open-source release).
• Day -3 to -2: Ask a few trusted builders to review your post, your first comment, and your landing page for clarity.
• Day -1: Double-check analytics and error monitoring. Prepare a list of FAQs and honest limitations.

Landing Page Checklist for HN Readers

HN readers care about clarity, proof, and technical details. Your landing page should feel like a helpful README, not a glossy brochure.

• Above-the-fold clarity: One sentence on who it is for, one sentence on what it replaces or improves.
• Fast load and no popups: Anything that blocks reading kills trust.
• Product proof: 2-3 screenshots or a short demo video that shows real usage.
• Technical details: Stack, architecture choice, or a short “how it works” section.
• Founder presence: A short line like “Built by [name], former [role]” adds credibility.
• Single primary CTA: “Try it free” or “Request access” - not three competing buttons.

Example above-the-fold copy:

Debug API latency in minutes with a local trace viewer. Built for backend teams that need answers without vendor lock-in.

Crafting the Perfect HN Title and Description

Your title and first comment are your hook:

• Be specific, not clever: “Show HN: An open‑source error tracker for Kubernetes” beats “Show HN: My side project”
• Highlight what’s new or different: Is it open source, unusually fast, or built with an interesting constraint?
• Avoid marketing fluff: No emojis, no ALL CAPS, no vague buzzwords
• Use the description field wisely: One short sentence on who it’s for and what makes it interesting

Examples of strong Show HN titles:

• “Show HN: A SQL query debugger that explains slow queries in plain English”
• “Show HN: CLI tool that turns logs into searchable dashboards in 30 seconds”

Title and Description Patterns That Work

Use these patterns as templates and adapt them to your product:

• [Show HN: What it is] for [specific audience]
  “Show HN: A private S3 alternative for teams that ship weekly”
• [Show HN: Product] built for [constraint]
  “Show HN: A log explorer built to run on a single Raspberry Pi”
• [Show HN: Product] that replaces [painful workflow]
  “Show HN: A CI dashboard that replaces daily spreadsheet triage”

Visuals and Assets to Prepare

Even though HN is text-heavy, a few precise visuals improve understanding.

• A short GIF showing the core flow in 10-15 seconds
• 2-3 screenshots with annotations (what problem this screen solves)
• A tiny architecture diagram if the product is technical

What to Post in Your First Comment

HN readers expect a thoughtful founder comment at the top:

• Share your motivation: Why you built this and who it’s really for
• Call out limitations upfront: “This is an early beta, mobile is still rough”
• Describe the tech briefly: Stack, interesting implementation details, or constraints
• Invite specific feedback: “I’d love feedback on X and Y—especially from people doing Z”
• Link to documentation or demo: Make it easy to go deeper without hard selling

First Comment Template (Copy and Adapt)

Use this template to draft a focused, honest first comment:

Hi HN, I'm [name]. I built [product] because [problem you hit repeatedly].

What it does: [one sentence]
Who it's for: [specific audience]
How it works: [short technical detail or stack]
Current limitations: [1-2 honest caveats]

I'd love feedback on:
1) [question about positioning]
2) [question about feature or UX]

Demo/docs: [link]

Launch Day Playbook

On launch day, your job is to be present and useful:

• Post once, then let it breathe: Submit your post, then avoid refreshing every 10 seconds
• Reply to every good‑faith comment: Answer questions fully; thank people for bug reports
• Stay calm about critical feedback: HN can be blunt—treat critiques as free product reviews
• Share real numbers when possible: Uptime, performance metrics, or technical trade‑offs perform well
• Avoid obvious manipulation: Don’t ask for upvotes or coordinate fake accounts—HN moderators are strict

If you have friends or customers who use HN:

• Ask them to check it out and comment honestly, not “Please upvote”
• Encourage them to share what problem your product solved for them, not generic praise

Step-by-Step Launch Day Timeline

Use this hour-by-hour plan to stay focused without refreshing constantly.

• T-60 minutes: Open your post draft, first comment, and landing page in separate tabs. Confirm analytics and error tracking are live.
• T-15 minutes: Re-read your title. If it sounds like marketing copy, make it more specific.
• T-0: Submit the post, then publish your first comment within 2-5 minutes.
• T+10 minutes: Reply to the first question with full context. Early engagement sets the tone.
• T+30 minutes: Check for bugs or broken links. Fix any critical issue immediately.
• T+1 to 3 hours: Stay active in the thread, answer technical questions, and ask follow-up questions.
• T+4 to 8 hours: Summarize any key feedback in a new comment so late readers can catch up.

Comment Handling Playbook

How you respond matters more than how you launch. Use these patterns to keep the thread productive:

• If someone critiques your idea: Thank them, clarify assumptions, and ask what would change their mind.
• If someone finds a bug: Acknowledge fast, fix quickly, then reply with the fix or workaround.
• If someone asks about pricing: Be direct and explain your reasoning briefly.
• If someone dismisses the product: Stay calm. Ask for one concrete reason so you can learn.

Example response that builds trust:

Thanks for calling that out. You’re right that onboarding is slower than it should be. We’re shipping a simpler flow this week and I’d love to know if it fixes your pain.

Measuring Success Beyond the Front Page

Not every launch hits #1—but “small” launches can still be huge wins:

• Traffic quality: Time on page, signups, and activation rates from HN visitors
• Depth of feedback: Comments that reveal new use cases, objections, or edge cases
• Links and mentions: Blog posts, podcasts, or tweets that reference your HN thread
• Long‑tail traffic: Many HN posts continue to send traffic for months via search and archives

Simple HN launch metrics to track:

• Number of unique visitors from HN
• Signups / demos / waitlist joins from HN
• Comments and replies you received
• Bugs or insights that directly changed your roadmap

Case Study (Hypothetical): Dev Tool Launch

An early-stage API monitoring tool launched on HN with a tight title and a candid first comment. The founder shared a 20-second demo GIF and a short architecture note.

Results over 72 hours (illustrative):

• 5,200 visitors from HN
• 410 signups, 120 activated users
• 18 high-signal comments with specific feature requests
• 2 blog posts and 1 newsletter mention that drove long-tail traffic

What made it work:

• The title was specific to a narrow audience (backend teams)
• The first comment included limitations and invited feedback on one feature
• The landing page had proof and technical detail, not marketing fluff

Common Hacker News Launch Mistakes

Avoid these patterns that frequently backfire:

• Pure marketing pages: Overdesigned marketing sites with no substance or technical detail
• Ignoring comments for hours: Posting then disappearing reads as “drive‑by promotion”
• Arguing with every critic: Defend your work calmly; don’t be defensive or snarky
• Over‑engineering before launch: Spending months polishing instead of shipping something testable
• Posting at random times: Posting at 3am Pacific guarantees fewer eyeballs

Turning an HN Launch into a Growth Asset

Treat your HN post as the start of a flywheel, not a one‑day event:

• Add a “Featured on Hacker News” section or quote key comments on your landing page
• Turn the best questions and answers into a public FAQ or blog post
• Email your list with a recap: what you launched, what you learned, what’s next
• Reach out to people who left thoughtful comments and invite deeper conversations
• Use what you learned about positioning and messaging across every other launch channel

FAQ

What’s the best time to post a Show HN?

Weekdays, 9 to 11 AM Pacific. HN front-page traffic is heaviest from 9 AM to 5 PM Pacific, so posting at the start of that window gives you a full day of early engagement. Avoid weekends and US holidays, when the audience thins out and sessions run shorter.

Should I use Show HN, Ask HN, or a standard link post?

Use Show HN when the product is live and you want users: it’s built for dev tools, apps, and open source you can demo today. Use Ask HN when the product is early and you want feedback or positioning validation. Use a standard link post only when you have a deep technical write-up that stands on its own.

What should my first comment say?

Within 10 minutes of posting, share why you built it and who it’s for, describe the stack and an interesting implementation detail, call out one or two honest limitations, and invite specific feedback. On HN, an engineering-changelog tone with candid tradeoffs outperforms marketing copy by a wide margin.

Do I need to hit the front page for an HN launch to be worth it?

No. A launch that never hits #1 can still deliver high-signal feedback, long-tail search traffic for months, and links from blogs, podcasts, and newsletters. Track unique visitors, signups, comment depth, and the bugs or insights that change your roadmap, not just rank.

How do I avoid getting my Show HN penalized?

Don’t disguise marketing as a technical discussion, don’t ask for upvotes, and don’t coordinate fake accounts. HN moderators are strict and readers downvote vague hype fast. Lead with utility and honesty, answer tech questions with specifics, and never argue to win with critics.

The Short Version

• Hacker News rewards honest, specific, technically interesting products—not hype
• Your title, first comment, and responsiveness matter more than fancy design
• The first 30–60 minutes after posting decide whether you climb or disappear, so be present and useful
• A “small” launch can still deliver outsized impact if you capture and compound the feedback
• Treat your HN launch as an experiment you can run more than once, not a one‑shot event
• Build momentum before your HN launch by launching on a weekly product launch platform to gather early feedback and social proof

My take, as of 2026: on HN the title and your first maker comment do more work than anything on your landing page—write them like an engineer talking to peers, ship a fast page with no popups, and the upvotes follow the honesty.