Launch day on X fills the replies with the same two words. The founder reads every one of them, because on launch day they read everything, and they remember the handful that said something. A reply that asks a real question, names the one thing that is genuinely good, or shares the launch with the right person does more for the launch than a hundred emojis, and it is the kind of reply people follow you for.
Below are 14 replies for the launches you will see this month: a friend's, a stranger's, a product in your own space, a Product Hunt day. Each one is written so the founder can answer it, so other readers learn something from it, and so you look like someone worth knowing.
What launch day looks like from the inside
The founder has been awake since five. They are refreshing a dashboard, answering DMs, fixing the bug that only appears when real people arrive, and reading the replies between all of that. Short congratulations are kind and they blur together. What stands out is anything that gives them something to do: a question to answer, a flaw to fix, a sentence to screenshot for the next landing page.
The other readers of a launch post are founders too, mostly. They read the replies to see what questions get asked and what reactions a launch gets. A reply that is useful to the founder is usually useful to them as well, which is why the shapes below are the same ones that work under any build in public update: specific, short, answerable.
Congrats on shipping. One question after reading the landing page twice: is this for teams that already run standups, or for the ones trying to start? The copy says both, and I think it's really the first.
Ask a question the founder wants to answer
Who is it not for?
Congrats on shipping. Who is the person this is clearly NOT for? That usually tells me more than the feature list.
- Why it works:
- An unusual question with a short answer. Founders love being asked this and the reply often becomes positioning copy.
What did you cut?
Launch day! What was the feature you cut to make today happen? Asking because I'm about to cut one of mine.
- Why it works:
- A question about the decision, not the product, with your own reason for asking. It invites a story.
A pricing question, asked kindly
Signed up. One honest question: why monthly only? Not a complaint, I'm deciding the same thing for mine next month.
- When:
- You are curious about a choice they made and would like to learn from it.
- Why it works:
- States that you converted first, then asks. The disclaimer keeps it from reading as a dig.
What surprised you?
Live, finally. What's the first thing a real user did that you didn't expect? There's always one.
- Why it works:
- Every launch has an answer to this, and it is always a good story. Readers stay in the thread for it.
Compliment one specific thing
"Looks great" is a kind thing to say about a landing page and tells the founder nothing. Name the one element you noticed and why it worked on you. Those replies get screenshotted, quoted in the next post, and remembered when you launch something yourself.
The landing page
The landing page says what it does in one sentence under the logo. You have no idea how rare that is. Bookmarking for the next time I write mine.
- Why it works:
- A specific observation about craft, plus a reason it matters to you. The founder learns what to keep.
The demo video
Watched the whole 40-second video, which I never do. Starting on the problem instead of the UI is why.
- Why it works:
- Describes your own behaviour and the cause. That is feedback, not flattery.
The onboarding
Got to a real result in under two minutes without reading anything. Whoever fought for that empty state won.
- Why it works:
- A measurable experience and credit to a decision. Founders remember replies that notice the decisions.
The journey, not the product
Been watching this since the "should I even build this" post in June. Seeing it live is a small win for everyone who replied back then too.
- When:
- You followed the project from early posts.
- Why it works:
- Connects the launch to its history and includes the other early supporters. Warm without being empty.
Share it, with context
You know who needs it
Sending this to the three people who asked me last week how to track reply performance. This is the answer I didn't have.
- Why it works:
- Tells the founder their product solved a real question you had been asked, and tells readers who it is for.
You are already a user
Been on the beta for a month. The thing the screenshots won't show you: the scheduling calendar actually got me posting daily. Worth it for that alone.
- When:
- You used it before launch day.
- Why it works:
- An outcome from a real user is the most persuasive reply on any launch post. Say the specific outcome.
Product Hunt day
Upvoted, and left a comment about the pricing page because I think it's the best part. Good luck with the rest of the day.
- Why it works:
- Confirms the action, names what you praised and where, and wishes them well without a demand.
When something is broken or unclear
A bug report on launch day is a favour, if it is delivered as one. Say what broke, say where, and offer the details privately so the thread does not become a support queue. Founders fix launch-day bugs within the hour, and they remember who told them kindly.
You found a bug
Congrats! Small thing: the signup button on mobile Safari doesn't respond on first tap. Sending a screen recording by DM so this thread stays clean.
- Why it works:
- Congratulations first, the bug in one line, the evidence offered privately. Nothing to be embarrassed about in public.
Something confused you
Live and working here. One confusion: I couldn't tell whether "posts" in the plan limit includes replies. Might just be me.
- Why it works:
- Reports working first, then the confusion, then leaves room for it to be your mistake. That is how to deliver copy feedback.
When you build something similar
A competitor launches
Congrats from the other side of the same problem. Your import flow is better than mine, and I'm going to borrow the idea of showing the limit before the upload.
- When:
- You are building in the same space.
- Why it works:
- Generous, specific, and honest about taking an idea. Both audiences see a person who is secure about their own product.
A plain congratulations that still says something
Congratulations. Launch day for a solo founder is eight hours of refreshing a dashboard and answering DMs. Hope the dashboard moves.
- Why it works:
- No question, no compliment, just recognition of what the day actually is. Founders feel seen by it.
Writing your own launch reply
- 01Open the product before you reply. Thirty seconds on the landing page gives you something specific; the post alone does not.
- 02Pick one: a question about a decision, a compliment about one element, a share with a named reason, or a bug with evidence offered privately.
- 03Write it in two lines. Launch replies get read on a phone between DMs.
- 04If you converted, say so first. "Signed up" or "bought it" is the most useful thing a reply can start with.
- 05Come back a week later and reply to their follow-up post. Almost nobody does, and the founder notices who did.
Do
- Name the specific element you liked and what it did to you.
- Report bugs with congratulations first and the details in DM.
- Mention that you shared it with a specific person or group, when true.
Don't
- Do not pitch your own product in a reply to someone else's launch, even a related one.
- Do not ask a question the landing page answers in its first screen.
- Do not post "Congrats 🚀" and nothing else under a friend's launch. They know you can do better.
If you are the one launching soon, the replies above are also a list of what people will ask. Preparing answers for them is part of the plan in X growth for founders, and the posts that lead up to a launch, so that launch day is not the first time anyone hears of you, are in build in public post ideas.
BuzzyX · X growth workspace
Grow on X with posts that sound like you.
Compose in your voice, schedule the week, find posts worth replying to and read real analytics from the X API. $29/mo after the trial, everything included.
Frequently
asked questions
Something else on your mind? Get in touch.
Is a plain Congrats rude?
No, it is kind and the founder appreciates it. It is just forgettable. If you have ten seconds for one specific sentence, that sentence does more for them and for you.
Should I report a bug publicly on launch day?
Mention that there is one in a single kind line, and send the details privately. Public helps because other users hit the same bug; private keeps the thread from becoming a support queue on their biggest day.
What if I think the product is a bad idea?
Launch day is not the day. If you have a serious concern, send it privately or wait a week and ask a genuine question. A public takedown under a launch post makes you look worse than the product.
Can I mention that I build something similar?
Yes, briefly and generously. Say what they did better and what you will learn from it. Do not link your product, do not compare prices, and do not ask them to try yours.
Does replying to launches actually help my own account?
Launch posts draw founders and builders, which is a good audience for most people reading this. A specific reply gets profile visits from them and starts relationships with people who will launch again, and who remember who showed up.