On this page
A good launch post says what you built, who it is for and why you built it, in the voice of a person rather than a brand, then asks for something specific: try it, give feedback, or share it. On X keep it short with one link and an image. On LinkedIn tell the story behind the product. On Reddit follow each subreddit's rules and lead with something useful. On Show HN describe the product plainly, make it easy to try, and stay to answer questions. Below are structures and templates for each.
What every launch post needs
Whatever the channel, the same five parts carry a launch post:
- The hook. One line on the problem or the result. Your tagline often works here; our guide on writing a product tagline helps.
- What it is. One or two sentences, plain words, no jargon.
- Why you made it. The honest reason. People connect with makers, not features.
- Proof it works. A screenshot, a short video, or a demo link.
- The ask. One clear action, such as "try it and tell me what is confusing".
Write the posts a few days before launch day, so on the day you only have to publish and reply. Tag each link with the UTM builder so you can see later which channel brought users.
Writing for X
Posts on X are short and scroll by fast. Lead with the hook, keep the main post to a few lines, and attach an image or short video of the product. Put the link in the post, or in a reply if you prefer to keep the first post clean.
A simple structure
I just launched [product]: [what it does for whom].
I built it because [honest reason].
It is free to try: [link]
I would love feedback on [specific thing].
If you want to say more, use a short thread: one post per point, each one useful on its own. Reply to every response, and thank people who share. Make sure your link preview looks right first, as covered in Open Graph images and link previews.
Writing for LinkedIn
LinkedIn readers respond to stories and lessons. A launch post there works best as a short personal story: the problem you saw at work, what you tried, what you built, and what you learned. Break the text into short paragraphs so it is easy to read on a phone.
A structure for the post body
- Open with the problem in one or two lines, from your own experience.
- Explain what you built and who it helps.
- Share one honest lesson from building it.
- Add a screenshot or short video.
- End with a clear ask and the link.
Tag people only when they were genuinely involved. Mass tagging looks like spam.
Writing for Reddit
Reddit is a collection of communities, each with its own rules and moderators. Many subreddits ban self promotion or allow it only on certain days or in certain threads. Before you post, read the rules in the sidebar, look at what has been posted recently, and check whether the community has a dedicated thread for showing projects.
What tends to work
- A title that describes the problem or the thing you made, not a sales line.
- A body that shares how you built it, what you learned, or a free resource, with the link as a natural part of the post.
- Being clear that you are the maker.
- Answering every comment, including the critical ones, calmly.
Do not post the same text in many subreddits at once. It often gets removed and can get your account limited.
Writing for Show HN
Show HN is the section of Hacker News for sharing something you made that people can try. Read the Show HN guidelines on the site before you post. In short, it should be something people can use or play with, not a sign up page or a blog post, and you should be around to discuss it.
Title and first comment
Titles start with "Show HN:" followed by the name and a plain description, such as:
Show HN: [Product], [plain description]Keep the description factual and free of marketing words. Then add a first comment that explains what it is, why you made it, how it works technically, and what feedback you want. Readers there appreciate technical detail and honesty about limitations.
Make it easy to try
Remove sign up barriers where you can. A demo account, a playground or a public example goes a long way. Expect direct criticism, take what is useful, and reply politely.
A side by side view
| Channel | Length | Tone | Main ask |
|---|---|---|---|
| X | A few lines, optional thread | Direct, personal | Try it, share it |
| Short story in paragraphs | Reflective, professional | Try it, tell a colleague | |
| Depends on the subreddit | Helpful, community first | Feedback | |
| Show HN | Plain title, detailed comment | Technical, honest | Try it, discuss it |
Connecting your posts to your launch
On your launch day, link to your Product Launch Day listing as well as your site, so people can comment and vote there. Remember that votes are weighted: accounts made on launch day count 0 and accounts under 7 days old count 0.5, with one vote per account. So the honest ask is "take a look and tell me what you think", not "please make an account and upvote". The rules explain the details, and the launch day playbook shows how these posts fit into the whole day. When you are ready, start your listing on the submit page.
Questions people ask
Should I post on every channel on the same day?
You can, but only if you can keep up with the replies. Many makers post on X and LinkedIn on launch day, then post on Reddit and Show HN on separate days, so they can give each conversation full attention.
Can I ask for upvotes in my launch post?
It is better not to. Many communities forbid it, and on Product Launch Day new accounts count little or nothing toward votes. Ask people to try the product and leave feedback instead.
What if my Show HN post gets no attention?
That is common and not a verdict on your product. Focus on the other channels, improve the product with the feedback you do get, and share again later when you have something new for people to try.
Should I write the post myself or use AI?
Use AI for drafts if it helps, but rewrite the result in your own voice. Readers on all of these channels respond to a real person explaining what they made and why, and they notice generic text.
