What a launch post is for
A launch post has two readers: the person scrolling past, who needs to know in one line what you made, and the person who stops, who wants the story and a reason to try it. The title or tagline serves the first. The post and your first maker comment serve the second. The comment is where you’re a person, not a product page: why you built it, what’s free, and what you want to hear back.
Each platform reads differently
- Show HN. For things people can try: the Show HN rules exclude landing pages and sign-up pages. Titles start with “Show HN:”. Plain language and technical detail do better than marketing copy.
- Product Hunt. A short tagline, a description of up to 260 characters and a maker comment that starts the conversation.
- Reddit and Indie Hackers. Community first. Say you’re the maker, share what you learned, and check each community’s rules on self-promotion before you post.
- LaunchRanked. A tagline and a third-person description for your permanent product page, plus a maker comment. Weeks run Monday to Sunday (UTC), and a human reviews every listing. Plan the week with the launch week calendar.
How the generator works
You pick a platform and a tone and describe the product. We send your input to Llama 3.3 70B on Cloudflare Workers AI with that platform’s format and length targets, and rules against invented numbers, testimonials and vote requests. We check the result: Show HN titles get their prefix, Product Hunt descriptions are trimmed to 260 characters at a sentence end, and any sentence asking for votes is removed.
Make the draft yours
- Replace every [placeholder] with a real detail, or delete it.
- Add one thing only you know: the moment you decided to build it, or a result from an early user who said you could share it.
- End with a specific question. “Would you use this for X or Y?” gets answers; “Thoughts?” rarely does.
- Plan to reply to every comment on launch day. That matters more than the post itself.