How to Get Waitlist Signups From Hacker News (and When Not to Try)

Most advice tells founders to post their launch on Hacker News. For a pre-launch waitlist that advice is close to backwards: Show HN exists for things other people can try right now, and a page that collects an email and promises something later is explicitly not that. This post covers what the rules actually say, the three things that do work on HN before you have a product, and what the traffic is worth if you land it.

Table of contents

• What Show HN is actually for
• Why a waitlist post gets flagged
• Three plays that work pre-launch
• When you are ready for a real Show HN
• Titles, and the one mistake everyone makes
• The comments are the product
• What HN traffic is actually worth
• Frequently asked questions

What Show HN is actually for

Hacker News publishes its Show HN rules on a dedicated page, and they are short enough that there is no excuse for guessing. The central line is that Show HN is for something you have made that other people can play with. The page then lists what does not qualify, and the list is the part founders skip: blog posts, sign-up pages, fundraising announcements, job postings, and anything people cannot actually try.

A pre-launch waitlist page is a sign-up page. It is on the list by name. This is not a moderator being harsh on the day, it is the documented rule, and the community enforces it by flagging long before a moderator arrives.

Worth knowing too: Launch HN, the format you sometimes see at the top of the front page, is not open to everyone. It is reserved for YC-funded companies and coordinated with the moderators. If you are not in a YC batch, Show HN and ordinary submissions are your two options.

Why a waitlist post gets flagged

Even setting the written rule aside, HN has a specific allergy that is useful to understand, because it explains a lot of otherwise confusing outcomes. The audience is largely engineers who arrived wanting to look at the thing. When the link leads to a page that asks for an email before showing anything, the reaction is not indifference, it is irritation. Flags follow quickly, and a flagged post drops off /newest within minutes.

The same allergy applies to a few adjacent things worth avoiding:

• A demo that requires an account before it does anything. If people have to sign up to see it work, it reads as a sign-up page with extra steps.
• Marketing language in the post body. HN rewards plain description and punishes anything that sounds like a press release.
• Asking friends for upvotes. Voting rings are one of the few things HN detects aggressively and penalises at the account level. It is not worth the risk on a post that was unlikely to take off anyway.

Three plays that work pre-launch

None of these is a launch. All three put you in front of the same audience without breaking a rule, and all three work better than a Show HN that gets flagged in four minutes.

1. Comment where the problem comes up

This is the highest return per hour on all of HN and almost nobody does it deliberately. Find threads where people are describing the problem you are solving, and write the genuinely useful comment: what you learned, what did not work, the specific detail nobody else mentioned. Mention what you are building only if it is relevant, and never as the point of the comment. A good comment on a busy thread is read by more of your actual audience than a mediocre Show HN would be.

2. Write the technical post, submit that

Blog posts are not Show HN material, but they are perfectly normal HN submissions. If the work behind your product produced something worth reading, write that up honestly and submit the article. The post has to stand on its own as writing, not as a funnel. Your product gets a mention in the text and a link in your profile, and that is the whole promotional payload.

3. Ask HN, when you have a real question

Ask HN works when the question is genuinely open and specific enough to be answerable. It does not work as a disguised advert, and the audience spots the difference immediately. The bar is whether you would still want the answers if nobody clicked through to anything of yours.

All three share a shape with what works on Reddit, which I covered in getting waitlist signups from Reddit. The difference is that Reddit has communities where promotion is allowed if you follow the rules, and HN has no such room anywhere.

When you are ready for a real Show HN

The bar is one sentence: a stranger can click your link and do the main thing without creating an account. Not a video, not a screenshot tour, not a sandbox behind a signup. If you can get to that, Show HN is open to you and it is one of the best launches available to a solo founder.

Practical ways to reach that bar earlier than you think:

• Ship a public demo with sample data preloaded, so the thing works on arrival and signup is only needed to save work.
• Carve out one feature that can run anonymously, even if the full product cannot.
• If your product is genuinely account-shaped, open source a piece of it and Show HN that instead. It is a real thing people can run.

