Templates

25 Twitter thread templates, with examples

Thread frameworks for X that founders and experts can fill in fast. Each has an outline, a written example numbered n/N, and every post under 280 characters.

Updated

On this page
  1. How a good thread works
  2. 25 thread templates
  3. Questions

How a good thread works

  • The first post does the selling. It says what the reader gets and why you can tell them.
  • One idea per post. Each one should make sense if it is the only one someone reads.
  • Number it. "3/7" tells people how far they are and that the end is near.
  • End with a job for the reader. A recap, a question, or a thing to try this week.

25 thread templates

Every example is written for this page with made up details. None is a real person's thread.

01

The lesson list

7 posts

Share what a stretch of work taught you, one lesson per post.

Outline
1/7 [Number] lessons from [time or project]. The last one changed how I [do the work].
2/7 Lesson 1: [lesson]. [One line of what happened].
3/7 Lesson 2: [lesson]. [One line of what happened].
4/7 Lesson 3: [lesson]. [One line of what happened].
5/7 Lesson 4: [lesson]. [One line of what happened].
6/7 Lesson 5: [the lesson that changed your approach]. [What you do now].
7/7 If you are [in the same spot], start with lesson [number]. Follow for more on [topic].
Written example
  1. 5 lessons from 3 years of running a small design studio. The last one changed how I price every project. 1/7109 / 280
  2. Lesson 1: The first call decides the whole project. When I rushed it, we spent weeks fixing the wrong problem. Now I spend a full hour on it and ask more than I talk. 2/7171 / 280
  3. Lesson 2: Write the scope down before you start. A client once asked for "a few small changes." It was 40 hours of work. A one page scope would have saved us both. 3/7168 / 280
  4. Lesson 3: Slow clients are usually busy, not unhappy. I used to panic when a reply took a week. Now I send one friendly nudge and get on with my day. 4/7154 / 280
  5. Lesson 4: Your best clients come from your last good project. Almost all of our work this year came from two people telling their friends about us. 5/7152 / 280
  6. Lesson 5: Charge for the result, not the hours. When I billed hourly, getting faster cut my pay. Now I price the outcome and getting faster is my reward. 6/7158 / 280
  7. If you run a small studio, start with lesson 5. It fixed more than the other four together. Follow for more on running a lean service business. 7/7148 / 280

Why it works. Each post stands alone, so readers can skim and still get value. Teasing the last lesson in the hook gives people a reason to keep going.

02

The teardown

7 posts

Break down a page, email or product and show what works and what does not.

Outline
1/7 I took apart [thing] to see why it [works or fails]. Here is what I found.
2/7 First, the [part 1]. [What it does well or badly].
3/7 Then the [part 2]. [What it does well or badly].
4/7 The [part 3] is where it [wins or loses]. [Why].
5/7 One small detail most people miss: [detail].
6/7 What I would change: [fix].
7/7 The takeaway for your own [thing]: [lesson].
Written example
  1. I took apart a landing page that turns 1 in 8 visitors into a trial. It breaks half the rules people teach. Here is why it still works. 1/7140 / 280
  2. First, the headline. It is only six words and it names the pain, not the product. "Stop chasing invoices every Friday." You know right away if this is for you. 2/7164 / 280
  3. Then the image. It is not a glossy mockup. It is a real screen with a real invoice marked paid. It shows the moment of relief, not the feature. 3/7148 / 280
  4. The pricing section is where it wins. One plan, one price, one button. No table with twelve rows. Nothing to compare, so nothing to stall on. 4/7146 / 280
  5. One small detail most people miss: the button says "Send my first invoice" instead of "Start free trial." It describes the first thing you will do, not the deal. 5/7166 / 280
  6. What I would change: the testimonials sit too far down. Most people will never scroll that far. I would put one short quote right under the button. 6/7152 / 280
  7. The takeaway for your own page: name the pain, show the relief, and make the next step feel small. That is most of the job. 7/7128 / 280

Why it works. Teardowns teach through a real example, which is easier to follow than theory. Readers also get a checklist they can run on their own work.

03

How I did X

7 posts

Walk people through how you reached a specific result, step by step.

Outline
1/7 How I [got result] in [time frame], without [common thing people assume you need].
2/7 Where I started: [starting point].
3/7 Step 1: [what you did first and why].
4/7 Step 2: [what you did next].
5/7 Step 3: [the step that made the biggest difference].
6/7 What did not work: [thing you tried and dropped].
7/7 The result: [outcome]. If I did it again, I would [change].
Written example
  1. How I got my first 20 paying clients in 4 months, with no ads and no audience. 1/782 / 280
  2. Where I started: a new bookkeeping practice, zero clients, and about 200 contacts from my old job. No website yet. Just a name and a plan. 2/7143 / 280
  3. Step 1: I wrote to 30 old coworkers. Not to sell. Just to say what I was doing and ask who they knew that hated their books. 11 wrote back. 4 sent intros. 3/7159 / 280
  4. Step 2: I offered a free 20 minute books review. I found at least one real problem in every single one. People trust you fast when you find money they are losing. 4/7167 / 280
  5. Step 3 made the biggest difference: I asked every new client for one intro in the first month, while they were happiest. That alone brought in 9 of the 20. 5/7160 / 280
  6. What did not work: a local networking group. I went 6 times and got one lead, who never paid. The room was full of people selling, not buying. 6/7147 / 280
  7. The result: 20 clients by month 4, all from people I already knew or their friends. If I did it again, I would ask for intros from day one, not month two. 7/7159 / 280

