Introduction
Hacker News (HN) remains one of the most powerful platforms for developer-focused products to gain traction, feedback, and early adoption. The platform attracts thousands of technical decision-makers, investors, and potential users daily. A successful “Show HN” launch can generate hundreds or thousands of qualified visitors, meaningful product feedback, and genuine early adopters—but poorly executed posts often get buried or flagged off the front page.
This guide covers practical, battle-tested strategies to increase your odds of success. Whether you’re launching a SaaS tool, open-source project, or indie product, these principles apply.
Before You Launch: The Preparation Phase
Have a Usable Product or Compelling Prototype
Hacker News communities appreciate authenticity. You don’t need a fully polished product, but users should be able to:
- Try it immediately: A live demo or accessible prototype is essential
- Understand the value in 30 seconds: Clear benefits without reading lengthy marketing copy
- Provide meaningful feedback: The product should be functional enough for real critique
Example: Instead of launching a “coming soon” page, have a working beta with 2–3 core features. Users on HN prefer substance over hype.
Craft a Compelling Title and Elevator Pitch
Your title is your first impression. HN titles should be:
- Clear and descriptive (avoid clickbait or vague language)
- Specific about the problem solved (not generic)
- Honest about stage/status (beta, MVP, side project)
Strong examples:
- “Show HN: Sidekick – A browser extension that surfaces relevant docs while you code”
- “Show HN: I built a local-first SQLite query builder to replace Postman”
- “Show HN: Filetree – Organize your codebase with a visual dependency graph”
Weak examples:
- “Show HN: The future of coding is here” (too vague)
- “Show HN: You won’t believe what we built” (clickbait)
- “Check out my awesome startup!” (too promotional)
Prepare Compelling Visuals and Demo Materials
HN readers are visual and impatient. Prepare:
- Demo video (30–60 seconds): Show the product in action, not slides
- High-quality screenshots: Highlight key features and user flows
- Animated GIF: A quick walkthrough of core functionality
- Live link: Ensure your demo URL doesn’t crash under traffic
Tools for demo creation:
Prepare Your First Comment (The Sales Pitch)
Your first comment is crucial. HN readers will scroll directly to it. Structure it as:
- Opening: A one-liner on what it is
- Problem: What problem does it solve?
- Solution: How is your approach different?
- Status: Beta/MVP/Alpha? What’s ready?
- Invite: “Ask me anything” or “Try it and let me know what you think”
Example first comment:
Hi! I built Sidekick to solve a problem I had constantly switching between my IDE and documentation. It’s a browser extension that surfaces relevant docs (MDN, Django, React, etc.) while you code, without leaving your editor.
It’s written in TypeScript with a Chrome manifest v3 backend. Currently supports JavaScript/TypeScript/Python. The extension is free for the first 500 users; I’m exploring a freemium model.
Try it here: [link]. Happy to answer questions about the architecture, monetization, or why I chose this approach over alternatives like Copilot.
Timing & Title Strategy: The Science of Getting Visibility
Optimal Submission Times
HN’s ranking algorithm rewards early upvotes and comments. Timing matters significantly:
Best times (US-centric, when HN traffic peaks):
- Tuesday–Thursday, 8–10 AM PT (11–1 PM ET): Peak traffic window
- Avoid Mondays (competition) and Fridays (people are checked out)
- Avoid weekends: Much lower traffic and engagement
Why timing matters:
- Posts submitted during peak hours accumulate upvotes faster
- Faster upvotes trigger the ranking algorithm, pushing posts higher
- Higher visibility = more comments = more discussion = stickiness on front page
Tools to help:
- Hacker News API to monitor submission timing
- Hacker News Submit page (set a reminder 15 minutes before)
Title Formula That Works
The best HN titles follow a predictable pattern:
Pattern:
Show HN: [Product Name] – [One-sentence value prop with optional detail]
Anatomy:
- “Show HN”: Signals this is your own work (algorithm-favored)
- Product Name: Clear, memorable
- Value prop: Specific benefit or use case
- Optional detail: Pricing, unique tech, or standout feature
Real examples from successful launches:
- “Show HN: Replicate – An open-source CDC platform for syncing databases”
- “Show HN: Codemod – Automate large-scale codebase refactors”
- “Show HN: ORCA – A tool to visualize your codebase as a 3D graph”
Title testing:
- Ask 3–5 friends: Can they explain what it does in one sentence?
- If not, simplify further
Pre-Launch Preparation Checklist
Before you hit submit, ensure:
- Product link is fast and doesn’t crash under load (test with ab or wrk)
- Demo is under 60 seconds; include captions for sound-off viewing
- Uptime monitoring active (PagerDuty, Pingdom)
- Database backups in place (expect traffic spikes)
- First comment drafted and ready to post immediately
- 10–20 friends/colleagues lined up to engage (first comments, questions)
- You’re available for 24–48 hours to respond to comments
- Marketing/analytics tracking set up (Segment, Plausible, or Mixpanel)
Engagement Tactics: Building Momentum
The First 2 Hours Are Critical
After submission, your post needs early engagement to signal quality to the algorithm:
What to do:
- Post your first comment immediately (within 5 minutes of submission)
- Alert your community: Ping 10–20 trusted people via email/Slack to engage (don’t ask for upvotes; ask them to try it and comment honestly)
- Monitor actively: Refresh every 10–15 minutes for the first hour
- Respond quickly: Answer the first 5–10 comments within 30 minutes
Why early engagement matters:
- The ranking algorithm heavily weights early velocity
- Early visibility gets more eyes, which triggers more organic upvotes
- Substantive early comments signal quality to lurkers
Being Present for 24–48 Hours
Successful launches require active participation:
What founders should do:
- Answer every question: Even hostile ones; professionalism wins
- Admit limitations: “We haven’t solved X yet, but it’s on the roadmap” builds trust
- Provide context: Explain technical tradeoffs (why Rust vs Go? Why Postgres vs MongoDB?)
- Share behind-the-scenes stories: “I built this over 6 weeks because…”
- Engage deeply: Not one-word replies; thoughtful 2–3 sentence responses
Engagement patterns that work:
- User asks: “How is this different from [competitor]?”
- Good response: “Great question. Unlike Competitor X, we optimize for [specific tradeoff]. This means you get A and B, but lose C. For our users, that tradeoff was worth it because…”
- Bad response: “We’re way better” or no response
Leverage Your Network Wisely
Don’t ask for upvotes; ask for engagement:
Email to friends:
Hey! I’m launching [Product] on Hacker News tomorrow at 9 AM PT. Would love if you could try it and share honest feedback in the HN thread. If you use it, comment about what you’d actually use it for.
What not to do:
- “Please upvote this”
- “Share this everywhere”
- Coordinate off-platform brigades (HN flags/removes these)
What To Avoid: Common Launch Mistakes
Mistake #1: Spammy or Misleading Titles
❌ “Show HN: The best developer tool ever built” ❌ “Show HN: This will change how you code” ✅ “Show HN: Sidekick – Autocomplete suggestions from your docs”
Mistake #2: Asking for Upvotes
❌ “Please upvote if this resonates” ❌ “Help us reach the front page” ✅ Let the quality speak for itself; HN flags these posts
Mistake #3: Aggressive Monetization Messaging
❌ “Buy now, 50% off launch discount!” ❌ “Sign up for our premium plan” ✅ “Free for the first 30 days; we’re exploring a freemium model”
Mistake #4: Low-Effort Engagement
❌ Posting your link without a substantive first comment ❌ One-word replies to questions ❌ Disappearing after the first 12 hours ✅ Thoughtful, helpful responses showing you built something you care about
Mistake #5: Overloading the Post with Features
❌ “We support 47 programming languages, 12 frameworks, and 99 data sources” ✅ “Core feature: X. Nice-to-haves: Y, Z. Future: A, B”
Post-Launch: Measure & Follow Up
Key Metrics to Track
Set up analytics before launch to measure:
- Traffic: Visitors, page views, session duration
- Conversion: Signups, demo starts, GitHub stars
- Engagement: Comments, upvotes, reach
- Sources: HN referrer attribution
Analytics tools:
- Plausible (privacy-friendly, minimal setup)
- Fathom Analytics (lightweight)
- Segment (powerful for events)
The 24–48 Hour Window
- Track upvotes and rank: Note when you hit #1, top 5, top 10
- Log notable comments and feature requests
- Identify patterns in user questions
Response and Bug Fixes
- Within 24 hours: Fix any obvious bugs reported in comments
- Within 48 hours: Publish a brief update (e.g., “Bug fix: improved performance on large datasets”)
- Tag the update in HN comments: “Quick update: We just pushed a fix for X. Thanks @user for reporting it”
Long-Term Follow-Up
- Week 1: Reach out to interesting commenters for deeper conversations
- Week 2–4: Publish a follow-up post on dev.to or Medium: “500 HN Users Tried Our Product. Here’s What We Learned”
- Month 2: Share early traction: “We hit 1K signups from HN. Here’s our growth breakdown”
Examples and Case Studies
Case Study #1: Sidekick (Successful Launch)
Title: “Show HN: Sidekick – A browser extension that surfaces relevant docs” Result: 487 upvotes, 120+ comments, 2K signups in 48 hours
What worked:
- Solved a specific, relatable pain point (context switching)
- Live demo video showing before/after
- Founder answered 100+ questions personally
- Acknowledged limitations: “Works best for JS/TS; Python support coming in v2”
Case Study #2: Codemod (Viral Launch)
Title: “Show HN: Codemod – Automate large-scale codebase refactors” Result: 623 upvotes, front page for 2 days, 10K+ GitHub stars
What worked:
- Solved a painful problem (large migrations)
- Open-source from day one (GitHub link, not SaaS)
- Technical depth: Founder explained the AST parser design
- Timing: Submitted Tuesday 9 AM PT during holiday lull (less competition)
Case Study #3: Failed Launch (Lessons Learned)
Title: “Show HN: Revolutionary AI coding assistant” Result: 12 upvotes, flagged, buried
What went wrong:
- Vague, overhyped title
- No first comment; just a link
- Product required login (friction)
- Founder didn’t engage in comments
Final Thoughts and Action Plan
Launching on Hacker News is a mixture of preparation, timing, and genuine community engagement. The formula is:
- Build something real: Solve a problem you or your network has
- Pick the right time: Tuesday–Thursday, 8–10 AM PT
- Craft a clear title: Specific, honest, valuable
- Engage authentically: Answer questions, admit limitations, show you care
- Measure and iterate: Track what worked; apply lessons to next launch
The HN community rewards authenticity, transparency, and substantive technical discussion. If you show up with a real product, a respectful pitch, and a willingness to engage thoughtfully for 48 hours, you’ll likely generate useful feedback and motivated early users—regardless of upvote count.
Bonus Resources
Guides & Tools:
- Hacker News Startup Playbook by Hackers and Slackers
- Show HN Guidelines (official HN guide)
- YC Startup School (free founder resources)
Analytics & Monitoring:
- Hacker News API
- HN Search (find similar launches)
- StatusPage.io (uptime monitoring)
Design & Demo:
Action: Launch Checklist
- Product is live and handles traffic
- Title is clear, specific, and tested with 3+ people
- First comment is drafted and ready
- Demo video/screenshots are polished
- 15 people lined up to try and comment
- Analytics tracking is active
- You’ve blocked 24–48 hours for engagement
- You’re ready to answer tough questions honestly
- Launch scheduled for Tuesday–Thursday, 8–10 AM PT
Next step: Pick your launch date, set a reminder, and prepare your post. Good luck! 🚀
Comments