Start here
Some of you are further along with AI than others, and that's fine. The purpose of this course is simple: once you strip away the acronyms and the buzzwords, AI is a pretty logical idea.
There are a lot of big claims about how amazing AI is. My view is more grounded: it's a tool. And like any tool, it's only as good as how well you understand how to use it.
A year of using it seriously taught me something honest. It changed the shape of my work rather than shrinking it. The things I already knew, the frameworks I'd learned, the processes I'd been part of: all of it became more valuable, not less. AI didn't replace it. It sharpened it.
Here's the part nobody tells you: the speed comes with more work, not less. Which is exactly why the system this course builds matters.
The businesses that work this out first will be the ones it helps most. This is the first step for you and your business.
If any of this lands, you know where to find me. I'm genuinely happy to answer questions about putting AI to work in your business.
J
What you are about to build
By the end of part one, about twenty minutes from now, you will have a working AI Operating System: a permanent place your AI reads before it answers anything, so you stop explaining your job from scratch every time.
That sentence is the whole course. The next two lessons explain it. The one after that builds it. Everything past part one makes it sturdier: context it can stand on, rules it follows, tools it can reach, and one piece of your real work mapped so it runs the same way twice.
Two things worth knowing before you start.
Nothing to install for the system itself. You build this by asking the AI you already pay for to build it with you. That is also the first demonstration of the point: you do not have to write any of it, you have to ask for it.
Every lesson ends with something that exists. A file, a decision written down, a rule your AI now follows. This is not a video course you watch. If you finish a lesson with nothing but notes, the lesson failed.
Which app you are in changes what happens next
Same course, two paths through it, and this is the part people are not told.
"ChatGPT" and "Claude" are not one thing each. Both have a browser version and a desktop app, and the desktop apps can do something the browser cannot: work directly in a folder on your own computer. For an AI Operating System that difference is the whole game, because a folder you own is a thing you can edit, back up, and point a different AI at next year.
Where you are | What it does with files | What it costs |
|---|---|---|
ChatGPT in a browser | Projects. You upload copies and add project instructions | Free plan included |
ChatGPT desktop app | Work opens a folder on your computer and reads and changes the files in it | Free plan included |
Claude in a browser | Projects. Project knowledge plus project instructions | Free plan limited use |
Claude desktop app | Cowork reads and writes your local files directly, macOS and Windows | Paid plans only |
Two names worth decoding, because both are new and neither explains itself:
The one surprise in that table is that the free route to a real folder runs through ChatGPT rather than Claude. Work is free to start on any ChatGPT plan, as long as you are in the desktop app. Cowork needs a paid Claude plan. If you are not paying for either yet and you want files on your own machine, download the ChatGPT desktop app.
If you only have the browser, carry on. You will end up with a Project rather than a folder, which is a real AI OS and slightly more work to maintain. One thing the browser path does need: an account, signed in. The free plan is enough, but signed out there are no Projects and the chat is not saved, so the system you build would die with the tab. The course tells you both ways at every step.
If you have a desktop app, use it (Preferred). Install it before you start, sign in, and you will finish part one with files on your own machine.
Pick a path now. You can switch later; lesson 4 walks through both.
Stuck anywhere in this lesson? Reply to any Build Notes email and tell me where. I would rather fix the lesson than have you quietly give up.