Why it works. A clear result in the hook earns attention, and the step by step format makes it easy to copy. Sharing what failed makes the whole thread more believable.

04

The mistakes thread

7 posts

Share mistakes you made so others can skip them.

Outline
1/7 I made [number] mistakes [doing thing] that cost me [time or money]. Here they are so you do not have to.
2/7 Mistake 1: [mistake]. What it cost: [cost].
3/7 Mistake 2: [mistake]. What it cost: [cost].
4/7 Mistake 3: [mistake]. What it cost: [cost].
5/7 Mistake 4: [mistake]. What it cost: [cost].
6/7 The pattern behind all of them: [root cause].
7/7 What I do now instead: [new habit]. Which one have you made?
Written example
  1. I made 4 mistakes in my first year selling software that cost me about 8 months. Here they are so you can skip them. 1/7121 / 280
  2. Mistake 1: I built for 6 months before talking to a single buyer. What it cost: half the features I built, nobody wanted. I deleted them in one afternoon. 2/7159 / 280
  3. Mistake 2: I priced at $9 a month because I was scared. What it cost: I needed 900 customers to pay myself. At $49 I needed less than 200. 3/7143 / 280
  4. Mistake 3: I said yes to every feature request. What it cost: a product that did 20 things badly. New users could not tell what it was for. 4/7144 / 280
  5. Mistake 4: I stopped writing to my email list when I got busy. What it cost: when I came back 3 months later, most people had forgotten who I was. 5/7151 / 280
  6. The pattern behind all of them: I avoided the hard, awkward conversations. With buyers, about price, about saying no. 6/7122 / 280
  7. What I do now: one hard conversation every day before I write any code. Which of these have you made? 7/7106 / 280

Why it works. Mistakes feel honest and useful at the same time. Putting the cost next to each one shows the stakes without any hype.

05

Myth vs fact

7 posts

Correct common beliefs in your field with what you have seen.

Outline
1/7 [Number] things people believe about [topic] that do not match what I see. Myth vs fact:
2/7 Myth: [belief]. Fact: [what you have seen].
3/7 Myth: [belief]. Fact: [what you have seen].
4/7 Myth: [belief]. Fact: [what you have seen].
5/7 Myth: [belief]. Fact: [what you have seen].
6/7 Why these myths stick around: [reason].
7/7 The one fact I would tattoo on every [role]: [fact].
Written example
  1. 4 things people believe about hiring a freelancer that do not match what I have seen in 6 years of doing it. Myth vs fact: 1/7127 / 280
  2. Myth: The cheapest quote saves you money. Fact: The cheapest quote usually has the most rework. I have paid twice for the same job more than once. 2/7151 / 280
  3. Myth: A big portfolio means they are good. Fact: Ask what part of each project they did themselves. Many portfolios show team work. 3/7136 / 280
  4. Myth: You need a long contract. Fact: A one page scope with dates and a price has kept me out of trouble more than any 12 page contract. 4/7141 / 280
  5. Myth: Good freelancers are always booked. Fact: Many good ones have gaps between projects. Ask. You might get someone great next week. 5/7139 / 280
  6. Why these myths stick around: most people hire a freelancer once or twice a year, so they never get enough reps to see the pattern. 6/7135 / 280
  7. The one fact I would tell every first time buyer: clear scope beats low price every single time. Write down what done looks like before you hire. 7/7150 / 280

Why it works. The myth vs fact pattern creates small moments of surprise in every post. It also positions you as someone with real reps in the field.

06

The step by step guide

8 posts

Teach a process from start to finish in numbered steps.

Outline
1/8 How to [do task] in [number] steps, even if [common worry].
2/8 Step 1: [step]. [Short tip].
3/8 Step 2: [step]. [Short tip].
4/8 Step 3: [step]. [Short tip].
5/8 Step 4: [step]. [Short tip].
6/8 Step 5: [step]. [Short tip].
7/8 Common mistake to avoid: [mistake].
8/8 Save this for the next time you [do task].
Written example
  1. How to run a customer interview in 5 steps, even if you hate cold calls. 1/876 / 280
  2. Step 1: Ask for 20 minutes, not 30. Small asks get more yeses. Most calls run long anyway if they are going well. 2/8118 / 280
  3. Step 2: Start with their day, not your product. "Walk me through the last time you did this." Then stay quiet and let them talk. 3/8133 / 280
  4. Step 3: Ask about the past, not the future. "Would you use this?" gets polite lies. "What did you do last week?" gets the truth. 4/8133 / 280
  5. Step 4: Dig into anything they paid for. Time or money spent is the best sign of a real problem. Ask what they tried and why they stopped. 5/8143 / 280
  6. Step 5: End with one question. "Who else should I talk to?" Half my interviews come from this line. 6/8104 / 280
  7. Common mistake to avoid: pitching at the end. The second you pitch, they switch from teacher to polite guest. Save it for a later call. 7/8140 / 280
  8. Save this for your next round of customer calls. 8/852 / 280

