How to Get Your SaaS Featured on Hacker News

Hacker News is one of the highest-leverage launch channels available to a technical founder, and also one of the least forgiving. The audience is sharp, skeptical of anything that reads as marketing, and the ranking algorithm punishes a slow start almost as hard as Reddit's does. A genuinely good product posted the wrong way can sit at zero points and vanish within the hour. Here's what actually works.

What Hacker News actually rewards

Three things, consistently: genuine novelty or technical interest, transparency about what the thing is and who built it, and a founder who's visibly present in the comments answering questions honestly, including the hard ones. A post missing any of these three tends to underperform regardless of how good the underlying product is.

Show HN vs a regular submission

Show HN is the specific format for "I built this, here it is." It gets its own section of the site and a somewhat more forgiving read from the community, since everyone clicking in already knows it's a founder's own post. A regular submission (just a link, no "Show HN" prefix) works better for content about your product, a technical writeup, a genuinely interesting blog post, rather than the product announcement itself. Most first launches should use Show HN; save plain submissions for follow-up content once the product exists.

Writing the post itself

• Title: plain, specific, no hype. "Show HN: I built a tool that does X" beats anything with adjectives like "revolutionary" or "game-changing." Hacker News's culture actively penalizes hype language, it reads as compensating for something thin underneath.
• Lead with what it does, not why it matters. State the mechanism plainly in the first sentence. Save the backstory and motivation for after the technical substance, not before it.
• Include genuine technical detail if there's any to include. Hacker News's audience specifically rewards posts that explain an interesting technical decision or trade-off, not just the end-user pitch. If there's something genuinely interesting about how you built it, that's often more compelling to this audience than the product's business case.
• Disclose who you are, briefly. "I built this" or "founder here" up front. Evasion about authorship, once discovered (and it usually is), does more damage than the original post could have earned in upvotes.

Timing

Hacker News's ranking, like Reddit's, weights early velocity heavily. Weekday mornings, U.S. Eastern time, tend to perform best, since that overlaps both US morning traffic and the tail end of the workday in Europe. Avoid weekends, when both traffic and the kind of attentive, technical readership this format needs are thinner. See best time to post on Reddit for the same underlying mechanic applied to a different platform, since the logic (early votes compound, late ones don't) is structurally similar across both.

What happens after it's posted matters more than the post itself

A founder who disappears after submitting rarely does well. The comments section is where a Hacker News launch actually gets won or lost: respond to every substantive question, concede genuine limitations honestly rather than deflecting, and never argue defensively with a critical comment. A critical but accurate comment, acknowledged gracefully, tends to read better to onlookers than a flawless post with no engagement at all.

The mistakes that bury a post fast

• Vote manipulation, or anything that looks like it. Asking friends to upvote, using multiple accounts, or any coordinated voting pattern gets detected by Hacker News's own systems and can get a post or account penalized, sometimes without obvious explanation, which is exactly why it's not worth the risk even once.
• Marketing language in the post or the comments. This audience is unusually good at identifying a pitch dressed as a technical post, and calling it out publicly once identified.
• A landing page that doesn't match the post's claims. Overselling in the post and underdelivering on click-through is one of the fastest ways to tank a thread's momentum, since early commenters who bounce off a mismatched landing page say so.
• Posting the same product repeatedly in a short window. A failed launch is usually better relaunched after genuine changes and some time, not resubmitted hoping for a different outcome the next day.

What a Hacker News launch is actually good for

Realistic expectations: a successful Show HN produces a real spike in traffic and often some of the most technically substantive feedback you'll get anywhere, including from people who read your actual code or architecture closely enough to find real gaps. It's less reliable as a pure customer-acquisition channel for non-technical products, and like most launch-day channels, the traffic mostly stops the day the post drops off the front page. See where to launch your startup online for how it compares to Product Hunt, Reddit, and other launch channels, and what to do for the months after launch day that a spike alone doesn't cover.

Hacker News and Reddit draw a genuinely overlapping, technically literate audience, so a good Show HN post is often worth cross-referencing against the Reddit threads where the same kind of person is already asking for what you built. ThreadyGo surfaces those Reddit conversations continuously, so the launch-day spike has something ongoing to feed into afterward. Try it for $9 to see it against your own product.