How to Respond to Launch Comments: Praise, Criticism, Bugs and Spam
Reply to every real comment on your launch, soon after it appears, in your own words and as the person who built the product. Answer the question that was asked, say plainly what you will change, and ignore trolls without arguing. Do not ask friends to post supportive comments: a thread that reads like a fan club loses the readers you are trying to reach, and some platforms treat it as manipulation.
How quickly should you reply, and in what voice?
Soon, because a thread is read most while it is new. On this board that means the Today feed; on other sites it differs, and nobody can give you an exact number of hours. Pick fixed check-in times for launch day, say every couple of hours, and tell yourself that a reply at the check-in is fine. You do not need to refresh the page all day.
Write as one person. Hacker News’s moderator tips for Show HN posts say to “drop any language that sounds like marketing or sales”, and to use “factual, direct language”, adding that personal stories and technical details work well. The same tips ask you to write your text by hand and not generate it, and the site’s guidelines say the same for posts and comments. Even where no rule says so, a reply that sounds like a brand account reads as a form letter.
Use your own name if you can. The tips also advise against a username that is your company or project name, because it makes the thread look like promotion and not a person taking part.
What should you say to each kind of comment?
The replies below are for PantryPal, an invented meal planner that builds a shopping list from what is already in your cupboard. They show the shape, not words to paste.
| The comment | What the person wants | How to reply | Example reply |
|---|---|---|---|
| Praise | To be acknowledged, and sometimes to ask something | Thank them briefly, then ask one thing that moves you forward | “Glad it fits. What do you cook most, so I know which recipes to add next?” |
| A question | An answer they can use | Answer first, link only if it adds something | “It reads your cupboard list, not receipts. You type or tick items; there is no scanning yet.” |
| A bug report | To know it was heard | Confirm, ask for what you need, give a rough time | “Thanks, I can see why that broke. Which browser were you on? I will fix it today and reply here.” |
| A feature request | To be taken seriously | Ask what they were trying to do, then say yes, no or later honestly | “What would you do with a barcode scan that typing doesn’t cover?” |
| Sharp criticism | A fair hearing | Find the true part, agree with it, answer the rest with facts | “You’re right that the free tier is limited. The reason is X; here is what it covers.” |
| “How is this different from Y?” | A comparison | Name Y respectfully and say what you do differently | “Y is better for full recipe libraries. PantryPal starts from what you already have.” |
| Spam or a pure insult | Attention | Do not engage; report it if the board offers a way | No reply. |
How do you reply to a comment that stings?
- Wait ten minutes before writing. The first draft is for you.
- Pull out the claim hidden in the comment. “This is pointless” often means “I do not see why this beats my spreadsheet”.
- Answer the strongest reading of what they said. Hacker News’s guidelines ask commenters to “respond to the strongest plausible interpretation of what someone says, not a weaker one that’s easier to criticize”, and a maker who does it first sets the tone.
- Agree out loud where they are right. It costs you nothing and takes the heat out.
- Stop after one exchange if the thread goes in circles. You can leave the last word to them.
Do not defend the product against someone describing their own experience. If a person says a step confused them, it confused them, and the useful reply is “thank you, I will change that”.
Which replies and habits hurt a launch thread?
- Booster comments from friends. The Show HN tips say plainly to make sure friends and users do not add them, because readers spot them and call it spamming. The guide to earning upvotes covers the same trap.
- The same line to everyone. “Thanks for the feedback!” under ten comments looks automated. Say something specific to each person.
- Link-only replies. On this board, links inside text people write are marked nofollow and ugc, so a link dropped in a comment does nothing for search anyway. Use it to help, not to promote.
- Posting your link in other makers’ threads. Reply to their launches because you have something to say about them.
- Promising what you will not build. “Soon” is a commitment. Say “not planned” when it is true.
What if nobody comments at all?
A silent thread is common and is not a verdict on the product. Seed it yourself with a maker’s note that says why you built it and one question you want answered, and keep that question narrow so it is easy to answer. The maker first comment template gives a shape. If the quiet comes with no visits either, work through why nobody visited my launch.
If you have not posted a launch page yet, launch your product for free on this board, where comments are threaded and a thread can start with a single useful question from you.
How do you know your replies helped?
Keep a short log with four columns: the comment, its type, what you did and whether you closed the loop. After a few days look for three things. Did conversations go back and forth more than once? Did anyone who commented go on to use the product? Did you ship a fix someone asked for and tell them? Those are the outcomes that count, and none depends on how many comments you collected.
When the log shows repeated problems, use the sorting rules in how to get feedback on an MVP to decide what to fix first, and use the reply templates when you want ready wording. If you are still choosing what to build, the ideas board shows what others are discussing.
Frequently asked questions
Should I reply to every comment on my launch?
Reply to every comment that is a real question, report, request or criticism. A short thanks is enough for plain praise. Skip spam and pure insults. Replying shows readers that a person is behind the product, and it gives you the details you need to improve it. Be specific instead of repeating one line.
How do I respond to negative comments on my launch?
Pull out the true part, agree with it, and answer the rest with facts, without defending yourself against someone’s own experience. Wait ten minutes before you write. If a thread turns circular after one exchange, stop and let it rest. A calm, specific reply often wins more readers than the original comment cost you.
Is it okay to ask friends to comment on my launch?
Not to cheer for it. Hacker News tells makers to make sure friends and users do not add booster comments, since readers see through them. A friend with something useful to say, such as a real question or a fair criticism, is welcome. Ask people to try the product and be honest, not to be supportive.
What should I put in my first comment?
Say why you built it, what it does in one sentence, and one question you want answered. Keep the question narrow, such as which step felt slowest. Avoid sales language. A first comment gives readers a place to begin when the listing itself is short.
Written by Post your build ideas with AI assistance and edited for this site. Where a page names another product, the facts came from that product’s own pages on the date shown above; terms change, so check them before you rely on them. About the publisher.