Why it works. Numbered steps are easy to follow and easy to save. A clear promise in the hook tells people exactly what they will get.

07

The tools I use

7 posts

Show your working setup and why each piece earns its place.

Outline
1/7 The [number] tools I use to [do job] as a [role]. None of them are fancy.
2/7 For [task 1]: [type of tool]. Why: [reason].
3/7 For [task 2]: [type of tool]. Why: [reason].
4/7 For [task 3]: [type of tool]. Why: [reason].
5/7 For [task 4]: [type of tool]. Why: [reason].
6/7 What I stopped using: [tool type] because [reason].
7/7 The rule I follow: [rule for picking tools].
Written example
  1. The 5 tools I use to run a one person consulting business. None of them are fancy. That is the point. 1/7106 / 280
  2. For notes: a plain text notes app. One file per client. I can search 4 years of calls in two seconds. 2/7106 / 280
  3. For scheduling: a simple booking link. It saved me about 3 emails per meeting. Over a year that is hundreds of emails I never wrote. 3/7137 / 280
  4. For invoices: the invoicing feature in my bank. No extra login. Money lands in the same place I send the bill from. 4/7120 / 280
  5. For writing: a paper notebook first, then a doc. I think better with a pen. The doc is just where the clean version goes. 5/7126 / 280
  6. What I stopped using: a big project board. I spent more time moving cards than doing the work. A simple list does the job. 6/7127 / 280
  7. The rule I follow: if I cannot explain why I need a tool in one sentence, I do not keep it. 7/795 / 280

Why it works. People love seeing how others work, and a lean setup feels doable. The rule at the end gives readers something to take away even if they use different tools.

08

The case study

7 posts

Tell the story of one client or project from problem to result.

Outline
1/7 [Client type] came to me with [problem]. [Time] later, [result]. Here is what we did.
2/7 The situation: [context and stakes].
3/7 What they had tried: [past attempts].
4/7 What we found: [real cause].
5/7 What we changed: [the fix].
6/7 What happened: [result with details].
7/7 What you can take from this: [lesson]. [Soft call to action].
Written example
  1. A small bakery came to me losing money on every wedding cake. 3 months later, cakes were their best margin. Here is what we did. 1/7133 / 280
  2. The situation: Fernhill Bakery sold about 8 wedding cakes a month. They were busy every weekend but the bank account kept shrinking. 2/7136 / 280
  3. What they had tried: raising prices by 10 percent. They lost 2 bookings and still lost money on the rest. 3/7109 / 280
  4. What we found: the price was fine. The problem was tastings. They gave free tastings to every couple, and most tastings did not turn into orders. 4/7150 / 280
  5. What we changed: tastings now cost $40, taken off the cake if you book. We also cut the flavor menu from 14 to 6. 5/7118 / 280
  6. What happened: tastings dropped by half, but bookings stayed the same. Baking waste went way down. Cakes went from a loss to their best margin. 6/7148 / 280
  7. What you can take from this: before you raise prices, look for the hidden cost. If you want a second pair of eyes on yours, my notes are always open. 7/7154 / 280

Why it works. A before and after story with a clear cause is the most convincing thing an expert can post. It shows your thinking, not just your claim.

09

The build in public update

7 posts

Share an honest progress update on something you are building.

Outline
1/7 [Product] update, [time period]. [One honest headline about how it went].
2/7 What shipped: [features or changes].
3/7 The numbers: [simple fictional metrics].
4/7 What went well: [win].
5/7 What went badly: [problem].
6/7 What I am changing: [plan].
7/7 Next [period] goal: [goal]. I will report back.
Written example
  1. Month 7 update on Quarry, my scheduling tool for small clinics. Short version: more users, less money. Here is why. 1/7120 / 280
  2. What shipped: text reminders, a new calendar view, and a way to block lunch breaks. The lunch break one came from a single email. It is now the most used setting. 2/7167 / 280
  3. The numbers: 64 clinics using it, up from 51. Monthly revenue went from $2,900 down to $2,700. 3/798 / 280
  4. What went well: people who try the text reminders almost never leave. Only 1 of them cancelled this month. 4/7110 / 280
  5. What went badly: I ran a half price promo. It brought in cheap signups and 4 old customers asked to switch to the lower price. I said yes. That was the drop. 5/7162 / 280
  6. What I am changing: no more discounts. I would rather grow slower with people who value it. 6/795 / 280
  7. Goal for month 8: back above $3,000 and 70 clinics. I will report back either way. 7/787 / 280

