revert: Bye Substack – Welcome to Writer's Fastlane

Ctrl-Z this week, thanks

In today’s issue:

• Why is Akos sending emails from Substack again?

• Thread Fatigue

Before diving into this, I’d like to thank Louie, Greg, Adi, and others I could annoy with my questions about the future of this newsletter. Thank you!

---

Remember when I wrote this last week:

I'm working on a comprehensive post explaining why I moved from Substack to ConvertKit.

The good news is that I have the blog post.

The bad news is that I canceled ConvertKit. So basically, everything stays the same - I’m explaining everything in the post above.

Here’s what you have to do:

Nothing.

I’m grateful you stay subscribed to my newsletter and enjoy the bumpy road filled with partially evaluated decisions, such as the ConvertKit migration.

You’re awesome.

Not subscribed yet? Let’s fix that:

So what happened over ConvertKit?

First, I was afraid of using the name Writer’s Fastlane, but it’s not that. I learned a lesson about brands after A/B testing my bio.link + Substack + Gumroad combination vs. ConvertKit for almost a month. You’ll find the details in the blog post.

If I had to give you a short summary, why not ConvertKit, it would be this:

Every niche got its language. And this doesn’t stop at terminology but applies to platforms as well.

If someone sees Louie’s profile and buys his Gumroad course, the next time they run into my Gumroad, it’s already familiar to them because it looks the same for everyone (very different from ConvertKit).

It’s like entering the same store and seeing a familiar face at the counter.

ConvertKit is a wonderful platform. I annoyed their support a lot, and they always responded in less than an hour. It’s something that Gumroad could improve with their 2 business-day responses.

Anyways, I kept your emails, assuming you are interested in what I say.

Next, my update on my ongoing 35at35 challenge:

Thread Fatigue

35at35 - 15 threads for 15 days

I see some positive effects of nonstop talking about community building and writing for 15 days.

It’s doing OK, but… what if people have Thread Fatigue?

Thread Fatigue is a disorder I just came up with. It affects people who saw too many tweets in their timeline, usually ending with 🧵 or here’s why.

So basically, as you scroll your timeline, you become immune to these tweets and scroll past them. You might not even read the hook. I do this sometimes as well.

Why do I think my readers have Thread Fatigue? The answer is Engagement:

You might have noticed that I share two tweets daily—one at 9 AM and the other at 2 PM.

These are this week's top 6 performing tweets, sorted by Engagement.

These are all the 9 AM tweets.

None of the threads made it to this list – although I like to think I wrote good ones – most followers and engagement came from single tweets.

So here’s what I’ll do the next week:

To fight thread fatigue, I will not publish more threads for the next 15 days.

I can’t post long-form tweets with Typefully, so I’ll do what Ship30for30 calls atomic essays.

Essentially screenshots of long-form text. I’ll create something that looks good, probably in Figma, and add my content there.

I hope you’ll like it!

---

That’s it for this newsletter. I want to thank you for your patience again and for your time.

See you soon,

Akos