A Twitter thread is still the best format on X for explaining a product that is new, a little abstract, and needs more than one sentence to make sense. That describes most AI products. The trouble is that most threads written by founders read like a landing page chopped into pieces. Feature, feature, feature, link. Nobody reads past post two. This play covers how to write a Twitter thread that people actually finish, and that leaves them wanting to try what you built.
What a selling thread is for
A thread that sells does not try to close anyone. Before launch, there is nothing to buy yet. The job of the thread is to move a reader one step: from “never heard of this” to “I want to be told when this is ready”. That step is a follow or a waitlist signup.
To get there, the reader has to believe two things by the end. First, that you understand their problem better than they expected. Second, that your product is a sensible answer to it. Everything in the thread serves one of those two beliefs. Anything that does not gets cut.
If your thread would make sense with a competitor’s name swapped in, it is not about your product. It is about the category.
The structure of a Twitter thread that sells
Here is the shape we use for almost every product thread. Six to ten posts.
- Hook. One specific claim or observation the reader has not heard put this way.
- Problem. The painful, concrete version of the problem, in the reader’s words.
- Why it is hard. Why the obvious fixes do not work. This is where you show you know the space.
- Insight. The thing you figured out that makes a better answer possible.
- Proof. A screen recording, a before and after, or a real number from testing.
- What it means for the reader. The practical outcome, not the feature.
- Ask. One action. Join the waitlist, or follow for the build.
Posts three and four do the selling. Most founders skip straight from problem to product, and the product feels like an ad. The insight is the bridge.
Write the hook last, but write five of them
Your first post decides whether anyone reads the second. Write the body first, so you know what you are actually saying, then write five hooks and pick the best.
Good hooks are specific. Weak hooks are vague and promise a lot. For a hypothetical AI tool that turns sales calls into CRM updates:
- Weak: “AI is changing sales forever. Here is how.”
- Better: “Sales reps spend their Friday afternoons typing call notes into the CRM. We timed it. Then we tried to make it zero.”
- Weak: “We built something big. A thread.”
- Better: “Every CRM is full of deals that say ‘follow up next week’ and nothing else. Here is why that happens and what we are doing about it.”
The better versions name a person, a moment and a problem. A reader knows within one line whether this is for them.
An illustrative X thread, written by us
Here is a full example for the same hypothetical sales call tool. It is written to show the structure, not copied from a real account.
1/ Sales reps spend their Friday afternoons typing call notes into the CRM. We timed it across a few teams. Then we tried to make it zero.
2/ The problem is not laziness. After six calls in a day, nobody remembers what the third customer said about budget. So the notes get short. “Good call. Follow up.”
3/ Call recorders do not fix this. They give you an hour of transcript, and nobody reads a transcript on a Friday.
4/ What we noticed: managers only use about five fields from each call. Next step, budget, timeline, blockers, who else is involved. Everything else is noise.
5/ So we stopped summarising calls and started filling in those five fields directly. Here is a 20 second recording of it updating a deal from a real test call. [video]
6/ The point is not saving time on notes. It is that the pipeline review on Monday finally reflects what customers actually said.
7/ We are opening early access in a few weeks. If your team lives in a CRM and hates updating it, the waitlist is in my bio.
Notice what is not here: a feature list, a pricing hint, or the word “revolutionary”. More annotated versions live in our thread examples.
The proof post does more selling than every other post combined. Spend half your time on it.
Formatting rules that keep people reading
- One idea per post. If a post needs “and also”, split it.
- Short lines. White space is your friend on a phone screen.
- Numbering posts with “1/” is optional. Either style works; pick one and stay with it.
- Put media in the proof post, not the hook. A video in post one gets watched and the thread gets skipped.
- Leave the link out of the first post. Put it in the last post or in a reply.
After you post
The first two hours matter. Stay on the app. Reply to every comment with something real, not a thank you emoji. Each reply puts the thread back in front of people.
Then, a day later, quote your own thread with one new angle. A thread that did well deserves a second push. One that did badly tells you the hook or the problem missed, and that is useful too. Rewrite it in two weeks with a new hook.
Threads also need an account people trust. If yours is brand new, the play on how AI founders grow on X before launch covers the groundwork, and the 30 day posting calendar slots one thread into every week.
When the threads are not landing
If you have written four or five threads and none of them get replies, the issue is usually not the writing. It is the problem you picked, or the profile people land on when they click your name. Our free X account teardown looks at both and tells you which one to fix first.