Why it works. Honest updates build trust over time because readers see the bad months too. A clear goal at the end brings people back for the next one.

10

The contrarian take

7 posts

Argue against popular advice in your field, with reasons.

Outline
1/7 Unpopular opinion: [common advice] is [wrong or overrated] for [who].
2/7 The usual advice: [advice as people say it].
3/7 Why it sounds right: [fair point].
4/7 Where it breaks: [problem].
5/7 What I have seen instead: [your experience].
6/7 What I do: [your approach].
7/7 When the usual advice does fit: [exception]. Where do you land?
Written example
  1. Unpopular opinion: "post every day" is bad advice for most consultants. I tried it for 90 days. Here is what happened. 1/7123 / 280
  2. The usual advice: show up daily, the algorithm rewards you, and volume beats quality. 2/789 / 280
  3. Why it sounds right: you do get better with reps. And you cannot be found if you never post. 3/796 / 280
  4. Where it breaks: consultants sell trust. My daily posts got thinner and thinner by week 3. People noticed. Two clients asked if I was OK. 4/7142 / 280
  5. What I saw instead: my 3 deep posts that month brought 5 calls. The other 27 brought zero. 5/794 / 280
  6. What I do now: 3 posts a week, each one about a real problem I solved that week. Fewer posts, more calls. 6/7110 / 280
  7. When daily posting does fit: if you are selling to a huge crowd, or you have a team. For a solo expert, depth wins. Where do you land? 7/7139 / 280

Why it works. A clear stance gets people to stop and think. Being fair to the other side keeps it from feeling like a hot take for its own sake.

11

The before and after

7 posts

Show a clear change and what caused it.

Outline
1/7 [Time] ago I [before state]. Now I [after state]. The change came from [number] things.
2/7 Before: [picture of the old way].
3/7 The moment I knew it had to change: [trigger].
4/7 Change 1: [change].
5/7 Change 2: [change].
6/7 Change 3: [change].
7/7 After: [picture of the new way]. [What you would tell your old self].
Written example
  1. A year ago I worked 60 hour weeks and still missed deadlines. Now I work 40 and ship early. It came down to 3 changes. 1/7123 / 280
  2. Before: I said yes to every call, answered email all day, and did deep work after 9pm. My best hours went to my inbox. 2/7123 / 280
  3. The moment I knew: I missed my daughter's school play for a client call that ended up being cancelled. 3/7106 / 280
  4. Change 1: no meetings before noon. Mornings are for the one task that moves the work forward. 4/797 / 280
  5. Change 2: email twice a day, at 12 and at 4. Nobody has ever complained. Not once. 5/787 / 280
  6. Change 3: I raised my rate and took on 2 fewer clients. Same income, fewer fires. 6/786 / 280
  7. After: 40 hour weeks, work shipped early, dinner at home. What I would tell my old self: being busy is not the same as being useful. 7/7137 / 280

Why it works. Readers can picture both states, so the change feels real. Breaking it into small changes makes it feel possible for them too.

12

The timeline story

7 posts

Tell how something unfolded over time, one milestone per post.

Outline
1/7 The full story of [thing], from [start] to [now].
2/7 [Date 1]: [what happened].
3/7 [Date 2]: [what happened].
4/7 [Date 3]: [the low point].
5/7 [Date 4]: [the turn].
6/7 [Date 5]: [where things are now].
7/7 What I would tell anyone at [early stage]: [lesson].
Written example
  1. The full story of my small agency, from a spare bedroom to a team of 6. It was not a straight line. 1/7104 / 280
  2. 2021: I quit my job and took one client, a friend's shop. I built their site from my spare bedroom for $1,500. 2/7114 / 280
  3. 2022: 9 clients, all from word of mouth. I hired my first contractor, Priya, to help with design. 3/7101 / 280
  4. Early 2023: our biggest client, 40 percent of revenue, left with 2 weeks notice. I had to cut my own pay to zero for three months. 4/7135 / 280
  5. Late 2023: I decided no client could ever be more than 15 percent of revenue again. We started posting our work every week. New leads started coming in. 5/7157 / 280
  6. Today: 6 people, 22 clients, and no single client above 12 percent. 6/771 / 280
  7. What I would tell anyone in year one: spread your risk before you need to. The client who pays the most can leave the fastest. 7/7131 / 280

Why it works. Stories with dates feel concrete and are easy to follow. A clear low point gives the thread tension and keeps people reading.

13

The checklist

7 posts

Give readers a list they can run before a common task.

