Answering Comments on Your Launch Page Like a Pro

Comments are the best thing a launch gives you, and the thing founders are least prepared for. A vote is a number. A comment is a person telling you what they think, in their own words, for free. Used well, comments produce your first users, your best ideas and a record of how you treat people. Used badly, they produce a defensive thread that scares visitors away.

This guide covers how to read, answer and learn from comments during a launch.

Why comments matter more than votes

Product Hunt's launch guide points out that comments let makers gather feedback and often open doors to networking, partnerships and even funding. It also says that you cannot ask for upvotes directly but should invite people to visit and comment. The platform's emphasis tells you what it values: conversation.

There is also a practical reason. Visitors who read comments are deciding whether to try the product. A thread in which the maker answers questions clearly and kindly is a better advertisement than any copy you could write.

Set up before the day

Draft your core answers. Write short replies to the questions you expect: what it does, who it is for, how it differs from the obvious alternative, how data is handled, what is coming next. These are not for pasting. They are to keep your facts straight.

Decide who replies. If you have teammates, assign topics. Questions about the product go to the person who knows it best. Questions about support go to whoever handles it.

Agree a tone. Warm, direct, humble. Ten words of kindness cost nothing.

Prepare a place for follow-ups. Where will people go with bug reports? A support email, a form, a chat? Have it ready and mention it where useful.

The anatomy of a good reply

Most good replies have four parts.

1. Greeting and thanks. Use the person's name if shown.
2. Acknowledgement. Show you read their comment: "You asked whether it works offline."
3. The answer. Specific and truthful.
4. A next step or question. "Which export format would you need?"

A reply with all four takes thirty seconds and feels personal.

Kinds of comments and how to handle them

The compliment

"This looks great!" Thank them, and ask something that moves the conversation forward: "Thank you! What would you use it for first?" You learn something and keep the thread alive.

The question

Answer it clearly, then add a short extra if it is useful. If the question reveals a gap in your page, note it for later.

The pricing question

State what you can, briefly, and point to your own pricing page for current figures so nothing goes stale. If something is not decided, say so: "We are still working on team plans and would like to hear what you need."

The comparison

"How is this different from X?" Do not run the competitor down. Say what you do differently, and be honest about where they might suit someone better. Readers trust fairness.

The feature request

Thank them and explore the need. "That is interesting. What are you trying to do when you need that?" Sometimes the underlying problem has a simpler answer than the requested feature. If you are not going to build it, say so kindly and explain why in a sentence.

The criticism

This is the one that tests you. Take a breath. Then:

• Thank them. They took time.
• Restate the point. "You found the sign-up confusing."
• Offer facts. What the design is meant to do.
• Say what you will do. "We will test a shorter version this week."
• Do not argue. If you disagree, say so once, politely.

Visitors reading the thread see a person who can hear criticism, which is reassuring.

The bug report

Thank them and say you are looking into it. Ask for what you need: the device, the steps. Report back in the thread when it is fixed, so everyone sees the follow-through.

The troll

Some comments are not worth engaging with. A short, civil reply, or none, is fine. Report abuse to the platform. Hacker News's guidelines ask users to be respectful and to ask genuine questions rather than interrogate, and a thread that follows that spirit is easier for everyone.

The spam

Ignore it and report it.

Keep the thread tidy

• Reply in the thread, not in a separate message, so others can see the answer.
• Link to resources sparingly. One helpful link is enough.
• Avoid walls of text. Short paragraphs are easier to read on a phone.
• Do not edit your replies to change their meaning, after others have responded.
• Correct mistakes openly. "Correction: we do support Windows."

Mind the rules

Platforms differ in what they allow. Product Hunt says company accounts are prohibited and only personal accounts can launch, and it warns that behaviour marking an account as spam breaks its guidelines. Hacker News asks that you do not use it primarily for promotion. Read the rules of the platform you use, and keep within them, even in the heat of the day.

Time management

Comment threads can eat a day. A few techniques:

• Batch. Reply in bursts of fifteen minutes rather than constantly.
• Prioritise. Questions and bug reports first, compliments next.
• Use a spreadsheet to log feature requests and bugs, with the commenter's name and the date.
• Take breaks. A rested founder writes better replies.

Turning commenters into users

Many commenters are potential customers. Without being pushy:

• Invite them to try. "Here is a link to a sandbox with sample data."
• Offer help. "If you tell me what you need, I will set up an example."
• Follow up later. Note the people who asked for something, and tell them when it ships.
• Thank them in public when a suggestion improves the product.

A commenter who sees their idea built becomes an advocate.

What to record afterwards

When the competition closes, save the thread. Then do some analysis.

1. Count the question types. How many were about pricing, features, bugs, comparisons?
2. List the top three confusions. Each is a fix for your page or product.
3. List the top three requests. They guide your roadmap.
4. Find your champions. The people who engaged most are your first community.
5. Collect quotes, with permission, for later use.

Common mistakes

• Getting defensive. It is the fastest way to make a thread worse.
• Overpromising. "We will build it next week" is a promise you must keep.
• Ignoring tough comments. Silence reads as avoidance.
• Replying only to praise.
• Writing identical replies. They feel automated.
• Arguing about ranking.

On this site

If you launch with us, comments appear on your entry, and the acceptable use page sets out what is and is not allowed. The submit page starts your listing. Launch entries are currently $5, and none of the paid options change who can comment or vote. The founders describe their approach to community on the about-founders page.

Example replies you can adapt

Seeing real wording helps, so here are a few examples for an imaginary rota tool called Shiftly. Adapt the structure, not the words.

To a question about integrations. "Thanks for asking, Priya. Shiftly can export to a spreadsheet today, and a calendar feed is in testing. Which calendar do your staff use? That will help us decide what to ship first."

To criticism of the sign-up. "Fair point, Dan, and thank you for saying it plainly. Asking for a company name before showing anything is friction we added without testing. We are trialling a version that lets you try a sample rota first. I will post here when it is live."

To a comparison. "Good question. The older rota tools are stronger on payroll. Shiftly is narrower: it focuses on swaps and last-minute changes, and sends staff a message when something moves. If payroll is your main need, one of those may suit you better."

To a feature request we will not build. "I understand why that would help, Jo. We have decided to keep Shiftly small and not add time-tracking for now, because it would complicate the thing people like about it. If you tell me what you need it for, I might know a simple workaround."

Notice that every example thanks the person, answers the point and ends with something concrete. None of them is long, and none is defensive.

When the thread is quiet

A launch with few comments is not a failure. If the thread is quiet, make it easy to join. Post a follow-up comment of your own later in the day, asking a specific question such as "What is the first thing you would try?" Share one short behind-the-scenes note about how a feature came about. Reply to the thoughtful comments on other entries you have genuinely tried. The people who respond to those may well visit your page in return, which is community behaving as it should.

A closing habit

At the end of each day of the competition, spend ten minutes rereading the thread from the top. Fix typos, answer anything that slipped through, and write one line in your log about the single most useful thing someone said. After a week, that list is a better product brief than most you could commission.

One principle to carry

Treat each comment as a conversation with one real person. If you do that, the thread takes care of itself, and so, over time, does the product.