How to Post a Show HN for Your SaaS

Show HN is the section of Hacker News where people share things they have built. A good Show HN post can bring thoughtful feedback, early users and attention from a technical audience that rarely responds to ads. A poorly prepared one can sink without a trace or attract a wave of blunt criticism. If you plan to launch on Hacker News with a Show HN, it pays to understand the community before you post.

Hacker News has a distinct culture. Success there depends less on marketing polish and more on genuine interest, technical substance and honest engagement. This guide covers how to decide whether your product fits, how to prepare, how to write the title and first comment, and how to handle the discussion that follows.

Is your product a good fit?

Show HN works best for products that people can try easily, without a long signup form or a sales call. It favors products with technical depth or an interesting approach, such as an unusual architecture, a clever use of an existing technology or an open-source core. The audience is mostly developers, founders, engineers and other technical people, so products that appeal to them have a natural advantage. And it rewards products that solve a problem in a new way or execute an existing idea unusually well.

If your product requires a demo request before anyone can use it, Show HN is likely the wrong channel. Readers want to click a link and try the thing. Similarly, if you serve a non-technical niche, such as a scheduling tool for dental practices, the audience may simply not care, however good the product is. That doesn't mean you can never post. A story about the technical decisions behind a niche product can still interest readers. But be honest with yourself about whether the people reading will want to use it.

Read the rules first

Hacker News publishes guidelines for Show HN posts, and you should read them before you post. The details change occasionally, but the core expectations are consistent. A Show HN should be something people can try, not a landing page with an email signup or a blog post about a product. You shouldn't ask friends or colleagues to upvote or comment, and the community and moderators are good at spotting coordinated activity. Marketing language is unwelcome. And the community expects you to engage genuinely with the people who comment.

Breaking these rules can lead to your post being flagged or your account being penalized. More importantly, it signals to readers that you see the community as a promotion channel rather than a group of people whose opinion you value, and that impression is hard to reverse.

Prepare your product

Make it easy to try. A free trial without a credit card, a demo account with sample data or an interactive demo that works without signing up all lower the barrier. Every field on a signup form loses some readers. If your product needs data to be useful, provide a sample dataset so people can see it working immediately.

Fix obvious bugs before you post. Hacker News readers will find them, and they will mention them in the comments where everyone else can see. Walk through the main flows yourself on a fresh account, on different browsers and on mobile.

Make sure your site loads quickly and can handle a traffic spike. A post that reaches the front page can send a surge of visitors in a short time, and a site that falls over turns your launch into a thread about why your site is down. Check your hosting, caching and any rate limits on third-party services you depend on.

Prepare documentation. Technical readers will ask how things work, what the API looks like, how data is stored and what the limits are. Having clear docs to link to makes your replies faster and more credible.

Write the title

Show HN titles follow a simple format.

Show HN: [Product name] – [what it does in plain language]

A title like "Show HN: Logly – Self-hosted log search for small teams" works because a reader immediately knows what the product is and who it's for. Some founders write a first-person version, such as "Show HN: I built a SQL-based alternative to spreadsheets for finance teams," which can feel more personal and invite curiosity about the story.

Avoid hype words such as revolutionary, game-changing or the best. Plain, specific titles do better because they respect the reader's time and because the community is skeptical of superlatives. Describe what the product does, not how you feel about it.

Write the first comment

Post a comment as soon as you submit. This comment is your chance to give context, and readers often look for it before deciding whether to engage. Explain who you are and what you built. Describe why you built it, ideally through the specific problem you or your team ran into. If the technical approach is interesting, explain how it works. Say what is different from existing tools, and be fair to those tools, since readers will know them. End by saying what kind of feedback you want.

Keep the tone honest and conversational. Hacker News readers appreciate stories about the problem, the technical decisions and the lessons learned along the way. A comment that explains you tried three approaches before settling on the current one, and why, will draw more thoughtful replies than a polished summary of features. If the product is early, say so. Readers are more forgiving of rough edges when the founder is upfront about them.

When to post

Many people post on weekday mornings US time, when traffic is high. There is no guaranteed best time, and competition varies from day to day. A day with several popular posts can push yours down quickly, while a quieter day can give it more room. Pick a time when you and anyone helping you can be available for several hours, because the hours after posting matter most.

Engage with comments

Engagement is the most important part of a Show HN. Reply quickly to questions and feedback, especially in the first few hours when the post is most visible. Be humble and open to criticism. When someone asks about a technical decision, explain it clearly, including the trade-offs you accepted. Acknowledge limitations honestly. If the product doesn't support something, say so and explain whether it's planned.

Avoid defensive replies, even to harsh comments. A defensive response is visible to every reader and often draws more criticism. A calm reply that acknowledges the point, explains your reasoning and thanks the commenter tends to earn respect, even from people who disagree. Thoughtful engagement usually leads to better discussion and more interest in the product, because readers see a founder who listens.

Handle criticism

Hacker News comments can be blunt. Common criticisms include pricing, privacy, comparisons to existing tools, the choice of technology stack and doubts about whether the problem is real. Treat each as feedback. Thank people who give detailed responses, since they spent real time on your product. Clarify misunderstandings politely. If someone thinks your product sends data to a third party and it doesn't, explain how it works. Note useful suggestions and say you're considering them.

Pricing criticism deserves particular care. Technical readers often compare a paid product with what they could build themselves in a weekend, or with an open-source tool that does part of the job. Arguing that they couldn't build it rarely helps. Explaining what the price covers, such as hosting, maintenance, support or the features that took the longest to get right, gives a more useful answer. If several people raise the same pricing concern, treat it as a signal worth investigating after the launch rather than something to defend in the thread.

Some criticism will be unfair or uninformed. You don't need to win every argument. A short, polite reply, or no reply at all for comments that are simply hostile, is often the right choice. Readers can tell the difference between a founder who engages with substance and one who argues for the sake of it.

Track results

Set up tracking before you post so you can see visitors from Hacker News, signups and trial starts, and how many of those users activate in the following days. Keep a record of feedback themes from the comments.

Hacker News traffic can be large but may not match your target customer. Many visitors will be curious engineers who have no intention of buying, which is fine. Focus on activation and meaningful feedback rather than raw visits. A post that brings fewer visitors but several detailed conversations with people in your target market may be more valuable than one that tops the front page and produces nothing lasting.

After posting

Follow up with new users through your onboarding emails, and consider a short personal note to those who signed up from the post. Fix issues raised in the comments, and if you fix something a commenter pointed out, reply in the thread to let them know. It shows you listened and often prompts them to try the product again. Write a short recap of what you learned, which can be useful content and a record for the next launch. Thank commenters who gave thoughtful feedback.

Reposting

If your first post didn't get traction, check the guidelines on reposting before trying again. A significant update can justify a new Show HN later, especially if it addresses feedback from the first post. Avoid repeatedly posting the same thing in the hope of a better result, which annoys the community and can lead to penalties.

Common mistakes

The most frequent mistakes are predictable. Marketing language in the title or comments puts readers off immediately. Asking for upvotes breaks the rules and tends to be noticed. Posting a product that's hard to try, such as one that requires a sales call, gives readers nothing to engage with. Ignoring comments after posting wastes the most valuable part of the launch. And arguing with critics turns a useful discussion into a thread about the founder's temper.

The takeaway

A successful Show HN is a conversation with a technical community, not a promotion. Make the product easy to try, write a plain title and an honest first comment, and set aside time to engage thoughtfully with every reply. Judge the result by the feedback you gather and the users who stick around, not by whether the post reaches the front page. Treat it that way and you will learn a great deal, even from a post that gets modest attention.