Outline
1/7 My [number] point checklist before I [task]. I run it every time.
2/7 1. [Check]. [Why].
3/7 2. [Check]. [Why].
4/7 3. [Check]. [Why].
5/7 4. [Check]. [Why].
6/7 5. [Check]. [Why].
7/7 Bookmark this for your next [task].
Written example
  1. My 5 point checklist before I send any proposal. I started using it after losing a deal over one typo in a price. 1/7118 / 280
  2. 1. Is their problem in the first line, in their words? If the first line is about me, I rewrite it. 2/7104 / 280
  3. 2. Is there one clear price? When I give 3 options, people pick none. I give one, with one optional add on. 3/7112 / 280
  4. 3. Is the start date real? I check my calendar before I promise. A late start is the worst first impression. 4/7113 / 280
  5. 4. Did I say what is not included? This one line has prevented more fights than anything else I do. 5/7104 / 280
  6. 5. Did I read it out loud? You hear mistakes you cannot see. That is how I would have caught the typo. 6/7107 / 280
  7. Bookmark this for your next proposal. What is on your checklist that is not on mine? 7/789 / 280

Why it works. Checklists are practical and get saved a lot. The small story in the hook explains why the list exists.

14

The FAQ thread

7 posts

Answer the questions people ask you most, in one place.

Outline
1/7 The [number] questions I get most about [topic], answered.
2/7 Q: [question]? A: [answer].
3/7 Q: [question]? A: [answer].
4/7 Q: [question]? A: [answer].
5/7 Q: [question]? A: [answer].
6/7 Q: [question]? A: [answer].
7/7 Got a question I missed? Ask below and I will answer it.
Written example
  1. The 5 questions I get most about going freelance as a developer, answered in one place. 1/791 / 280
  2. Q: How much savings do I need? A: I had 6 months of costs saved. I used 4 of them before the work was steady. 2/7114 / 280
  3. Q: Where do the first clients come from? A: For me, old coworkers and managers. My first 3 clients were all people I had worked with. 3/7138 / 280
  4. Q: How do I set my rate? A: I took my old salary, doubled it, and divided by 1,000 billable hours. Then I raised it every 6 months. 4/7136 / 280
  5. Q: Do I need a niche? A: Not on day one. But by month 6 I noticed most of my good work was for clinics. Now that is all I do. 5/7130 / 280
  6. Q: What is the hardest part? A: The quiet weeks. Not the work itself. You have to keep selling even when you are busy. 6/7123 / 280
  7. Got a question I missed? Ask below and I will answer it. 7/760 / 280

Why it works. An FAQ thread answers what people already want to know, so it earns replies. It also saves you time the next time someone asks.

15

The glossary

7 posts

Explain the key terms in your field in plain words.

Outline
1/7 [Number] [topic] terms explained in plain English. No jargon.
2/7 [Term]: [plain meaning]. [Simple example].
3/7 [Term]: [plain meaning]. [Simple example].
4/7 [Term]: [plain meaning]. [Simple example].
5/7 [Term]: [plain meaning]. [Simple example].
6/7 [Term]: [plain meaning]. [Simple example].
7/7 Which term confused you the longest?
Written example
  1. 5 money terms every new founder hears in their first month, explained in plain English. 1/791 / 280
  2. Runway: how many months you can keep going before the money runs out. $60,000 in the bank and $10,000 spent a month means 6 months of runway. 2/7146 / 280
  3. Burn: how much money you spend each month beyond what comes in. If you earn $4,000 and spend $10,000, your burn is $6,000. 3/7127 / 280
  4. Gross margin: what is left from each sale after the direct cost of making it. Sell for $100, it costs $30 to deliver, your margin is 70 percent. 4/7149 / 280
  5. Churn: the share of customers who leave in a period. 100 customers at the start of the month, 5 leave, churn is 5 percent. 5/7127 / 280
  6. Payback: how long it takes to earn back what you spent to win a customer. Spend $300 to win someone paying $50 a month, payback is 6 months. 6/7145 / 280
  7. Which of these confused you the longest? For me it was burn. I thought it meant total spending for a whole year. 7/7117 / 280

Why it works. Plain definitions help beginners and signal that you know the field well. Each post is a small, useful bite people can save.

16

What I would do if I started over

7 posts

Share the plan you would follow if you had to start from zero today.

Outline
1/7 If I had to start my [business or career] from zero today, here is exactly what I would do.
2/7 Week 1: [first move].
3/7 Month 1: [next move].
4/7 What I would skip: [thing you did that was a waste].
5/7 What I would do much earlier: [thing you did late].
6/7 The one habit I would start on day one: [habit].
7/7 It would not be fast. But it would be [benefit].
Written example
  1. If I lost every client tomorrow and had to rebuild my coaching business from zero, here is exactly what I would do. 1/7119 / 280
  2. Week 1: write a list of 50 people I have helped in any way. Old coworkers, friends, past clients. Then message 10 a day to catch up. No pitch. 2/7147 / 280
  3. Month 1: run 5 free sessions on one narrow problem. For me, new managers handling their first hard conversation. Ask each one for a quote after. 3/7149 / 280
  4. What I would skip: a fancy website. My first site took 2 months and brought in nothing. A one page doc with 3 quotes works fine. 4/7132 / 280
  5. What I would do much earlier: raise prices. I waited 2 years. Every time I raised them, I got better clients, not fewer. 5/7124 / 280
  6. The one habit from day one: write down every question a client asks. That list becomes your posts, your offers and your talks. 6/7131 / 280
  7. It would not be fast. But in 6 months I would have a full calendar of the right people. 7/791 / 280

