Show HN Launch: Getting Feedback the Right Way

Hacker News's community is unusually skilled at detecting a post that's trying to market at them rather than talk to them, and the site's guidelines and unofficial norms both reflect that — Show HN exists specifically as a space for builders to share real projects with other technically-minded people, not as a free marketing channel, and posts that treat it as the latter tend to get flagged, downvoted, or quietly buried before they ever reach the front page.

The launch mechanics below get a day of attention on the thread itself. What's worth planning for before the post even goes up is Hacker News mention tracking for the conversation after it spreads — a Show HN post that gets any real traction rarely stays contained to the original thread.

What Show HN actually is, and what it isn't

Show HN is a labeled post type for sharing something you made — software, a hardware project, a writeup of something you built — posted directly by the builder, with a brief first comment explaining what it is and why you built it. It isn't a press release format, and it isn't meant for pure announcements without a working thing behind them; historically, Hacker News has preferred Show HN posts to link to something a visitor can actually try, not just a landing page describing a future product.

Writing a title and first comment that won't get flagged

• Describe what it does plainly in the title — "Show HN: a tool that converts CSV files to SQL schemas" reads as legitimate; a title built around a tagline or a vague value proposition reads as marketing copy.
• Skip superlatives entirely — "fastest," "best," "revolutionary" are reliable signals to this specific audience that a post is marketing-driven rather than builder-driven, regardless of whether the claim happens to be true.
• Write the first comment yourself, as the builder, explaining what problem you were solving, what's technically interesting about how you built it, and what's still rough or unfinished. Hacker News readers respond well to genuine technical detail and visible humility about a project's current limitations.
• Never ask for upvotes, anywhere — not in the post, not in a comment, not in a message to friends asking them to go upvote. Coordinated or asked-for voting is against Hacker News's guidelines and is actively detected by the site's ranking system, which can suppress or remove a post entirely once a pattern like that is flagged.

Timing a Show HN post

Hacker News traffic follows a daily and weekly rhythm — weekday mornings in US time zones tend to see more active browsing than weekends, though this shifts over time and shouldn't be treated as a fixed rule. Beyond timing for traffic, the more important timing question is product readiness: post when there's something real to try, not when a calendar date happens to be convenient. A broken link, a confusing signup flow, or a demo that doesn't actually work gets noticed within minutes by this specific audience, and a bad first impression here tends to be remembered longer than on a more forgiving platform.

Who should actually post it

Unlike Product Hunt, where teams sometimes look for an established community member to post on their behalf, Show HN works best coming directly from whoever actually built the thing. A founder or engineer posting their own project reads as exactly what Show HN is for; a marketing or growth hire posting on behalf of a technical founder tends to read slightly off, and commenters are quick to ask pointed technical questions that someone outside the build process may struggle to answer convincingly in the thread.

A fictional example of a post that worked

A two-person team building a small developer tool called Northbound — a command-line utility for diffing API responses — posted a Show HN with a plain, literal title describing exactly what the tool did, no tagline attached. The first comment, written by one of the two founders, explained the specific debugging problem that led them to build it, named the two existing tools they'd tried and found insufficient, and openly noted a few rough edges still being worked on. Early comments asked pointed technical questions about edge cases in diffing nested JSON, and the founder answered each one directly and specifically rather than deflecting to documentation. The post never reached the very top of the front page, but it generated enough genuine technical discussion that several commenters became actual users within the week — a smaller but more durable outcome than a higher ranking with shallower engagement would have produced.

Handling comments, including the critical ones

Hacker News comment sections are known for blunt, sometimes harsh technical criticism, and the single biggest mistake builders make after posting is being thin-skinned about it in replies. A calm, specific, non-defensive response to a critical comment — engaging with the actual technical point rather than the tone — tends to read well even to onlookers who weren't going to use the product anyway. Arguing with a critic, or responding to feedback with visible frustration, tends to do more damage to how the whole thread reads than the original criticism did.

What happens after the post: tracking where the conversation spreads

A Show HN post that gets any real traction rarely stays contained to the thread itself — it gets quoted on Twitter/X, cross-posted to relevant subreddits, and sometimes picked up by a newsletter or aggregator within the same day. Catching that spread as it happens, rather than scrambling to find the conversation after it's already moved on, means you see follow-up questions and criticism wherever they end up rather than only in the original thread.

Set up the tracking before the post goes up, not after. The first twenty-four hours after a successful Show HN post tend to produce most of the secondary conversation, and checking manually across several platforms during that window is exactly the kind of task that's easy to miss while you're also busy replying to comments on the original thread itself.

This matters more in the days immediately after a launch than it does later, since early momentum on a related subreddit thread or a quote-tweet can drive a meaningful second wave of visitors well after the original Hacker News post has scrolled off the front page.

From launch-day attention to the feedback that actually compounds

The launch mechanics above get people to look at your product for a day. What determines whether that attention turns into anything lasting is what happens with the people who actually sign up afterward — specifically, collecting honest feedback and reviews from that first wave of users the same way you would from any other cohort, rather than treating launch-day traffic as a one-time spike to maximize and move on from. Asking every new signup from that wave for feedback on the same schedule you'd use for any other new customer, without singling out the ones who seemed most enthusiastic in the Hacker News thread, keeps the same no-gating principle intact even in the excitement of a launch.

If you're planning a broader launch sequence rather than a single Show HN post, our guide on launching on Product Hunt covers a different platform with its own norms and timing, which some SaaS teams run in combination with a Hacker News post rather than choosing one over the other.

Can I ask my team or friends to upvote my Show HN post?

No. Asking anyone to vote, even privately, is against Hacker News's guidelines and risks the post being flagged, removed, or having the account associated with it penalized. Genuine organic engagement, even if slower to build, is the only approach that holds up under the platform's own scrutiny.

What if my Show HN post gets flagged?

A flagged post typically drops out of visible rankings, and there's no guaranteed way to reverse that once it happens. The best prevention is avoiding the patterns that trigger flags in the first place — promotional language, asked-for votes, or a post that reads as an announcement rather than a genuine share from the builder.

Should I post on Show HN before or after a Product Hunt launch?

There's no universally correct order — some teams spread the two out by a few weeks to get two separate waves of attention rather than splitting one audience's attention across both platforms on the same day. The right choice depends more on which audience matters more for your specific product than on a fixed sequencing rule.

Every review from the App Store, Google Play, G2 and Capterra in one inbox → Try Tailwind free.

Tailwind runs $5 a month per tool, or $50 a month for the Full plan covering everything, with the first month free and no card required to start.