TSS #011: The system behind 9 Twitter threads with 6M+ impressions.

Mar 19, 2022


Hey 👋 - Justin here.

Happy Saturday morning to 13,295 motivated solopreneurs.

Here's one short tip on how to grow your audience and online business.

Today's issue takes about 3 minutes to read.




Today, I'm going to share the process I use for writing my most popular Twitter threads.

I've written 9 Twitter threads that have been seen 6.037M times, and been saved to Readwise over 1,000 times. According to them, that makes me (currently) the 43rd most saved thread writer of all time.

And that's just in 17 weeks of being truly active on Twitter.

Writing high-quality Twitter threads is the fastest and easiest way to pick up new followers who are interested in your expertise. And with interest in your expertise comes email subscribers and customers.

Unfortunately, most people are writing extremely messy, difficult threads.

Writing Twitter threads is about the format as much as the information.

Here are the most common mistakes I see when looking at messy threads.

  • Lacking a good “Hook Tweet”.
  • No "headers" on the "body" Tweets.
  • Way too wordy, and no white space for reading.
  • No clear call-to-action or call-to-conversation at the end.

Much like everything I write about, the key to overcoming these problems is having a clear system for writing threads.

Here's my system, step by step:

Step 1: Start by writing the body of the thread

The body of the thread is the information you're attempting to convey.

If you're not sharing anything of value, even the best "hook" won't get people to engage, comment, and Retweet.

Remember, that scrolling a long thread is tiring, so the format is everything. Because of that, the body should be written in a specific way to make it very easy to read.

Each "body" Tweet should:

  • Have a header
  • Include enough white space to make it easy to read

A header simply tells the reader what to expect in the Tweet they are reading.

White space is the space between lines so that it's easier on the eyes.

Here's an example of both:

Step 2: Write out the CTA (Call-to-action) next

So many people write good threads and then forget to tell the reader what to do at the end. What a waste!

Think about the possible actions you can take at the conclusion of your thread and tell the reader exactly what they should do:

  • Follow you.
  • Join your email list.
  • Sign up for a live event.
  • Read another thread you wrote.
  • Buy a product that is relevant to the thread.

Here's an example of how I end my threads and ask people to follow me, which is the metric I care about most right now.

Note: I also share my email list in case someone wants to take that next step.

Step 3: End your writing process by creating your "Hook Tweet"

We're at the last, but most critically important step of writing Tweet threads.

The "Hook" Tweet.

This is the first Tweet in your thread, and it makes or breaks your entire thread.

Without a good hook, nobody stops to read. And if people don't read it, they don't engage, comment and Retweet it. Ouch.

I've generally found 3 ways to open your thread with a good "hook" that works for me.

They are:

Tell people what they'll get, & address an objection


Use eye-catching numbers


Use juxtaposition (comparison)


And that's it.


Step 1: Write the body using headers and white space

Step 2: Use a specific call to action to tell readers what to do.

Step 3: Write compelling hook lines by using my recommendations.



That's all for this Saturday. 1 simple online business tip.

If you're not getting value out of these tips, please consider unsubscribing.

I won't mind and there are no hard feelings.

Alternatively, if you are enjoying this newsletter, the best compliment you could pay me would be to share it with others on Twitter.

See you again next week.




Join 26k+ subscribers growing their audience and business online.

Every Saturday morning, you'll get 1 actionable tip on audience and revenue growth for your online business.

I will never sell your information, for any reason.