Why it works. This format packs years of lessons into a clear plan. Readers who are just starting can follow it almost word for word.

17

The resource roundup

7 posts

Share the kinds of resources that helped you most, and why.

Outline
1/7 The [number] things that taught me the most about [topic]. None of them cost much.
2/7 1. [Resource type]: [what you learned].
3/7 2. [Resource type]: [what you learned].
4/7 3. [Resource type]: [what you learned].
5/7 4. [Resource type]: [what you learned].
6/7 5. [Resource type]: [what you learned].
7/7 The best one was free: [which and why].
Written example
  1. The 5 things that taught me the most about sales as a founder. None of them were a course. 1/795 / 280
  2. 1. Sitting in on 10 calls with a friend who sells for a living. I learned that good sellers ask 3 times more questions than they answer. 2/7141 / 280
  3. 2. Reading my own call notes a week later. Painful. But I saw how often I talked over people at the exact moment they were about to say something useful. 3/7158 / 280
  4. 3. A book I read on negotiation. One idea stuck: silence after a price is fine. The next person who speaks usually gives something up. 4/7139 / 280
  5. 4. Losing deals and asking why. I emailed every lost lead for a year. About a third replied. Their answers rewrote my pitch. 5/7129 / 280
  6. 5. Selling something tiny on the side. A $20 template taught me more about pages and pricing than a year of theory. 6/7120 / 280
  7. The best one was free: asking lost leads why they said no. It costs one email and it hurts a little. Do it anyway. 7/7119 / 280

Why it works. Readers want shortcuts, and a curated list gives them one. Explaining what each resource taught you makes the list useful even without names.

18

The framework explainer

7 posts

Teach a simple model you use to make decisions.

Outline
1/7 I use a simple [number] part framework to decide [decision]. Here is how it works.
2/7 Part 1: [name]. [What it means].
3/7 Part 2: [name]. [What it means].
4/7 Part 3: [name]. [What it means].
5/7 How I use it: [example].
6/7 Where it fails: [limit].
7/7 Try it on your next [decision]. Follow for more on [topic].
Written example
  1. I use a simple 3 question test to decide which client work to say yes to. It has saved me from at least 5 bad projects this year. 1/7134 / 280
  2. Question 1: Pay. Does it meet my rate without a discount? If I have to talk myself into the price, it is already a no. 2/7123 / 280
  3. Question 2: People. Would I enjoy a 30 minute call with them every week? Bad fit people make good money feel bad. 3/7118 / 280
  4. Question 3: Proof. Will this give me a story or result I can share later? Good work you cannot talk about does not help you grow. 4/7134 / 280
  5. How I use it: I need 2 out of 3 to say yes. Last month a big project scored only Pay. I said no. Two weeks later a better one came in and I had room for it. 5/7161 / 280
  6. Where it fails: early on, you may need to say yes to Pay alone to keep the lights on. That is fine. Just know it is a trade. 6/7128 / 280
  7. Try it on the next project you are unsure about. Follow for more on running a service business with fewer headaches. 7/7121 / 280

Why it works. A named framework is easy to remember and share. Showing where it fails makes it more trustworthy.

19

The numbers recap

7 posts

Share the real numbers behind a project, with what they mean.

Outline
1/7 [Project] by the numbers after [time]. The most useful number is not the biggest one.
2/7 [Number]: [what it counts]. [What it means].
3/7 [Number]: [what it counts]. [What it means].
4/7 [Number]: [what it counts]. [What it means].
5/7 [Number]: [what it counts]. [What it means].
6/7 The number that matters most: [number and why].
7/7 What I am tracking next: [metric].
Written example
  1. My newsletter by the numbers after 1 year. The most useful number is not the subscriber count. 1/799 / 280
  2. 2,400: subscribers. Nice, but it grew slowly. About 200 a month. 2/768 / 280
  3. 52: issues sent. I did not miss a single week, even the week I was sick. That habit mattered more than any growth trick. 3/7124 / 280
  4. 46 percent: average open rate. It started at 61 percent. The drop came as I grew, which I am told is normal. 4/7112 / 280
  5. 31: replies to one issue, the one where I shared my worst client story. My how to posts get about 3 replies. 5/7113 / 280
  6. The number that matters most: 7. That is how many consulting clients came from the newsletter. It paid for the whole year many times over. 6/7143 / 280
  7. What I am tracking next: replies per issue. They seem to predict who becomes a client better than opens do. 7/7111 / 280

