Turn a Show HN spike into your first 100 real users

Your Show HN post is live. Comments are piling up. The next few hours decide whether the spike becomes a list of people you can talk to or a metric you cannot use by tomorrow.

A launch spike behaves like a room full of strangers who have already raised their hands. The first hundred users are won by treating each comment as a personal meeting, not by waiting for a growth tactic to catch up.

The spike is a set of meetings

When a post gets attention, the useful signal is the comment that says the product did or did not work, not the point count. DenchClaw's Hacker News launch post accumulated 147 points and 124 comments. A Hacker News commenter, hakobapollo, reported a successful DenchClaw installation. That single line is worth more than a vague compliment because it names a person, a result, and a next step.

If your product has setup friction, the thread will show you where it is. A public repository, a required runtime, a default port, or a license question can all become the reason someone stops before trying. Answer those questions plainly in the thread, then move the conversation to a place where you can keep it.

The checklist wins the first hundred

It builds a short list of people who will tell you whether the product is real, not a funnel.

• Classify every comment before replying. Put each one in a few buckets: tried it, wants to try it, has a blocker, or is just curious. If you cannot tell, ask one direct question.
• Reply to every comment quickly. A short answer is enough: make the commenter feel seen, not write a blog post.
• Tag the people who actually tried the product. A successful install, a screenshot, a bug report, or a use case is a signal. Mark those comments so you can find them later.
• Answer setup questions in the thread. If someone asks how to run it, what it costs, or where to get help, answer plainly. Do not make them dig through docs.
• Move the useful conversations to a private channel. A chat channel, a team workspace, or a simple email thread works, because it gives you a place to follow up without crowding the public post.
• Send a personal follow-up to the 10 to 15 most engaged commenters. Pick the short list of people who tried it, asked sharp questions, or offered feedback. Mention one specific thing they said.
• Ask for one next step. Do not ask for a testimonial, a referral, or a sale. Ask them to try one narrow task, report one blocker, or join a short feedback call.
• Record who they are and what they said. Keep a simple sheet with name, comment, status, and next action. This is how you track your first users instead of relying on memory.

The order matters. Classification tells you who is real. Replies keep the thread active. Tagging preserves the signal. Follow-up turns a public comment into a private relationship. If you skip the last step, the first hundred stay strangers.

A follow-up that says thanks is weak. A follow-up that names the exact blocker is a meeting. If someone reports a problem, ask for the error. If someone described a use case, ask whether they will try it again tomorrow.

Follow-up is where the first hundred become real

The public thread is the front door. The follow-up is where users come back. A user who tried the product and got a personal reply is more likely to come back than a user who saw a launch banner and disappeared.

Do not wait for the metrics to settle. The first users after launch are won manually. You will message people one by one, answer the same setup question twice, and learn which part of the product feels broken because a real person tried it and stopped.

When the thread ends, the work is not over. The people you tagged, followed up with, and recorded are your first community. Use them to decide what to fix next, what to ignore, and which narrow problem deserves the next round of manual support.