Since Miami, one question has come back on repeat. In different words, from different people, but always the same shape.
Should I move from ChatGPT to Claude? Is Pro worth it? Where do I actually start?
The honest answer first: everything you'll learn through this newsletter is platform-agnostic. Claude, ChatGPT, Gemini, they all work. The thinking is what matters. The harness, meaning the AI platform you build on, is your choice.
But I was asked which one I use, so here's the honest answer to that, and the migration kit if you decide to come across.
I run on Claude. Have done for a couple of years. I have accounts on all of them. Claude is the one I actually work in.
Quick frame, since I'll use the term throughout: when I say specialist, I mean an AI assistant trained on your practice's data, voice, and workflows to do one specific job reliably. Not a chatbot. Not an automation. An assistant with a defined role.
Why Claude, for what I do
Three reasons.
Writing style. Claude's prose comes out more human, less template-shaped. When I draft anything that needs to sound like me, memos, posts, patient-facing copy, Claude needs less editing. ChatGPT writes well. Claude writes closer to my voice on the first pass.
Coding. Claude Code is the part most people don't see, but it's where the higher levels of AI-Powered Thinking become reachable. When I'm building specialists, automating workflows, or stitching tools together, the coding capability matters. Claude leads on coding benchmarks and around 70% of developers prefer it for that work. For the creation side of the ten levels, this is the difference between Level 5 and Level 8.
The harness. Claude Projects hold persistent knowledge and context. They're the foundation. Skills sit on top. Small reusable instruction sets Claude reads and applies automatically when the moment calls for them. Build a Skill once. From then on, Claude knows how to do that specific job your way, without being asked. That's the layer that turns a Project into a real specialist.
ChatGPT has equivalents to Projects (Custom GPTs), and they work. But nothing in their harness matches the way Skills compound quietly in the background. The Claude harness facilitates AI systems and agent work better, in my honest opinion.
Don't worry if those terms feel abstract right now. They become concrete as we go.
ChatGPT is ahead on image generation, voice, and ecosystem breadth. If those matter to your work, run both. Most people I respect do.
So this isn't "switch or you're behind." It's: I was asked which I use. This is the answer. If you want to come across, the kit below is the way I'd do it.
Block a half-day. Do it once. Move on.
Step 1: Get a Claude account [15 min]
Start at claude.com. Get Pro. The free tier is fine for trying it. It is not enough to take the work seriously. $20/month.
Step 2: Bring your memory across [30 min]
The killer step. Most people don't know it exists.
Go to claude.com/import-memory and Claude will read your ChatGPT history and bring across what it needs to know about you and your practice. Years of context, half an hour.
If you want a visual walkthrough showing exactly where to click on the ChatGPT side as well as the Claude side, this five-minute video covers it cleanly.
Step 3: Build your first Project, not your first chat [45 min]
The mindset shift sits here.
A chat is a one-off conversation. A Project is a workspace where you load instructions, knowledge, and context once, and Claude keeps them every time you return. That's the foundation of every specialist you'll ever build.
Anthropic's seven-minute walkthrough covers the mechanics cleanly. Watch it once, then build alongside.
For your first Project, pick something low-stakes. A draft of your practice voice. A patient FAQ. Anything you'd otherwise re-explain every time.
Step 4: Choose your path from here
Free path: this newsletter. Issue 1 in two weeks.
Paid path: Your AI Think Team, the ten-module course that takes you from "I've got Claude Pro" to "I've got ten specialists running my practice." $495 one-time.
Block the day. Once it's done, it's done.
The migration is the boring part. Foundations always are. Once they're set, everything you build on top compounds.
— Brendon
P.S. If you know someone still stuck deciding, forward this on. The easiest favour you can do them this month.
Got this from someone else? Subscribe at guideable.me/newsletter. One use case, one prompt, one short read. Every two weeks.
