- Elliot's Key Notes
- Posts
- The Switch
ChatGPT helped me write. Claude helped me build.
For 18 months I told myself I needed more time. Turns out I needed a different tool.
The wild part isn't that Claude is a better writer than ChatGPT. They're both fine. The wild part is what happens when the AI can actually reach your tools.
Testing the Waters
The Creator's Content Cascade had been sitting on my todo list for months.
I'd been building it manually. One Notion page at a time. One workflow at a time. The vision was clear in my head. The execution was glacial. I was writing in ChatGPT, copying into Notion, formatting by hand, second-guessing the structure, going back, redoing it.
Every step was friction.
I'd open the laptop on a Sunday with three hours and walk away with one new piece of the system. Sometimes less.
Then I was watching yet another tutorial on how to build out a Notion workspace, and a related video popped up. How to connect Claude to Notion.
I watched it three times through. If this actually works, maybe I can finally finish what I'd been trying to build for months.
So I did a deep dive on Claude. Read about the connectors. Specifically the Notion one. You could give Claude access to a Notion workspace, and it would actually work in there. Read pages. Write pages. Build databases. Link relations. Not "draft text I'd paste in." Actually do the work.
I didn't believe it.
So I started on the free plan. Just to test. Connected Claude to my Notion. Asked it to help me build out one piece of the Cascade.
What happened next is hard to explain without sounding like I'm overselling it.
It built. Pages with the right properties. Templates. Relations to other databases. Whole workflows materializing in my actual workspace as I described what I wanted.
It became my go-to. When I had a question, it had the answer. When I needed to adjust something, it made the change in the workspace, not in a chat I'd have to translate. When I needed to check whether the databases were linked correctly, it walked the workspace and fixed what was off.
This was different.
If I hadn't made that switch, I don't think the Cascade would exist today. It would still be on the todo list.
So I upgraded. Then I started connecting Claude to everything else I could. Google. Canva. Gamma. beehiiv. Figma when I bother. The mundane backend work that used to eat hours of my Sundays just happens now. While I focus on the parts only I can do.
The whole thing got rebuilt from the inside. I started calling it the AI-Powered Content Cascade because at this point that's literally what it is.
Last week I shipped an ad for an entire imagined luxury brand. None of that happens if I'm still spending Sundays formatting Notion pages by hand.
It's Not About the Writing
Most ChatGPT vs Claude debates are about output quality. Which one writes better. Which one's faster. Which one hallucinates less.
That's the wrong frame.
The writing difference between top models is small enough that it doesn't matter for most of us. What matters is what the AI can actually do once you've talked to it.
Claude can plug into my tools. ChatGPT, when I left it, mostly couldn't. That gap is the entire story.
When the AI lives inside your tools, the friction collapses. You stop being a translator between the model and your workspace. You start being a director. The AI moves from thing I copy from to thing I build with.
Claude is plugged into my Cascade now. It knows my workflow. It knows a single Sunday newsletter becomes a week of content across eight platforms. It knows the templates and the voice rules. I don't have to re-explain the system every time I open a chat. That cuts hours of repetitive work out of every Sunday and frees me up to do the parts only I can do.
This isn't a hit piece on ChatGPT. They built the category. They got me writing in the first place. Credit where it's due.
But the next chapter of the productivity story isn't "AI that drafts for you." It's AI that does work alongside you, in the tools you already use.
That's the switch worth making.
The Bottleneck Wasn't Me
The hardest part of this story to admit: I'd been telling myself I needed more discipline. More focused Sundays. A better routine.
The bottleneck wasn't any of that.
The bottleneck was a tool that could only produce text. The minute I switched to a tool that could move inside my system, the discipline question disappeared. There was nothing left to be disciplined about. The friction was just gone.
If you're stuck on something that should be moving faster than it is, before you blame your discipline, look at your tools. The bottleneck is rarely where you think it is.
Key Takeaways
Tool quality and tool fit aren't the same thing. A model that writes well but can't reach your work isn't going to ship your work.
Connectors are the new bar. AI that operates inside your tools beats AI that drafts in a chat window.
Try the free plan first. I tested everything that mattered before I paid a dollar.
Upgrade after proof. The integration changed my output. That's why I switched. Not because I'd read it would.
When something feels stuck, audit your tools. The bottleneck is rarely where you think it is.
Final Note
The Creator's Content Cascade exists today because I tried a free plan on a Sunday afternoon to see what would happen.
That's the version of the story I want to remember. Not the tool. The willingness to test it and try something new.
What's been on your todo list long enough that maybe the issue isn't you?
Until next time,
Elliot