Quick answer: The maker comment is the comment the maker posts within the first few minutes of a Product Hunt launch. It's pinned at the top of the discussion thread, and it's where you tell the story behind the product in your own voice.

It matters because the listing itself is a product page; the maker comment is the human part. Here's what it should contain, how long it should be, and a structure you can reuse.

What the comment does

It answers four questions a reader has:

  1. What is this, exactly?
  2. Why does it exist?
  3. Who built it, and why are they qualified to?
  4. What should I do now?

A good comment reads like a person explaining their work to a smart friend. A bad comment reads like a press release pasted into a text box.

The structure

Five short sections, roughly 200–350 words total.

1. One-line intro. State the product and what it does in a sentence.

2. The problem. The specific situation that made you build it. This is the strongest part of the comment; write it in the way users describe the problem, not the way you'd describe the market.

3. What it does. A short, concrete description of the core workflow, maybe 2–3 sentences. One small screenshot or a short GIF can be embedded in the comment, but the text has to work without it.

4. The honest state. What's built, what's rough, what's coming. Readers trust early-stage products more when the founder is candid about what isn't done.

5. The ask and the thanks. Ask for specific feedback, and thank people who helped.

What to avoid

  • A wall of adjectives. "Beautiful, powerful, seamless" tells the reader nothing.
  • The founding myth with no specifics. A real story has a concrete moment.
  • Fake scarcity. Nothing about a launch discount that doesn't exist.
  • Asking for upvotes. The comment asks for feedback and questions, not votes.
  • Copy-paste in every other channel. The maker comment is native to the Product Hunt thread; the X launch post has a different shape.

The template

Here's the skeleton, not a script to fill mechanically.

Hey everyone, we're [names] — maker of [product].

[One sentence: what it is and who it's for.]

The short version of why we built this: [specific problem,
the situation it showed up in, and what the workaround looked like].

Today it does [concrete workflow, 2–3 sentences].
We used [real technology or method], and the thing we care about
most is [honest design decision].

What's honest: [what's rough or limited].
What's next: [one or two genuine roadmap items].

We'd love feedback on [specific question].
Thanks to [people].

How it connects to the assets

The comment links to the gallery, and the gallery should carry the details the comment can't. A reader who finishes the comment and wants to see the product taps through, so make sure the gallery order tells the same story. The gallery and thumbnail specs are in the launch asset checklist.

Timing

Post it within the first few minutes after the 12:01 AM Pacific go-live. Have it written and saved in a note so you can paste it at go-live. This is one of the items on the launch day timeline.

Frequently asked questions

How long should the maker comment be? 200–350 words. Long enough to be a real story, short enough that nobody skips it.

Can I edit it after posting? Yes, but edit for small errors, not to add marketing. The first readers saw the original.

Should the comment link out? Link to the product (already on the listing) and one or two genuinely useful things; don't turn it into a link farm.

What if there are two makers? Write it in one voice and introduce both. Two competing styles in one comment reads as stitched together.

Can an AI draft it? It can draft the structure, but the problem story and the honest state are the parts that have to sound like you. The rest of the launch can be generated in Neatico; the maker comment is the one thing worth writing by hand.

Write the problem section first and read it out loud. If it sounds like a press release, rewrite it in the language you'd use explaining the product to a friend at a coffee shop.