Launching Your SaaS on Hacker News

You finally shipped the thing. Someone in a group chat says "just post it to Hacker News." So you picture the front page, a flood of signups, a comment thread full of people telling you it is exactly what they needed. What actually tends to happen for most posts is quieter: you submit a Show HN, it sits on the new page for a while, gets a couple of votes, and slides off without ever reaching the front page. And on the rare day it does hit, the traffic spike is real but so are the comments, and some of them are blunt in a way that stings if you were expecting applause.

Both outcomes are normal. Hacker News is a genuine channel with a specific audience and specific habits, and a post there is a single event, not a plan. This guide is about running that event with your eyes open: what HN traffic is honestly worth, how to post in a way the community respects, how to handle the harsh feedback, and why one good day there belongs inside a wider distribution mix rather than carrying your whole launch.

Where does the money actually come from?#

Hacker News does not pay you. There is no revenue share for hitting the front page. Any money that eventually arrives comes through a long chain that starts with a spike of traffic and ends, weeks later, with someone deciding your tool is worth paying for. Most of the value is not the sales you make on the day. It is the qualified audience and the feedback you collect while the spike is happening.

Show HN post goes live on the new page
        |
        v
Most posts stall here and quietly slide off
        |
        +--> (rarely) votes and comments push it to the front page
        |
        v
Front page: sharp spike of technical, skeptical traffic
        |
        +--> a few try it and one or two might pay now
        |
        v
The rest you capture: email signup or free account
        |
        v
Plus a pile of blunt, useful feedback in the comments
        |
        v
You follow up and fix things over the next weeks
        |
        +--> some warm up and convert later
        |
        v
A smaller, slower stream of revenue after the spike

Notice where the value actually sits. A tiny slice of the spike converts on the day. A bigger slice is the emails and free accounts you collect, which you can nurture into customers later. And a third kind of value is not revenue at all: comments from technically sharp people who will tell you exactly what is confusing, missing, or already done better elsewhere. That feedback is worth real money if you act on it, because it comes from your buyer. If the idea of a channel earning through a chain of steps rather than one click is new, where does online money come from covers the general shape.

The reason direct sales are thin is worth sitting with. The HN crowd is unusually good at evaluating tools and unusually likely to think "I could build that in a weekend," and many are already using an alternative or building something adjacent. Plan around that instead of being surprised by it.

How it actually works#

A submission starts on the new page, where fresh posts wait for early votes. If a handful of people upvote it quickly and nobody flags it, it can climb toward the front page, where the real traffic lives. Most posts never make that jump, there is a large element of timing and luck, and you cannot buy your way up. So give it your best shot and accept the base rate.

For a product, the format is Show HN. You title it "Show HN:" followed by a plain description of what the thing is. That prefix tells the community you made something and want them to look, which sets the right expectations. The title should say what the product does in plain language, not sell it. "Show HN: A tool that turns API docs into a typed client library" works. "Show HN: The revolutionary AI platform that 10x's your workflow" gets you downvoted and mocked, because marketing voice is exactly what this audience is allergic to.

The body, and your first comment, are where you tell the honest story. As the maker you post a comment introducing yourself, what you built, why, what stack it runs on, and what is still rough. HN respects candor and technical detail. Say what it does not do yet, mention the hard part you solved, and invite specific feedback. This crowd rewards the person who shows up as a real engineer rather than a brand, and being present in the thread is not optional, it is the whole etiquette of the place.

There is a line you must not cross: no vote manipulation. Do not ask friends to upvote, do not use multiple accounts, do not run a voting ring. HN detects coordinated voting and penalizes it hard, and getting caught can sink your post or your account. You can tell people you posted, but the votes have to be earned by the post itself. That is genuinely different from how some other channels feel, so do not carry over habits from elsewhere.

Timing helps at the margin. Weekday mornings in US time zones tend to have more readers awake and voting, and early votes are what lift a post off the new page. But do not obsess over it. A great post at an average time beats a mediocre post at a perfect time.

Concrete move: write your title and first comment now, then read them out loud. If any sentence sounds like an ad, rewrite it in the voice you would use to describe the project to another engineer.

A clearly hypothetical worked example#

Let me walk through made-up numbers so you can see the shape of a good day. These are illustrative, not a promise. Real results depend on your product, your niche, and a lot of luck about whether the post catches.

Say you built a small tool that turns messy API docs into a typed client library. You post "Show HN: Generate a typed client from any API's docs" with an honest first comment about how it works, what it cannot handle yet, and a question about which APIs people would throw at it. Suppose it catches, reaches the front page for part of a day, and sends 4,000 visitors to your site over roughly two days.

That is a big spike, and it is mostly people who will look and leave. Say 6 percent, around 240 people, start a free account. Maybe 4 of those convert to a paid plan at a hypothetical 29 dollars per month during the spike. That is about 116 dollars of recurring revenue from the launch itself, which for 4,000 visitors would feel underwhelming if it were the whole story.

But here is the part that pays off. Because you put an email capture on your landing page with a small free thing behind it, say a hosted API spec linter, 300 of those visitors gave you their email even though they did not sign up for the product. And the comment thread handed you a list: a few people pointed out your generated types break on a common auth pattern, someone flagged that your pricing page was confusing, and two mentioned a competitor you had not heard of. Over the next few weeks you fix the auth bug, clarify the pricing, and email your new list with genuine updates. A handful start trials, a couple convert, and one commenter who was skeptical on the day comes back and pays because you actually shipped the fix they asked for. The spike-day revenue was small. The list and the feedback were the real return. For how to think about that whole first cohort, see how to get your first 10 customers and our overview of finding your first customers.

