Product Hunt Comment Strategy for Makers

A good Product Hunt comment is supportive, specific, and useful to the maker. It is not a soft pitch for your own product and not a paste of "Congrats on the launch!!!"

If you are launching, hunting, or hanging around the PH feed as a builder, comment strategy is relationship work in public. Treat it that way.

Key Takeaways

• Specific questions about features, pricing, or workflow beat generic praise every time.
• Two to five sentences is the sweet spot. Long essays bury the maker's time.
• On your own launch day, your thread matters most. Other launches are for being a good peer.

What Product Hunt comments are for

Product Hunt comments help hunters and makers understand the product, surface real buyer questions, show you as a thoughtful peer, and occasionally start a real conversation.

On Product Hunt, comments do a few jobs:

1. Help hunters and makers understand the product
2. Surface real questions buyers will have
3. Show you as a thoughtful peer in the ecosystem
4. Occasionally earn a reply that starts a real conversation

They are a weak place to drop affiliate links or vague growth tips. The room can smell spam quickly.

Principles that keep you out of the spam bucket

Stay out of the spam bucket by being specific, honest, brief, maker-to-maker, and free of soft sells.

Be specific. Mention a feature, screenshot detail, pricing choice, or workflow. Not "amazing product."

Be honest. If you have not tried it, say what you would test first. Do not invent a review.

Be brief. Long essays bury the makers' time. Two to five sentences usually win.

Be maker-to-maker. Share a constraint you hit building something similar, or a question you would ask as a user.

Skip the soft sell. "We built something complementary, link in bio" under every launch is why people mute accounts.

Comment types that work

Four comment types work on Product Hunt: useful questions, peer observations, tried-it notes (only when true), and supportive bumps paired with one specific detail.

1. The useful question

Ask something the page does not already answer: onboarding, data export, team seats, offline mode, API limits.

curious whether the Chrome side panel keeps state across tabs. that is the failure mode that killed our last extension experiment

2. The peer observation

React to a concrete product decision.

shipping without a free tier on day one is a gutsy call. curious how you are handling drive-by tire-kickers vs serious trials

3. The tried-it note

Only if true. One sentence on what you clicked and what felt clear or confusing.

installed and ran the first workflow. the empty state copy is clear; the second step still asks for a token I did not expect

4. The supportive bump (sparingly)

A short congrats is fine when you know the maker. Pair it with one specific hope or observation so it is not empty.

What to avoid on launch day

Avoid copy-paste templates, pitching your product in the same breath, fake urgency, keyword stuffing, and arguing with hunters about ranking mid-launch.

• Copy-paste templates across multiple launches
• Asking the maker to check your product in the same breath
• Fake urgency ("This will 10x your growth")
• Keyword stuffing for SEO that nobody on PH reads that way
• Arguing with hunters about ranking mid-launch

If you are launching your own product the same day, spend most of your energy on your thread and genuine replies there. Drive-by commenting on competitors to farm visibility usually backfires.

A simple session routine

Open Product Hunt for products in your actual category, read the gallery and top questions, leave one specific comment if you have something real, reply if the maker answers, then stop after a few quality notes.

1. Open Product Hunt for products in your actual category (tools you would use)
2. Read the gallery, first comment from the maker, and top questions
3. Leave one specific comment if you have something real
4. Reply if the maker answers. That is where relationships start
5. Stop after a few quality notes; do not clear the homepage

Using AI drafts without sounding like sludge

AI can help when you blank on wording. It should not invent that you used the product. Draft, delete compliment openers, insert one concrete detail from the page, then post only after you would send it to a fellow founder in Slack.

Workflow:

1. Draft with a practical or curious tone
2. Delete compliment openers and hype verbs
3. Insert one concrete detail from the page
4. Post only after you would send it to a fellow founder in Slack

Same craft rules as human-sounding social replies.

If you are the one launching

On your launch day, lead with a clear maker comment, answer every serious question quickly, thank hunters with varied notes, ignore bait in the thread, and keep answering stragglers for a few days after launch.

Comment strategy flips when it is your launch day:

1. Pin or lead with a clear maker comment: who it is for, what to try first, where to report bugs
2. Answer every serious question as fast as you reasonably can
3. Thank hunters without copy-pasting the same sentence twenty times. Vary the note, reference their question
4. Ignore bait and ranking anxiety in the thread; take product feedback offline when it needs depth
5. After launch day, keep answering stragglers for a few days. Late questions still convert curious readers

Your own thread is where PH comments matter most for you. Other people's launches are for being a good peer, not for farming.

Category etiquette in one minute

Be generous with adjacent tools, stay quiet or ask sharp technical questions on direct competitors, and keep non-overlapping launch notes short and specific.

• Tools adjacent to yours: be generous; the ecosystem is small
• Direct competitors: either stay quiet or ask a sharp technical question without shade
• Non-overlapping launches you love: a short specific note is fine; you do not owe a novel

If you would not say it at a meetup, do not post it under their gallery images.

FAQ

Should I upvote everything I comment on?
Upvote products you genuinely find interesting. Empty upvote-plus-spam comment patterns are easy to spot.

Is it okay to mention my product?
Only when it is directly relevant and invited. For example, the maker asks about alternatives, or you are answering a technical question with real overlap. Lead with value, not a pitch.

How early should I comment?
Early enough that the maker might see it; not so early that you comment before reading. Substance beats racing for first.

Do PH comments grow my X following?
Sometimes people click through. Treat that as a side effect. The primary win is reputation among makers. For X-specific reply growth, see how to grow on X with replies.

Open Product Hunt today. Pick one launch in a category you actually use. Read the gallery, leave one specific question or peer observation, and reply if the maker answers.

Want a draft that sounds like you while you browse launches in Chrome? Try Synapt with trial credits, then edit until it reads maker-to-maker.