How to launch on Hacker News (Show HN) without flopping

By MentionLeads · July 16, 2026 · 6 min read

In short: A successful Show HN launch starts with something people can use, a literal title that explains what it does, and a first comment that gives technical context without pitching. Post when you can spend several hours answering questions, never coordinate votes, and judge the launch by conversations, qualified users, and product feedback—not whether you reach the front page.

How to launch on Hacker News is less about manufacturing a splash and more about making your work easy to inspect. Hacker News readers are unusually willing to test unfinished developer products, challenge architectural choices, and find edge cases, but they quickly reject vague positioning or promotional behavior. Treat Show HN as a live technical demo followed by a public founder interview.

What actually belongs in a Show HN launch?

The official Show HN guidance centers on something you made that people can try. A working tool, open-source project, interactive experiment, API, game, or technical prototype fits; a waitlist, funding announcement, blog post, or generic company homepage usually does not. If access requires an account, explain why and consider offering a demo, sandbox, sample output, or read-only path.

A rough product can work if its core behavior is real. “Early” is not an excuse for broken onboarding, missing documentation, or a page that never shows the product. Before posting, ask one person unfamiliar with the project to open the link and reach its useful moment without your help.

What should you prepare before submitting?

Prepare for scrutiny rather than a perfectly staged launch. Verify that the site works on mobile and desktop, error messages are understandable, the server can absorb a burst, and the pricing or license is visible. If your product touches source code, private data, or credentials, explain how those are stored and processed.

Keep a launch checklist that includes:

• A direct link to the usable product, repository, or demo
• A one-sentence explanation of the user and problem
• Test credentials or a no-signup path when practical
• Clear pricing, open-source license, and data-handling details
• Logging that distinguishes visits, activation, errors, and signups
• Enough availability to answer comments and repair obvious failures

Do not quietly change the core offer immediately before launching. Test the onboarding with a handful of users first; finding beta testers is cheaper than discovering a blocked signup flow in front of hundreds of technical readers.

When is the best time to post on Hacker News?

There is no reliably magical hour. Post when a meaningful portion of the Hacker News audience is active and, more importantly, when you can remain present for the next few hours. A theoretically optimal time is useless if questions sit unanswered while you sleep or attend meetings.

Avoid launching during an outage, migration, or another event that leaves you unable to fix problems. Consider the audience’s workday, but do not obsess over minute-level timing: submission quality, early discussion, and reader interest matter more than a copied scheduling formula. If the post does not catch, resist immediately resubmitting it.

How should you write the Show HN title?

Use the format “Show HN: Product – plain description of what it does.” A reader should understand the category and distinguishing behavior without recognizing your brand. For example, “Show HN: Patchwork – inspect API changes locally before deployment” is stronger than “Show HN: Patchwork, the future of API collaboration.”

Avoid superlatives, manufactured urgency, excessive capitalization, emoji, funding news, and claims such as “revolutionary.” Do not cram the full pitch into the title. HN titles may be edited for clarity, so write the straightforward version from the start.

What should the crucial first comment contain?

Post a founder comment immediately after submitting. The destination page demonstrates the product; the first comment explains why it exists, how it works, and where the interesting tradeoffs are. This gives readers material for a real discussion instead of forcing them to invent questions from a landing page.

A useful first comment covers:

• The concrete problem that caused you to build it
• Who it is for and what they currently use instead
• What is technically unusual or difficult about the implementation
• The product’s current limitations and unfinished areas
• Pricing, license, privacy, or hosting details likely to matter
• The kind of feedback you genuinely need

Write in the first person and disclose relevant interests. Acknowledging that a feature is incomplete builds more trust than disguising the limitation as a roadmap opportunity. The tone should resemble an engineering note, not launch copy.

How should you handle comments during the launch?

Reply promptly, but do not race to produce defensive answers. Address the specific question, admit uncertainty, and separate a bug from an intentional tradeoff. If someone reports a reproducible failure, thank them, investigate it, and update the thread when it is fixed.

Technical criticism is often the most valuable part of Show HN. Explain why you chose a database, model, protocol, or pricing structure, then say what evidence could change your mind. Do not turn every comment into a sales conversation, ask commenters to book calls, or repeat the same product pitch. For ongoing participation outside launch day, use a listening workflow such as finding relevant Hacker News discussions.

What gets a Show HN submission flagged or penalized?

Hacker News does not publish every ranking mechanism, so avoid confident theories about exactly why a post fell. Clear risks include asking for upvotes, coordinating votes through a team or community, creating accounts to support the submission, reposting too quickly, and behaving as though the discussion is a promotional channel.

A submission may also attract flags when the linked page is inaccessible, misleading, heavily gated, unrelated to something the submitter made, or presented with an inflated title. Sharing the launch link with existing users is not a license to request voting; if you notify people, ask them to try the product and give honest feedback elsewhere. Never tell them how to vote or comment.

How should you measure whether the launch worked?

Front-page placement is an outcome, not the business objective. Record referral traffic, successful activations, qualified signups, repository activity, documentation searches, errors, and the questions repeated in comments. Tag launch-day cohorts so you can later examine retention rather than confusing a traffic spike with durable adoption.

Also keep a decision log: which objections indicate missing positioning, which requests came from your actual buyer, and which ideas are interesting but outside the product. A launch with modest traffic can still clarify your startup positioning or produce several strong customer interviews.

Why is Hacker News traffic spiky but high-signal?

Visibility on Hacker News can rise and disappear within hours because the ranking and discussion move quickly. That makes the traffic operationally awkward: concurrent usage jumps, support arrives in clusters, and daily analytics can look impressive before returning to baseline.

The upside is concentration. For developer tools and technical infrastructure, visitors often understand implementation constraints, compare credible alternatives, and test the product immediately. Segment them carefully: curious engineers, potential users, contributors, buyers, and critics are not the same cohort. Follow up only when someone explicitly requests it or creates a normal product relationship.

Frequently asked questions

Can I launch on Show HN with a brand-new account?

Yes, but an account with no visible history gives readers little context and may make purely promotional behavior look worse. Participate honestly before launch because you find the community useful, not to farm a required amount of karma.

Should I ask friends or customers to upvote my Show HN?

No. Coordinated or requested voting undermines the ranking system and can hurt the submission. Ask trusted users to test the product before launch; after posting, let Hacker News readers decide whether the submission deserves attention.

Can I relaunch a product that previously flopped?

A materially improved product can sometimes justify a later Show HN, especially when there is a new capability people can actually use. Do not repost the same link with cosmetic wording after a weak result; wait until the product and story are genuinely different, and explain what changed.

Start here

• Write a literal “Show HN” title and a six-point first comment before launch day.
• Run the entire product flow as a new user, including signup, documentation, pricing, and error states.
• Choose a posting window when you can spend several uninterrupted hours answering questions and fixing defects.

To monitor relevant Hacker News conversations after the launch and prioritize high-intent discussions, use MentionLeads.