Launch day: be in the thread at minute zero and answer for five hours
A minute-zero to hour-five Show HN checklist for founders who need first real users, not front-page points.
The thread is the first sales call
You are about to post Show HN, and most posts never get a comment. In a 70,894-post dataset, 61.6% stayed silent. Treat that silence as a signal to keep working, not a verdict. The first five hours are the window where you can still shape the reply.
The lane is also faster and more crowded. Monthly submissions went from about 1,600 in late 2024 to about 3,900 recently, a 2.4x rise. The median time to first comment dropped from 9.6 hours to 5.1 hours between 2025 and 2026.
The odds of a big hit have tightened. In 2026, 1.67% of launches reached 100 or more points, half the 2025 share. The share reaching 10 points fell from 14.5% in late 2024 to 7.8% in early 2026. The middle band of 10 to 100 points, once a sign of real momentum, dropped from 9.5% to 6.1% in a year.
For a founder without distribution, the thread is a manual sales call. Aim for a few replies that can become first users, not a front page. Growth tactics that need scale do not help here. You post, stay, answer, and learn what breaks. The first hundred users will come from one-on-one attention.
Silence is a normal outcome
The baseline was small and quiet: the median was 2 points, the 75th percentile was 4, and the 90th was 9. It is not catastrophic. A thread with no comments can still tell you whether the product is understandable. A first comment that complains or asks about pricing is useful. A missing comment points to the post itself. Make the next step obvious.
When the thread is quiet, check whether a stranger can say what the product does and what to try first. A stranger who cannot points to the same fix: tighten the title, the first line, or the link. The silence is also a test of your own description. If you need to explain it in a comment, the post did not do its job.
The checklist is manual work
The list is short because the work is manual. Before you post, write a short description and direct answers for the questions you expect: cost, what it replaces, and what it does not do yet. Keep the answers ready in a note, because the first comments arrive while you are still settling in. The note is your first support desk.
- Post the moment the product is live. Say who it is for, what it does, and what a new user should try first.
- Stay in the comments from the start. Do not leave the thread to check email or wait for a point spike.
- Answer every question in the first five hours, even the small ones.
- Surface the first real user problem in your own words. Name the exact step where the user got stuck, and say what you changed or will change.
- Keep the thread alive for five hours by replying to every new comment and asking a follow-up question that invites another person to try it.
A good answer is direct and short. For a question about a particular tool, answer yes or no, then add the limitation that matters. When you do not know, say you are checking and come back with the answer. Do not hide behind a generic reply. First users judge responsiveness more than polish, and a fast, honest answer is part of the product.
After hour five, stop treating the thread as a live conversation. Read every comment again. Write down the first user problem, the first objection, and the first person who seems likely to return. Then do the unscalable thing: email that person, ask what they tried, and tell them what you fixed. That email is the first real user conversation.