Why it works. Specific numbers inside a real story feel honest. Pointing to the one number that matters teaches readers what to watch.

20

Hiring lessons

7 posts

Share what you learned from hiring, good and bad.

Outline
1/7 I have hired [number] people. Here is what I wish I knew before the first one.
2/7 Lesson 1: [lesson]. [Story].
3/7 Lesson 2: [lesson]. [Story].
4/7 Lesson 3: [lesson]. [Story].
5/7 Lesson 4: [lesson]. [Story].
6/7 The question I now ask every candidate: [question].
7/7 Hiring is [short summary]. What is your best hiring lesson?
Written example
  1. I have hired 11 people for my small team. Here is what I wish I knew before the first one. 1/795 / 280
  2. Lesson 1: Write the job before you post it. My first hire had no clear goals. After 3 months, neither of us knew if it was working. 2/7136 / 280
  3. Lesson 2: A paid trial project beats a great interview. One candidate interviewed well and missed every deadline in the trial. Another was quiet and did great work. 3/7169 / 280
  4. Lesson 3: Hire for the next year, not the next week. When I hired in a panic, I hired for today's fire. Those hires did not last. 4/7134 / 280
  5. Lesson 4: Check references by asking one question. "Would you hire them again?" Listen for how long the pause is. 5/7118 / 280
  6. The question I now ask everyone: "Tell me about a time you were wrong at work. What did you do next?" The answer tells me more than anything on a resume. 6/7158 / 280
  7. Hiring is slow when you do it well and slower when you do it badly. What is your best hiring lesson? 7/7105 / 280

Why it works. Hiring stories are relatable for any founder or manager. Specific questions and tests give readers something to use this week.

21

Pricing lessons

7 posts

Share what changing your prices taught you.

Outline
1/7 I changed my prices [number] times in [time]. Here is what each change taught me.
2/7 Change 1: [from and to]. What happened: [result].
3/7 Change 2: [from and to]. What happened: [result].
4/7 Change 3: [from and to]. What happened: [result].
5/7 What surprised me: [surprise].
6/7 How I set prices now: [method].
7/7 If you are nervous about raising your price: [advice].
Written example
  1. I changed my prices 4 times in 2 years. Each time I was scared. Each time I learned something. 1/799 / 280
  2. Change 1: $500 to $900 for a brand audit. What happened: I lost 1 lead who was only shopping on price. Everyone else said yes without a word. 2/7146 / 280
  3. Change 2: hourly to a fixed project price. What happened: clients stopped asking how long things took. They cared about the result and the date. 3/7149 / 280
  4. Change 3: $900 to $1,800, with a 30 minute follow up call included. What happened: fewer projects, better clients, more referrals. 4/7135 / 280
  5. What surprised me: the higher price made people take my advice more seriously. At $500 they argued. At $1,800 they took notes. 5/7131 / 280
  6. How I set prices now: I raise them after every 5 new clients until someone says it is too much. Then I hold. 6/7112 / 280
  7. If you are nervous about raising your price: try it on new leads only. Your current clients never have to know until you are ready. 7/7135 / 280

Why it works. Pricing is a topic most experts are nervous about, so real stories get attention. Clear before and after numbers make the lessons stick.

22

Customer interview notes

7 posts

Share patterns from talking to customers.

Outline
1/7 I talked to [number] [customer type] this month. Here is what they told me.
2/7 Pattern 1: [what many said].
3/7 Pattern 2: [what many said].
4/7 Pattern 3: [what many said].
5/7 The quote I cannot stop thinking about: [quote].
6/7 What surprised me: [surprise].
7/7 What I am changing because of it: [change].
Written example
  1. I talked to 15 small gym owners this month. What they told me was not what I expected. 1/791 / 280
  2. Pattern 1: none of them want more software. Most already pay for 4 or 5 tools and use about half of each. 2/7110 / 280
  3. Pattern 2: the real pain is the front desk. New staff get the same questions all day and give different answers. 3/7117 / 280
  4. Pattern 3: they trust other gym owners more than any ad. 12 of the 15 picked their last tool because a friend used it. 4/7123 / 280
  5. The quote I cannot stop thinking about: "I do not need another app. I need my Tuesday night person to know what to say." 5/7125 / 280
  6. What surprised me: price came up only twice. Time to learn a tool came up in almost every call. 6/799 / 280
  7. What I am changing: I am dropping 3 planned features and building one simple front desk guide instead. I will share how it goes. 7/7133 / 280

Why it works. Real customer patterns are rare and useful to anyone in the same market. A strong quote gives the thread a memorable center.

23

The launch recap

8 posts

Share how a launch went, what worked and what did not.

