How to Write a Launch Thread That Actually Gets Read

Most launch threads are brochures cut into pieces. "1/ Excited to announce..." - and the reader is gone before post two. The threads that get read are built like serialized argument: each post earns the next one, and the whole thing ends with the reader knowing exactly what to do. Here's the anatomy, then the template.

Why threads beat single posts for launches

A single launch post competes on one scroll-stop; a thread competes on narrative attention. The reader who taps "show this thread" has opted into reading more - the format's entire value is that you now have somewhere to put the details a stranger would never stop for: the problem, the mechanism, the terms, the proof. The single post can only gesture; the thread can demonstrate.

But the gesture still matters. Post one is the whole funnel - it does all the deciding. Which is why "Excited to announce" fails: it announces an emotion, not a reason.

The five-post structure

Post 1 - the stakes. What's being contested and why it matters, in the first sentence. Score, day, deadline, the two sides - anything with a live number in it beats anything abstract. If you're launching into a public contest, the contest itself is the hook: "It's 74–69 on day four. One seat, one vertical, and the crowd decides."

Posts 2–3 - the pitches, verbatim. This is the part founders sand the edge off, and shouldn't. Your product's one-liner, in your own words - and if you're in a head-to-head, the rival's too, framed fairly. A launch thread that quotes the competition honestly reads like someone with nothing to hide, because that's what it is. (On this board, a duel page renders exactly this - both taglines in the founders' own words - because the crowd judges the pitches, not the adjectives around them.)

Post 4 - the rules. How this gets decided and when. Not your internal roadmap - the external clock: what number ends the contest, what happens to the runner-up, when it all resolves. Deadlines convert maybes; vagueness loses them.

Post 5 - the ask, with the link. One action, stated plainly: watch it end, cast the deciding vote, take a seat. Not "we'd love your feedback" - that's a post for existing users. The launch ask is for attention, and it should sound like it.

The trap almost every founder thread falls into

The thread about the thread. "We're so humbled by the response to our launch 🧵 (1/9)" - writing the victory lap before the race. Every post spent on your emotions is a post not spent on the reader's reason to care. The reader's internal question is what does this have to do with me - answer it in post one and every post after.

The second trap is the opposite: the thread that's all hype and no artifacts. Real numbers, real quotes, real deadlines - the things a skeptical reader can check. A thread made entirely of adjectives is a brochure, and brochures get scrolled.

A template you can steal

1/ [The live stakes - score, contest, deadline, link] 2/ The challenger: "[one-liner, verbatim]" - [one sentence of honest context] 3/ The holder: "[one-liner, verbatim]" - [one sentence of honest context] 4/ The rules: [what decides it] · [when it resolves] · [what the runner-up pays] 5/ The chair goes to [the crowd/the market/whoever]. Watch it end - or decide it: [link]

On a live duel, this board's thread writer renders all five posts from the live state - score, both pitches, rules, ask - so the copy is always current and the claims are always the machine's numbers, not the founder's. The same structure works for any launch: replace "score" with your real traction, "rules" with your real terms, and keep the discipline of verbatim pitches.

When to post it

Day one of whatever window you're in, and again at the moment of highest tension - not on a schedule, on the news. A tied score with hours left is worth a re-thread; a quiet Tuesday is not. Threads age in days; stakes age in hours. For the full week-around-the-thread plan, see the duel week playbook - and for the single-post version, the trailer: how the 90-second cut works.