How to get a Show HN to actually work for your product

Show HN is one of the few channels where a solo founder can get direct, honest feedback from a technical audience and real traffic in the same 24-hour window. It's also a channel that most founders waste because they treat it like a press release rather than a conversation.

The mechanics matter, but the mindset matters more. Hacker News rewards genuine builders sharing real work. Anything that reads like marketing gets downvoted quickly.

Quick answer: Post Tuesday–Thursday between 8–10am ET, use the format "Show HN: [Product] – [plain-language description]" under 80 characters, and post your own top comment within the first few minutes covering what you built and what you want feedback on. Stay in the thread for the first 4–6 hours — that engagement window determines whether you surface or sink.

What makes a Show HN post succeed?

The posts that work share a few consistent traits. They're specific about what the product does and for whom. They include something the builder learned or found surprising — a technical challenge, a counterintuitive finding, a deliberate tradeoff. They acknowledge limitations honestly rather than hiding them.

The title format matters: "Show HN: [Product Name] – [What it does in plain language]". Keep it under 80 characters, no superlatives, no marketing language. "Show HN: I built a tool that monitors your SaaS metrics and alerts you to anomalies" beats "Show HN: The next-generation AI-powered analytics revolution for modern founders" every time. Hacker News users are technical and deeply allergic to hype.

The top comment also matters enormously. Post it yourself within the first few minutes. Two to three paragraphs covering what you built, why you built it, what you found hard, and what you want feedback on. This sets the tone for the whole thread and signals that you're there to engage.

When should you post a Show HN?

Timing affects your early vote velocity, which affects whether you surface in the top section long enough for organic engagement to kick in. The general consensus among founders who've done this multiple times: Tuesday, Wednesday, or Thursday between 8am and 10am Eastern US time. That's when the US technical audience is active and the HN homepage is moving fast enough to be interesting but not so fast that you scroll off in 30 minutes.

Avoid Mondays (everyone's catching up on email) and Fridays (everyone's winding down). Avoid major tech news days — if something significant just happened in the industry, the front page will be dominated by discussion posts and your Show HN will get less organic attention.

Don't post the same project twice without genuinely new substance. A "v2" post with meaningful new functionality is fine. Posting again because your first post didn't do well is the kind of thing HN regulars notice and downvote.

How do you handle the comments?

This is where most founders leave value on the table. You need to be in the thread for the first four to six hours, responding to every substantive comment. Not defensively, not with marketing copy — actually engaging with the questions and criticisms.

If someone points out a bug, acknowledge it and say you'll fix it. If someone challenges your approach, explain your reasoning and ask what they'd do differently. If someone misunderstands what the product does, clarify without making them feel stupid. The quality of your engagement in the thread affects how people perceive the product, and late-arriving users read the thread before they click your link.

The comments section is also free user research. The criticisms that sting most are usually the most actionable. Some of the best product pivots in indie SaaS history started with a HN comment that the founder initially disagreed with.

What do you do with the traffic after it arrives?

A good Show HN can drive a few hundred to a few thousand unique visitors over 24 to 48 hours. The conversion to signups is typically low — this is a technical audience kicking the tyres, not a buyer-intent audience. Your goal is to capture email addresses, make it trivially easy to sign up, and have a follow-up sequence ready.

Don't count on HN as a repeatable channel. It isn't. Most builders get one meaningful Show HN moment per product. Treat the traffic as a chance to get your first real users and real feedback, not as a scalable acquisition strategy. The lasting value is the Hacker News thread itself, which shows up in search results and signals legitimacy when investors, journalists, or potential users Google your product name.

---

Built something? Submit your product to LaunchBuff → — free listing + fortnightly tournament.

Frequently Asked Questions

Can I ask friends to upvote my Show HN? No — and beyond the ethical issue, it doesn't work reliably. HN has vote-ring detection and suspicious upvote patterns get flagged or penalised. Organic engagement from people who genuinely find the post interesting is what drives real results. Artificial boosts typically flatten out within an hour anyway.

What if my product isn't technical — will HN care? It depends on the product. HN's core audience is developers and technically-minded founders, so developer tools, infrastructure products, and anything that solves a problem they recognise personally get the most traction. Non-technical consumer products can still do well if the build story is interesting, but the audience fit is lower.

How long does Show HN traffic last? The primary spike is almost entirely in the first 24 hours. After that, traffic drops sharply. Some residual organic traffic comes from the HN thread appearing in search results over time, but don't plan on sustained traffic from a single post.

Should I launch on HN and Product Hunt on the same day? Most founders stagger them. Launching on both simultaneously splits your focus when you need to be fully engaged in both threads. HN first (smaller audience, higher quality feedback) is a common approach, with PH a day or two later once you've addressed the most obvious issues.