Outline
1/8 I launched [product] [time] ago. Here is the honest recap.
2/8 The plan: [what you planned].
3/8 Launch day: [what happened].
4/8 What worked: [channel or tactic].
5/8 What flopped: [channel or tactic].
6/8 The numbers: [simple fictional numbers].
7/8 What I would do differently: [change].
8/8 What is next: [plan].
Written example
  1. I launched a paid course for new managers 2 weeks ago. Here is the honest recap, including the part I got wrong. 1/8117 / 280
  2. The plan: email my list of 1,800 people, post 3 times, and hope a few friends shared it. 2/892 / 280
  3. Launch day: 14 sales in the first 3 hours, then almost nothing for 2 days. I refreshed the dashboard more than I would like to admit. 3/8138 / 280
  4. What worked: a plain text email telling the story of my worst first year as a manager. It drove more than half of all sales. 4/8129 / 280
  5. What flopped: a short video. I spent 2 days on it. It brought in 1 sale. 5/876 / 280
  6. The numbers: 41 sales at $149. About $6,100 total. Most buyers had been on my list for more than 6 months. 6/8111 / 280
  7. What I would do differently: warm people up for a month before launch with stories, not a countdown. 7/8104 / 280
  8. What is next: a live cohort in March for people who want more help. I am asking buyers what they need first. 8/8112 / 280

Why it works. Honest launch recaps are useful to anyone planning one. Including the flops shows you are sharing to teach, not to brag.

24

Notes on an idea

7 posts

Share notes on one idea or a book you read, and how you applied it.

Outline
1/7 One idea from [a book I read or a talk I heard] changed how I [do something]. My notes:
2/7 The idea in one line: [idea].
3/7 Why it clicked for me: [context].
4/7 Note 1: [point].
5/7 Note 2: [point].
6/7 How I applied it: [example].
7/7 The result so far: [result]. Worth trying if you [situation].
Written example
  1. One idea from a book I read on habits changed how I plan my week. My notes: 1/780 / 280
  2. The idea in one line: make the next step so small you cannot say no to it. 2/778 / 280
  3. Why it clicked: I had a list of big goals and did almost none of them. Every goal looked like a mountain on Monday morning. 3/7127 / 280
  4. Note 1: a goal is a direction. A step is something you can do in 10 minutes. I had been writing goals on my to do list. 4/7124 / 280
  5. Note 2: finishing a small step makes the next one easier. You build proof that you are the kind of person who does this. 5/7124 / 280
  6. How I applied it: "write a blog post" became "write the title." Most days I wrote the whole post anyway. The title just got me started. 6/7140 / 280
  7. The result so far: 8 posts in 8 weeks, after 0 in the 6 months before. Worth trying if your list keeps growing and nothing gets done. 7/7138 / 280

Why it works. One idea explained well beats a long summary. Showing how you applied it turns reading notes into proof.

25

The weekly notes

7 posts

Share a short set of notes from your week of work.

Outline
1/7 Notes from this week of [work]. [Number] things worth sharing.
2/7 1. [Observation].
3/7 2. [Observation].
4/7 3. [Observation].
5/7 4. [Observation].
6/7 One thing I got wrong: [mistake].
7/7 Next week I am [plan]. What was your week like?
Written example
  1. Notes from this week of running a small marketing agency. 4 things worth sharing, plus one I got wrong. 1/7108 / 280
  2. 1. A client asked for "more posts." When I dug in, what they wanted was more calls. We cut posts in half and added one clear offer per week. 2/7144 / 280
  3. 2. The best idea of the week came from Dev, our newest hire, in a meeting he almost skipped. I need to ask the quiet people first. 3/7134 / 280
  4. 3. Short emails get faster replies. I tested it all week. Under 5 lines, most replies came the same day. 4/7108 / 280
  5. 4. I blocked Friday afternoon for no calls. I finished two things that had been sitting for a month. 5/7104 / 280
  6. One thing I got wrong: I promised a report by Wednesday and sent it Friday. I said sorry and explained. The client was fine, but I will pad my dates. 6/7154 / 280
  7. Next week I am testing one new offer with 3 clients. What was your week like? 7/782 / 280

Why it works. Weekly notes are easy to write and build a habit of posting. Small true details make readers feel like they are in the room.

Questions

How long can each post in a thread be?

280 characters on a standard account. X counts some characters as two, such as emoji and Chinese, Japanese and Korean characters, and every link counts as 23. Every example here stays under 280 with its number.

Should I number my thread?

Numbering like 1/7 tells readers how long the thread is and where they are. It costs a few characters per post, which the examples here already allow for.

How many posts should a thread have?

As many as the idea needs and no more. The templates here run 5 to 9 posts. If a post does not add something new, cut it.

Can I turn a LinkedIn post into a thread?

Yes. Paste it into the LinkedIn to X thread tool, or open "See it as an X thread" under any LinkedIn post template on this site.

Are these threads real?

No. They were written for this page with made up details, so you can see each framework filled in.

Sources

  1. X Developer docs: Counting characters · checked 30 Sept 2026

Your next post, in your voice, on both networks.

7 days free. No card. Your drafts are kept.