Four paying customers on the day is not the dream you pictured. But 300 qualified emails and a bug list from your exact buyer is a good outcome, and it keeps paying after the traffic is gone.

What you need and what it costs#

Required. A working product someone can try without talking to you, because this audience will not sit through a demo request. A plain, honest title that says what the tool does. A first comment written ahead of time telling your real maker story, including what is rough. A landing page with an email capture, so you keep the traffic you do not immediately convert. And a thick skin, because the comments will be direct.

Optional. A small free tool behind the email capture to raise signups. A short launch-day note to your existing audience that you posted, which is fine as long as you do not ask for upvotes. A simple analytics setup so you can see how many visitors, signups, and emails the day produced, which you will want when deciding whether HN is worth another try.

Not needed. You do not need to pay anyone, and you cannot pay your way onto the front page anyway. You do not need a big following. You do not need a polished marketing site, and a plain one that loads fast and explains the tool clearly tends to do better with this crowd than a glossy one full of claims. What you do need is a landing page ready to hold traffic, which is worth building deliberately. Our guide on building a launch waitlist that converts covers how to make that capture actually work.

The real cost is not money, it is preparation and nerve. Posting is free. Budget a few days to get the product try-able, the title plain, and the email capture in place, then steel yourself for the comments.

How long it takes#

The active event is short: a day or two if the post catches, often less. Preparation is a few days to a week if you are honest about getting the product try-able and the capture in place. The tail is a few weeks, spent following up with the people you captured and shipping the fixes the comments surfaced.

The thing that does not happen fast is revenue, and the thing that does not happen at all is repeat traffic. Search traffic compounds. HN traffic spikes once and stops. So measure the day by emails captured and problems learned, and judge revenue over the following month or two, not by same-day sales.

Concrete move: put a reminder in your calendar for two weeks out to review what you captured and what you fixed, so the spike becomes follow-through instead of a fading memory.

What beginners usually get wrong#

The biggest mistake is treating HN as a growth plan. It is a spike, not an engine. It does not repeat on its own, so pinning your hopes on it leaves you with nothing once the quiet week arrives. It works best on top of channels that run continuously.

The second mistake is using marketing voice. Superlatives, "revolutionary," "game-changing," and hype language get punished here faster than almost anywhere, because this audience reads that as a signal you are hiding a thin product. Plain and honest wins.

The third mistake is posting and disappearing. If you drop a link and vanish, the thread fills with unanswered questions and the post dies. Being present, replying quickly, and engaging with criticism is what the community expects from a maker.

The fourth mistake is taking the harsh comments personally. Someone will say your idea is trivial, or that a competitor already does it, or that your pricing is wrong. Some of that is noise, but a lot of it is the most honest product feedback you will ever get for free. The builders who win read past the tone, thank people, and mine the comments for the real signal. Answer the substance, do not argue with the attitude, and never get defensive in public. And the one mistake that can sink the whole post is any hint of vote manipulation, so let it stand on its own votes.

How I would start#

Here is the sequence I would follow if I were posting a small tool to Show HN in a couple of weeks.

1. First, make the product genuinely try-able without a sales call, and put an email capture with a small free thing on the landing page so any traffic is worth keeping.
2. Second, write a plain title that says what the tool does, then test it on an engineer friend and rewrite until it sounds like a description, not an ad.
3. Third, write my first comment ahead of time: who I am, what I built, why, what is still rough, and one specific question I want feedback on.
4. Fourth, pick a weekday morning US time, post the Show HN, and immediately add my first comment.
5. Fifth, sit with the thread for the day, reply fast, thank the critics, and answer the substance of every hard question without getting defensive.
6. Sixth, over the following weeks, ship the top fixes the comments surfaced and email everyone I captured with real updates, because that follow-through is where most of the money actually shows up.

What I would not do#

I would not ask anyone to upvote or touch anything that looks like vote manipulation, because it risks the whole post and builds nothing real. I would not write the post in marketing voice, because this crowd punishes it on sight. I would not post and walk away, because an absent maker kills a thread. I would not send the traffic to a page with no email capture, which throws away the entire point of the spike. I would not argue with harsh commenters or take the bait, because a defensive founder looks worse than a blunt critic. And I would not treat one HN day as my launch plan, when that energy compounds far better in channels that run continuously, like the community-first approach in launching a SaaS on Reddit or the one-day maker spike of a Product Hunt launch, each of which pulls a different crowd worth having.

The honest close#

Hacker News is worth a shot, as long as you know what you are buying. You are buying a chance at one sharp day of attention from a smart, skeptical, technical crowd, plus some of the most direct feedback you will ever get. You are not buying a customer base, and you are not buying repeat traffic. Most posts get little, a hit brings a spike and a pile of blunt comments, and both are normal.

So run it as one moment inside a larger plan. Get the product try-able, write the post plainly, put an email capture in front of the traffic, show up in the comments as the engineer who built the thing, then do the unglamorous work of fixing what they told you and following up over the next few weeks. Do that and a good HN day becomes a batch of qualified people and a sharper product that keep paying out long after the spike is gone.