How to Get Early Users From Hacker News

Hacker News is the most concentrated source of technically sophisticated early adopters on the internet. A successful Show HN post can deliver hundreds of signups in a single day, from users who are predisposed to try new products, provide detailed feedback, and share tools they like with their networks.

It can also deliver brutal criticism that makes you question every decision you've ever made. The HN audience is sharp, skeptical, and allergic to marketing language. They'll dissect your product, challenge your assumptions, and call out any whiff of inauthenticity.

That's exactly what makes it valuable. The users you acquire from Hacker News are the highest-quality early adopters you'll find anywhere — if you know how to reach them.

This guide covers the complete Hacker News acquisition strategy: building credibility before you launch, crafting a Show HN post that resonates, handling comments, and converting HN traffic into retained users.

Understanding the Hacker News Audience

Before you post anything, understand who you're talking to:

Demographics:

Primarily software engineers, technical founders, and tech professionals
Skewed toward experienced developers (10+ years)
Mix of employees at big tech companies and indie/startup founders
Geographically concentrated in SF/Bay Area, NYC, and tech hubs globally, but increasingly distributed

Values:

Technical substance over marketing polish
Honesty and transparency (especially about limitations)
Simplicity and good engineering
Open source (not required, but respected)
Privacy and user respect

Allergies:

Marketing language ("revolutionary," "game-changing," "disruptive")
Vaporware or premature launches
Dark patterns or manipulative UX
Growth hacking tactics
AI hype without substance

Phase 1: Building Credibility (2-4 Weeks Before Launch)

The single biggest factor in Show HN success isn't your product — it's your HN account history. Posts from accounts with genuine participation history get more benefit of the doubt than posts from fresh or promotional accounts.

Commenting Strategy

Spend 15-20 minutes daily on HN for 2-4 weeks before your launch:

Where to comment:

