How to Write a Launch Thread That Doesn't Read Like an Ad
The structure of a launch thread people actually read: open with the problem, show the work, name the trade-offs, and put the link where it belongs.
Published 2026-10-30 · 3 min read
A launch thread is read by a few hundred people and skimmed by thousands more. The skimmers decide in the first line whether you are describing something or selling something, and once they decide it is the second, nothing later will change their mind.
The difference is structural, not tonal. These threads read as selling because of where the link is and what precedes it, not because the words are too enthusiastic.
The structure that works
- 1
Open with the problem, stated specifically
Not "excited to announce". A concrete situation someone recognises: "Turning an hour of podcast into clips took me four hours a week, and half the clips were unusable." The reader should nod before they know what you built.
- 2
Say what you tried before
The alternatives and why they failed. This is where credibility is established, because it shows you are comparing against real options rather than against nothing.
- 3
Show the thing working
A screenshot, a short clip, a before-and-after. Something observable. Descriptions of features do not survive skimming; evidence does.
- 4
Name what it does badly
One genuine limitation. This is the single highest-leverage line in the thread — it converts the reader from evaluating a pitch to evaluating a product, and it makes every other claim more believable.
- 5
Say who it is for, and who it is not for
Explicit disqualification. "Not for teams that need on-prem" tells the right people the thread is about them and lets the wrong ones leave without resenting you.
- 6
Put the link, once, near the end
After the thread has earned it. A link in the first post tells the reader the whole thing is an advertisement before they have read any of it.
Line by line
| Position | Should contain | Should not contain |
|---|---|---|
| Post 1 | The problem, in a buyer's words | The product name, a link, "excited to" |
| Post 2 | What you tried and why it failed | Competitor bashing |
| Post 3 | Evidence it works — image or clip | A feature list |
| Post 4 | The limitation and who it is not for | Hedging that hides the limitation |
| Post 5 | What it is, one sentence, with the link | A second pitch for why it is great |
| Post 6+ | Answers to questions as they arrive | Anything pre-written |
The four phrases that make a thread read as an ad
- "Excited to announce." It signals that the post exists to serve you. Open with the reader's situation instead.
- "Game-changing" / "revolutionary" / "the future of". These carry no information, and their presence tells the reader you have nothing specific to say.
- A list of features without a problem. Features are answers; a reader who has not seen the question has no way to evaluate them.
- "Link in bio" or a link in post one. Both announce the commercial intent before any value has been delivered.
What to do with the replies
The thread is half the work. The replies are where the actual outcome happens, and where most founders disappear.
- Answer every question, including the hostile ones. A calm, specific reply to a sceptic is read by everyone else in the thread and does more than any edit to the original post.
- Do not argue about the limitation. If someone says the missing feature matters, agree and say when or whether you plan to address it. Defending it converts nobody.
- Note the questions you keep getting. Three people asking the same thing is a gap in the thread, in your landing page, or in the product.
- Reply to replies for at least 48 hours. Threads keep circulating well after the first hour, and a dead comment section is visible.
Adapting it per platform
| Platform | What changes |
|---|---|
| X / Twitter | Thread format as above. First post carries the whole thing — most people never expand |
| No thread. One post, longer, with the image inline. Fewer, longer paragraphs; the audience tolerates more context | |
| Indie Hackers | Add the numbers and the timeline. This audience specifically wants the story of how it was built, not just what it is |
| A community forum | Rewrite entirely for that community's topic. Pasting the thread is the fastest route to removal |
| Hacker News | Do not post a launch thread. Post the technical detail as a first-person account, or submit the product and let the comments happen |
A launch thread is not an announcement. It is an argument that a specific problem deserves a specific solution, and the product is the evidence.
More in Content & building in public
- How to Get Your First 10 Newsletter MentionsNewsletters are a reachable audience for a new AI product. How to get mentioned in ten of them: finding the right ones, becoming a source, and pitching.
- Case Studies for AI Products: A Template Founders Can CopyA case study structure that works for a solo founder with one or two users: the six sections, what evidence each needs, and how to get permission.
- Repurposing Your AI Product Launch Across 6 ChannelsOne launch, six surfaces: how to cut the same material for a blog, a thread, LinkedIn, a community, listings and a pitch without repeating yourself.