Favors.dev
The short answer
The Product Hunt first comment is a personal note from the maker that sits right below your product gallery. Write it in five parts: an opening line about you and the problem, the story, what it does and who it is for, one honest limitation, and one specific question. Write it a week before launch, and keep it short enough to read in under a minute.
Most founders write this comment in the ten minutes before they go live, in whatever mood they are in. That is a strange way to treat the longest piece of copy on your launch page. It is longer than the tagline, it is read by far more people than your description, and it is the only text on the page that sounds like a person.
Below is the structure I use, one full example marked up line by line, a bank of replies for the four questions every launch gets, and the part almost nobody includes. If you are still on the tagline, start with the Product Hunt tagline teardown first. I checked Product Hunt's guidance in a real browser on the day this was published, since the site blocks automated fetchers and plenty of guides repeat what someone remembered.
What is the first comment for, and why does it outrank your description?
It is your launch post. Product Hunt's launch preparation guide says the first comment appears right below your product gallery, that you can add one when you submit your product so you do not have to wait until you are live, and that 70% of products that achieved Product of the Day, Week or Month included one from the maker.
Treat that last number carefully. Strong launches probably write strong comments, so it is a correlation, not a promise. But it tells you where the people who do this well put their effort.
The description is a summary. The first comment is a conversation. It is where a visitor decides whether there is a real person behind the product, and it is the first thing everyone replies to, so whatever you put in it shapes the whole thread underneath.
What is the five-part structure that works?
Product Hunt suggests including key features, who the product is for, your story, a launch offer and a request for feedback. I put those in an order that reads well and add one thing the guide does not mention, the honest limitation.
01The opening line
One sentence on who you are and the problem you got tired of. No greeting ceremony.
02The story
Two or three sentences on why you built it. What you were doing when the idea showed up.
03What it does, and who it is for
The two or three features that matter, written for one specific person.
04The honest limitation
What it does not do yet, or who it is not for. One or two sentences.
05The specific ask
One question you want answered. Feedback, never votes.
Keep it to roughly 120 to 200 words, with a blank line between each part. If a launch offer exists, add one short line for it after part three. Product Hunt also says emojis work best used sparingly, like bullet points for a short list of features, and that being humble and helpful is a better tone than marketing speak.
A complete first comment, annotated part by part
This is an invented product called Receiptly, written to show the pattern. It is not a real listing. Each block shows the line, then why it is there.
Part 1
I'm Dana, a freelance designer, and I lost a whole weekend last April rebuilding a tax folder from a camera roll of crumpled receipts.
Opening line. A person, a problem and a concrete detail in one sentence. A stranger already knows why this exists.
Part 2
Receiptly is the fix I built for myself. You photograph a receipt, and it lands in a spreadsheet with the date, the vendor and the category already filled in. I used it for six months before I let anyone else try it.
The story. Short, first person, and it shows the product was used before it was launched.
Part 3
It's built for freelancers and one-person studios who file their own taxes. The three things it does: reads a photo of a receipt, matches it to the right tax category, and exports one clean sheet your accountant can open.
What it does and who it is for. A named audience and three features, no adjectives.
Part 4
What it doesn't do yet: it only reads English-language receipts, and it doesn't connect to bank feeds. If you need either, it isn't ready for you today.
The honest limitation. It filters out the wrong visitors and makes the rest trust the other claims.
Part 5
The one thing I'd love to know: what is the most annoying receipt you have ever had to deal with? Handwritten ones, faded thermal paper, foreign currency. I'm trying to collect the worst cases to test against.
The specific ask. A question anyone can answer in one line, and it asks for experience, not votes.
That whole comment is under 190 words and takes about 40 seconds to read. Notice what it leaves out: no feature list longer than three items, no adjectives like powerful or seamless, no thanks to the hunters, and no request to vote.
Why does the opening line matter most, and why does "hey hunters" waste it?
Visitors scan the first line of a comment and decide whether to read the rest. "Hey hunters, excited to share my launch!" spends your best sentence on a greeting and a feeling. Nobody learns anything from it.
Weak opener
Hey Product Hunt! After months of hard work, I'm thrilled to finally share Receiptly with you all.Working opener
I'm Dana, a freelance designer, and I lost a whole weekend last April rebuilding a tax folder from a camera roll of crumpled receipts.The second version contains a name, a job, a problem and a concrete detail. Anyone reading just that line can picture the product before you name it. A simple test: if you can delete the opening sentence and lose nothing, it was not doing any work.
What do founders leave out, and why include the honest limitation?
Almost every first comment is a pitch. A comment that says what the product cannot do yet reads differently, because it is the one thing a pitch never says. It does two jobs. It sends away the visitors who would have churned anyway, and it makes the rest more willing to believe the claims you did make.
Keep it specific and short. "We are still early" is a hedge. "It only reads English-language receipts" is a fact. Pick the one gap that you hear about most often and state it plainly. You are not confessing anything. You are setting expectations so the first people to try it are the right people.
The second thing founders leave out is a specific ask. Product Hunt asks makers to request feedback, not upvotes, and the best way to do that is a question someone can answer from their own life, like "what is the most annoying receipt you have dealt with?" People who have an answer will give it. People who do not will just scroll past, and that is fine.
Writing it a week early, and what to change on the day
Because Product Hunt lets you add the comment when you submit, you can write it, sleep on it and get it read by someone else. Do that a week out. Show it to two people who have never seen the product and ask them one thing: after reading it, what is this and who is it for?
On the day, change only what has changed. Update the launch offer if it is live, fix anything that is no longer true, and read the opening line one more time. Do not rewrite the whole thing at 6 AM because you feel nervous. If you are still working out where else to launch, my launch directories guide lays out the options, and the listing requirements checklist covers every other field on the page.
Replying: what to say in the first six hours
Every launch gets roughly the same four questions. You can prepare the substance in advance, but write each reply yourself. Product Hunt's commenting guidelines say the community wants to hear from real people, with no LLMs or Chrome extensions, so a pasted or generated reply can get a comment hidden. Here is what a weak and a strong answer look like for each question.
"How is this different from [bigger tool]?"
Weak: We are way more powerful and modern.
Strong: Fair question. [Bigger tool] does a lot more. Receiptly does one thing: photo to spreadsheet in about ten seconds. If you only need that, it is faster. If you need invoicing and bank sync, use them.
"What does it cost?"
Weak: Check our pricing page!
Strong: Free for the first 20 receipts a month, then a flat monthly fee. The exact numbers are on the pricing page, and I will put the launch offer in this thread so it is easy to find.
"Will you add [feature]?"
Weak: Great suggestion, it's on the roadmap!
Strong: I want to, and I will tell you where it sits honestly: it is not in the next month. Can you tell me how you would use it? It helps me decide the order.
"How does it work under the hood?"
Weak: Proprietary AI.
Strong: It reads the text off the photo, then matches the vendor to a category list I wrote by hand. When it is unsure, it flags the row instead of guessing. Happy to go into more detail if you want it.
The pattern is the same each time. Answer the question first, say something true that does not flatter you, and finish with a question when you can. Reply to every comment, including the skeptical ones, and do it from your own account as the maker. The first six hours are when the thread is being formed, and a thread where the maker is visibly present keeps going. For the rest of the day, my full Product Hunt launch walkthrough has the timeline, and what gets you banned on Product Hunt is worth reading before you ask anyone to show up.
One more place the thread gets its first voices: your own network of fellow founders. On Favors.dev you can put your date on the launch calendar and ask other founders to read your page and leave a real comment. That is a favor, earned and spent in points, and it is about conversation, not votes.
Frequently asked questions
What should you write in your Product Hunt first comment?
Introduce yourself and the problem, tell the short story of why you built it, say who it is for and what it does, state one honest limitation, and ask one specific question. Product Hunt's own launch guide suggests covering key features, who the product is for, your story, any launch offer, and a request for feedback rather than upvotes.
Is the first comment important on Product Hunt?
Yes. Product Hunt's launch preparation guide says the first comment appears right below your product gallery, and that 70% of products that achieved Product of the Day, Week or Month included a first comment by the maker. That is a correlation rather than proof of cause, but it is a cheap thing to get right.
Can you write the Product Hunt first comment before you launch?
Yes. Product Hunt's guide says you have the option to include one when you submit your product, so you do not have to wait until the launch is live. Write it a week early, then adjust only what changed on the day.
How long should a Product Hunt maker comment be?
Short enough to read in under a minute. Roughly 120 to 200 words with short paragraphs works, because most visitors skim it. Lead with the most useful sentence and put the ask at the end.
Should you ask for upvotes in your first comment?
No. Product Hunt's guide says to ask for feedback, not upvotes. Ask a question that people can answer from their own experience, which gives them a reason to comment instead of just clicking.