How to write a launch thread on X (for Product Hunt day and beyond)
By Naod Tadele · · 5 min read
Launch day posts usually ask for something before giving anything: "We're live, please support us!" The people who already love you click. Nobody else does.
A good launch thread makes strangers care first, then asks.
The structure
Post 1: the hook. What it does, for whom, in one or two lines. Add your best screenshot or a short video.
Post 2: the problem. Why you built it. Be specific about the pain.
Post 3: how it works. Three steps, or the one feature that makes it different.
Post 4: the proof. Something real: a beta user's quote you have permission to use, a number from the beta, or what you used it for yourself.
Post 5: the story. How long it took, what was hard, what you cut. This is the one people reply to.
Post 6: the ask. Now ask: try it, give feedback, or support the launch. One ask, with the link.
An example
I built Nightshift: one incident summary in Slack instead of 40 pings at 3am. For on-call engineers at small teams.
Why: I was on call for 2 years. The worst part wasn't fixing things. It was 40 alerts for one problem.
How it works: connect your alerts, Nightshift groups them into one incident, and posts one summary with what changed.
In the beta, 14 teams used it for a month. The most common reply was "I slept through a bad night for once."
It took 5 months. I rewrote the grouping logic twice. The first version grouped everything into one giant incident.
It's free to start. If you're on call, I'd love your feedback: [link]
Tips for launch day
- Write it the day before. Launch day is chaos.
- Put the link at the end, or in a reply. Lead with value.
- Reply to every comment for the first few hours.
- Post more than once. A launch thread in the morning, a "what I learned on launch day" post in the evening.
- Don't beg for upvotes. Ask for feedback. The upvotes follow interest.
After launch
Launch day is one day. What brings users in the weeks after is posting what you shipped next. A steady drumbeat of real updates is what turns launch-day visitors into customers. Loudcode drafts those updates from your commits and revenue, so the drumbeat doesn't stop when launch week ends.