Keep the waitlist page for every other channel. It is the right landing page for Reddit, X, directories, and search, and the wrong one for HN specifically. There is no contradiction in running both.

Titles, and the one mistake everyone makes

HN titles are plain by convention and by rule. The site asks you not to editorialise, and the audience downvotes hype on sight. The format for Show HN is the prefix, your product name, and a flat description of what it does.

Good:
Show HN: A CLI that finds unused CSS in a Next.js build

Bad:
Show HN: The ultimate tool every frontend dev has been waiting for

Also bad (this is a sign-up page, it will be flagged):
Show HN: Join the waitlist for my new CSS tool

The mistake almost everyone makes is writing the title for the front page rather than for /newest. Nearly every post starts on /newest, where a small number of people are skimming a fast-moving list. The title has to make one of them curious enough to click within a second. Concrete nouns do that. Adjectives do not.

The comments are the product

If a post does get traction, the comments are worth more than the traffic, and this is the part founders handle worst. The norms:

• Reply to everything, quickly, in the first few hours. Response rate visibly affects how a thread goes.
• Answer the harsh comments properly. HN respects a founder who engages with a real criticism and loses interest in one who gets defensive. The critical comments are usually the most informative ones you will get all year.
• Say what it does not do. Volunteering a limitation buys more credibility than any feature list.
• Never argue about the flagging or the votes in the thread itself.

Treat the thread as a free user research session that happens to have an audience. What you learn there belongs in the same place as the rest of your feedback, next to your survey answers, so it is still there when you are deciding what to build next.

What HN traffic is actually worth

Expectations, honestly set. The large majority of Show HN posts get almost no attention: they appear on /newest, collect single digit points, and never reach the front page. That is the normal outcome, not a failure, and it is why HN should never be your only plan for a launch day.

When a post does hit, the traffic arrives fast and converts poorly compared with every other channel. HN readers click through to look, and looking is most of what they came to do. A spike that produces thousands of visitors and a small fraction of a percent in signups is an ordinary result, and it is worth understanding before you draw conclusions from the number. As I put it in validating an idea before writing code, a spike from one source is a sample of one audience, not evidence that the market wants your product.

The durable value is different and larger: a few engineers who become real early users, a handful of criticisms that change your roadmap, and a link from a domain that search engines and AI answer engines both weigh heavily. Those outlast the traffic spike by a long way. The wider picture of stacking channels is in how to grow a waitlist organically.

Frequently asked questions

Can I post my waitlist as a normal submission instead of Show HN?

Technically yes, and it will almost certainly be flagged anyway. The objection is to the page, not to the prefix. If the link leads to an email capture form, changing how you submit it does not change what people find.

What if my product genuinely cannot work without an account?

Then either build the smallest anonymous slice of it, or skip HN as a launch channel and use it the way described above, through comments and writing. Plenty of good businesses are a bad fit for Show HN, and forcing it wastes the one attempt you get with a given post.

When should I post?

Weekday mornings US time are the conventional answer, because that is when the most people are watching /newest. It matters far less than whether the thing is worth clicking. Do not spend a week optimising the hour for a post whose title is not ready.

My post got no traction. Can I submit again later?

A post that got no attention can be resubmitted after a reasonable gap, and the guidelines allow for this. Repeatedly submitting the same link, or the same thing under slightly different titles, is treated as spam.

Should I mention that I built it solo?

Only if it is relevant to what you are showing. HN is not sentimental about founder stories and the top comments will be about the software either way. Lead with what it does.

Hacker News is the one channel where the honest move and the effective move are the same: build something a stranger can try, then describe it plainly. Until you have that, spend your time in the comments rather than in the submission form, and keep the waitlist page pointed at the channels it suits. When the demo is ready, HN will still be there, and the post will be worth writing.

Lighthouse builds the waitlist page, asks your survey question on the signup form, and keeps the answers and your feedback in one place, so what you learn in a launch thread does not get lost. From an indie dev, for indie devs and makers.