Maker First Comment Template: What to Post Under Your Own Launch
The maker’s first comment is a short note, posted by you under your own launch page right after it goes live, that tells visitors who built the product, why, what a first try looks like and what feedback you want. Keep it to about 80 to 200 words, ask one specific question, and do not paste the description again. Three versions follow: an origin note, a first-run guide for products behind a sign-up, and an update post for day three.
Why post a comment under your own launch at all?
A launch page is a product shown to strangers, and strangers hesitate to be the first to say anything. An empty thread looks like an empty room. When you post a note first, you do three jobs at once: you show that a human is behind the page and is paying attention, you give people something easy to reply to, and you put the one question you care about in front of the first visitors, before the thread drifts elsewhere.
This is an established habit on launch platforms. On Product Hunt, whose pages refused our automated check so we limit this to the well-known basics, makers commonly post a first comment on their own product. The same habit works on any board with threaded comments, including the one on this site, where every launch page has a comment thread you can answer in. The point is not to game anything. It is to make the page feel attended to.
What goes in a first comment?
| Part | What it does | Example wording |
|---|---|---|
| Who you are | Shows a human is present | “I’m Maria, I make this on evenings.” |
| Why you built it | One honest reason, the real irritation | “I kept losing track of which invoices were paid.” |
| What a first try looks like | Lowers the cost of trying | “Paste one CSV; it takes under a minute.” |
| What is missing | Builds trust, deflects feature requests | “No mobile app yet.” |
| One question | Gives the thread a direction | “Which export format should I support next?” |
Maria and her invoice tool are invented for this table. The order matters: reasons come before asks, and the single question comes last so it is the thing the reader leaves with.
Three first-comment templates
Hi, I'm [first name], the person behind [product name]. I built it because [the specific moment or annoyance]. Before this I was [how you coped], and it cost me [time, money or patience]. Right now it can [the one or two things it does well]. It can't yet [honest gap]. I'd love your take on one thing: [one precise question, such as which of two options you should build next]. I'll be reading and replying here all [day or evening].
Thanks for stopping by. If you want to try [product name] in under [time]: 1. [First step, with the exact button or command] 2. [Second step] 3. [What you should see when it works] If step [number] fails, tell me which browser, device or version you were on and I will look at it today. [Optional: a demo link that needs no sign-up.] What I'm trying to learn: [question about where people get stuck].
Update, [day]: thanks to everyone who tried [product name]. Three things I heard more than once: - [Most common request or complaint, and what you did or will do about it] - [Second theme] - [Third theme, or a surprise] Shipped so far: [one real change]. Next: [one thing, with a rough date only if you will keep it]. Still curious: [the follow-up question].
How long, and in what tone?
Between 80 and 200 words is the range where a comment is read to the end. Shorter feels like a greeting with nothing in it; longer repeats your description, which the visitor has just read. Write it the way you would explain the product to a friend who asked a fair question. First person, contractions, no exclamation marks, no “we’re thrilled to announce”.
If you built the product with a team, use “I” when you mean the person typing and “we” only when the team really did the thing. Readers pick up the difference quickly, and it is an easy way to look larger than you are, which later reads as exaggeration.
What makes a first comment backfire?
- Asking for votes. Most platforms dislike it, and Hacker News bans it outright in its guidelines. Ask for opinions, never for upvotes.
- Pasting the description. Visitors have read it. Give them what the page could not: the reason behind it and the gap.
- Three questions at once. People answer none of them. Choose the question whose answer would change what you build next.
- Promises you cannot keep. “Ships this week” becomes a debt in public. Say “next” and keep dates for what is done.
- Posting and vanishing. The comment opens a conversation. If nobody answers for a day, the page looks abandoned.
When should you post it, and what comes next?
Post it within a few minutes of publishing, while the page is new and you are at your keyboard. Then reply to every comment, including short ones, with something specific; the reply-to-comments templates show how, and the answer on responding to launch comments covers the reasoning. If you have not published yet, you can launch your product free and have this ready as a note to paste.
Skip the day-three update if there is nothing true to say. An update that says “still working on it” is worse than silence. Pair this page with the launch day checklist, and browse the developer tool ideas on the board if you want to see how short problem statements read before you write your own.
Frequently asked questions
Is it bad form to comment on my own launch?
No. Posting a first comment as the maker is a normal, expected habit on launch boards, because it tells visitors who built the product and gives them something to answer. It becomes bad form only when it is a sales pitch, a request for votes, or a copy of the description.
Should the first comment be the same on every platform?
Keep the facts the same and rewrite the voice. A Show HN comment can be technical and blunt about limits, a Product Hunt-style note can be warmer, and a comment on a smaller board can be shorter. Pasting identical text everywhere reads as automation, and some communities treat it as spam.
What question should I ask in the first comment?
Ask the question whose answer would change your next week of work: which of two features to build, which format to support, or where people got stuck. Avoid yes-or-no questions and avoid “what do you think?”, which invites vague praise. Specific questions get specific replies.
What if nobody replies to my first comment?
That is normal for a new product and says little about its quality. Reply to any comment from anyone else, share the page where it is welcome, and go ask a few people you know to try it and tell you what confused them. Use that feedback, not the silence, to decide what to fix.
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.