Technical discussions related to your product's domain
"Ask HN" threads where you have relevant expertise
New product launches in your space (offer genuine, constructive feedback)
Threads about problems your product solves (don't mention your product yet)

How to comment:

Share specific technical knowledge or experience
Be concise — HN values density of insight over length
Disagree respectfully when you disagree (HN rewards intellectual honesty)
Share relevant links and resources (not your own)

What your comment history should look like by launch day:

30-50 thoughtful comments across various threads
Positive karma (aim for 200+, but quality matters more than quantity)
A visible pattern of expertise in your product's domain
Zero promotional comments

Submitting Non-Promotional Content

Before your Show HN, submit 2-3 interesting articles or resources to HN that are related to your product's domain but not about your product. This builds submission history and demonstrates your taste and interests.

Good submissions:

Technical blog posts about problems related to your space
Research papers or data relevant to your domain
Open-source tools or libraries you find useful
Interesting discussions from other platforms

Phase 2: Crafting Your Show HN Post

The Show HN format has specific conventions that affect how your post is received. Violating them triggers skepticism; following them earns goodwill.

The Title

Format: Show HN: [Product Name] – [Clear, honest description of what it does]

Good titles:

Show HN: Repomap – Visualize your Git repository's architecture
Show HN: Dataflow – SQL notebooks that run on your own infrastructure
Show HN: Briefcase – Encrypted file sharing without accounts

Bad titles:

Show HN: The Revolutionary AI Platform That Changes Everything (marketing language)
Show HN: We Built Something Amazing (vague, hyperbolic)
Show HN: [Product] – The #1 Tool for [Category] (claims without evidence)

Title principles:

State what it does, not why it matters
Be specific and concrete
Use technical terms if they're more precise
Avoid superlatives and claims

The Text (Self-Post Body)

Show HN posts can include text. Use it wisely — this is your chance to frame the conversation.

Recommended structure:

[1-2 sentences: What the product does and who it's for]

[1-2 sentences: The technical approach or what makes it interesting]

[1-2 sentences: Current status — what works, what's still in progress]

[1 sentence: What you'd like feedback on]

[Links: Product URL, demo/video if available, source code if applicable]

Example:

Dataflow lets you write SQL notebooks that run against your own
database infrastructure. Think Jupyter for SQL, but with version
control, scheduling, and team collaboration built in.

Built with Rust + WASM for the editor, with a thin Go backend
that proxies queries to your existing databases. No data leaves
your infrastructure.

Currently in beta with support for Postgres, MySQL, and BigQuery.
SQLite and DuckDB support is next.

Would love feedback on the editor UX and the collaboration model.
We're debating between real-time collaboration and async review
workflows.

Try it: https://dataflow.dev
Demo video: https://...
Source: https://github.com/...

What to include:

Technical details (what stack, what architecture)
Honest status (beta, alpha, v1 — whatever it actually is)
Specific feedback requests (gives people a reason to engage)
Demo or screenshots (HN users want to see the product, not read about it)

What to avoid:

Investor backing or funding amounts (feels braggy)
User counts or growth metrics (unless genuinely impressive)
Pricing details (save for the FAQ in comments)
Comparisons to well-known products (e.g., "like Notion but for X" — let users make those comparisons)

Phase 3: Timing and Launch

When to Post

HN traffic follows predictable patterns:

Best times:

Tuesday through Thursday
8:00-10:00 AM Eastern (5:00-7:00 AM Pacific)
This catches both US coasts during work hours

Avoid:

Weekends (lower traffic, smaller audience)
Monday mornings (posts get buried by the weekend backlog)
Friday afternoons (declining engagement)
Major tech news days (Apple events, big launches — your post will be drowned out)

The Launch Day Routine

Before posting:

Ensure your product is stable (HN traffic can be intense — make sure your server can handle it)
Have a teammate or friend ready to upvote (one genuine upvote, not a brigade)
Prepare answers for obvious questions (pricing, technical stack, comparison to competitors)
Set up analytics to track HN traffic separately

After posting:

Monitor the comments constantly for the first 2-3 hours
Respond to every comment within 30 minutes
Be in your product's analytics watching for bugs or crashes
Have a way to quickly deploy fixes if something breaks

Phase 4: Handling Comments

HN comments make or break your launch. The founder's responses in the thread often matter more than the product itself.

Types of Comments and How to Respond

Constructive criticism: "Your onboarding is confusing — I couldn't figure out how to create a new project."

Response: Thank them specifically. Explain why it works that way (if there's a reason) or acknowledge the issue and commit to fixing it. Never be defensive.

"You're right — we've heard this from a few users. The current flow assumes you know [context], which is a bad assumption. We're redesigning this next sprint. For now, the workaround is [specific steps]. Thanks for calling this out."

Technical questions: "How do you handle [specific technical challenge]?"

Response: Answer with technical depth. HN users appreciate thorough explanations. This is your chance to show engineering competence.

"Good question. We [detailed technical explanation]. The tradeoff is [honest discussion of limitations]. We chose this approach because [reasoning]. Open to suggestions if you've solved this differently."

Skeptical questions: "Why would I use this instead of [existing tool]?"

Response: Be honest about your differentiator. Don't trash competitors. Acknowledge where they're stronger and explain where you're different.

"[Existing tool] is great for [use case]. We're focused on [different use case] where [specific difference matters]. If you're primarily doing [thing competitor does well], they're probably the better choice. We're building for [specific audience/need]."

Negative comments: "This is just a wrapper around [API/model]. Why does this exist?"

Response: Don't get defensive. Explain the value you add beyond the underlying technology.

"Fair question. The raw [API/model] can do [basic thing], but getting it to consistently [your value-add] requires [engineering/UX/domain work]. We've built [specific components] to make this reliable and accessible for [specific audience]. But you're right that the underlying tech is [API/model] — we're transparent about that."

Trolling or bad-faith comments: Don't respond. Or respond with a brief, neutral acknowledgment. Never engage in arguments.

The Meta-Comment (Optional but Effective)

If your post gets significant traction, post a comment in your own thread:

OP here — really grateful for all the feedback. A few patterns I'm seeing:

1. [Common issue] — we're fixing this [timeframe]
2. [Common question] — the answer is [brief answer]
3. [Common request] — this is on our roadmap for [timeframe]

Keep the feedback coming. This is incredibly valuable.

This shows you're actively listening and synthesizing feedback.

Phase 5: Converting HN Traffic

HN sends a burst of high-quality traffic. Converting that traffic requires preparation.

Your Landing Page (HN Edition)

HN users have specific expectations:

Fast load time. If your page takes more than 2 seconds, they'll close it.
Clear value proposition. One sentence: what does this do?
Demo or screenshots above the fold. HN users want to see the product immediately.
Technical details available. Have a "how it works" section or blog post linked.
Transparent pricing. Hidden pricing frustrates technical users. If you don't have pricing yet, say so.
No dark patterns. No popups, no mandatory email capture, no cookie walls. These will get called out in the HN thread.

The Onboarding Funnel for HN Users

HN users are simultaneously more willing to try new products and less patient with friction. Optimize for:

Zero-friction signup. Email + password or GitHub OAuth. No multi-step wizards.
Immediate value. They should see a meaningful output within 2 minutes of signing up.
Self-serve exploration. HN users prefer to explore on their own before talking to anyone.
Documentation. Have basic docs ready. HN users will look for them.

Post-HN Follow-Up

The traffic spike from HN lasts 24-48 hours. After that, it drops to near-zero. Your job is to convert that spike into retained users.

For users who signed up but didn't activate: Send a follow-up email 24 hours later with a specific "getting started" path.

For users who activated: Send a personalized note from the founder within 48 hours.

For users who engaged in the HN thread: If someone left a great comment or question, DM them on HN (yes, HN has private messaging) with a personal thank-you.

What to Do After Your Show HN

If It Went Well (Front Page, 100+ Points)

Write a blog post about what you learned from the launch
Submit the blog post to HN a few weeks later (meta-posts about HN launches do well)
Follow up in the original thread with updates: "3 weeks after our Show HN, here's what we shipped based on your feedback"
Continue participating in HN discussions regularly

If It Didn't Get Traction (< 10 Points)

Don't panic. Many successful products had underwhelming first HN posts. Possible reasons:

Timing: You posted at the wrong time or got unlucky with competing stories
Title: It didn't communicate enough about what the product does
No demo: HN users want to see something, not read about it
Too early: The product wasn't ready for technical scrutiny

What to do: Wait 2-4 weeks, improve based on what you learned, and try again. HN allows re-posting if the first attempt didn't get meaningful traction.

If You Got Harsh Feedback

Take 24 hours before making any decisions. Then:

Separate valid criticism from noise
Prioritize the 3 most-mentioned issues
Fix them
Post an update in the thread showing the fixes

Nothing impresses the HN community more than a founder who ships fixes within days of feedback.

HN as an Ongoing Channel

Don't treat HN as a one-shot launch platform. It can be an ongoing acquisition channel:

Blog posts: Share technical blog posts about your domain (not product marketing)
Open-source contributions: If you open-source components of your product, submit them as Show HN
Feature launches: Major new features can warrant a new Show HN post
Community participation: Continue commenting and engaging. Your account builds credibility over time.

For complementary community strategies, read our guide on finding first users on Reddit and our comparison of Reddit vs. Twitter for startup marketing. For developer-specific content strategies, see content marketing for developer tools.

The HN Launch Checklist

Before you post:

[ ] HN account has 2+ weeks of genuine activity
[ ] Product is stable and can handle traffic spikes
[ ] Landing page loads fast and shows the product immediately
[ ] Demo or screenshots are ready
[ ] Title follows Show HN conventions (specific, honest, no hype)
[ ] Post body includes technical details and specific feedback requests
[ ] Answers prepared for predictable questions
[ ] Analytics set up to track HN traffic
[ ] You (or a co-founder) can monitor comments for the next 4-6 hours
[ ] Error monitoring is active so you catch crashes in real-time

For the full picture on getting your first 100 users across all channels, visit our complete guide to first 100 users.

Hacker News is the highest-concentration source of technical early adopters on the internet. A well-executed Show HN can deliver your first 50-200 users in a single day. But it requires preparation, authenticity, and thick skin. Build credibility before you launch, be honest about your product's state, respond to every comment with substance, and ship fixes fast. The HN community rewards builders who listen.