Anthropic courses worth doing. And when.

I’ve completed six Anthropic courses since the start of the year. I went through them in the order they were listed on the website, which was the wrong order. So I’m going to tell you the right one.

This guide is for small business owners and busy professionals. Not for developers building agents, not for ML engineers, not for people who want to be impressive at dinner parties. If you run a small team or a one-person practice and you want to use Claude well, here’s what to do, and what to skip.

Start with AI Fluency: Foundations

This is the one course I’d recommend to everyone, full stop. It’s about four to six hours, depending on how thorough you are with the exercises. It’s free.

What it covers is the four-step framework Anthropic teaches for thinking with AI: Delegation, Description, Discernment, Diligence. The names are clunky but the framework lands. By the end of the course you’ll have a vocabulary for what you’re doing every time you open Claude, and you’ll catch yourself doing it wrong less often.

The other reason to start here is that it sets the tone. The course is calm and grown-up. It doesn’t sell you on AI, and it doesn’t tell you the robots are coming. It just teaches you how to use a tool. That tone is rare in AI education in 2026, and it’s the reason I trust Anthropic’s curriculum more than most of the YouTube content out there.

I scored well on the assessment, but the question I missed taught me more than the ones I aced. It was about discernment. I’ve thought about that one question more than most things I got right since. Take the assessment seriously.

Then do AI Fluency: Framework

If Foundations is the vocabulary, Framework is the grammar. It takes the same four steps and shows you what they look like applied to actual work. There are case studies, a couple of which felt thin to me, but the structure is solid.

Three to five hours. Free. Take it within two weeks of finishing Foundations, while the framework is still fresh.

After Framework, stop and use Claude for thirty days. This is the most important sentence in this post.

The courses are good. They’re not a substitute for doing the work. Most of what you’ll learn about Claude comes from making mistakes inside your own actual workflows, not from watching another video. Thirty days of real use, with a CLAUDE.md you keep editing, will teach you more than a hundred hours of courses.

Optionally, after a month: prompting at depth

There’s a course on prompt engineering. The name varies depending on when you look. It’s worth doing if, after a month of real use, you find yourself frustrated that Claude isn’t giving you the format or specificity you want.

It’s not worth doing first. You won’t have enough texture in your own workflows to know which techniques matter for you. Doing it cold, before you’ve used Claude in earnest, is like reading a book on how to fold dough before you’ve baked anything.

Skip, for now: anything with “API”, “tools”, “agents” or “SDK” in the title

These courses are well made. They’re not for you, if you’re a small business owner who isn’t building software. They teach you how to construct multi-step agentic systems, or call Claude from Python, or wire up tool definitions in code. That’s a craft, and it’s a serious one, and Claude’s documentation around it is some of the best in the industry. But if your job is to ship invoices, draft memos, reconcile statements or write to clients, none of it is your fight.

If you’re curious, do them later. They’ll make sense after the third or fourth time you find yourself thinking “I wish Claude could just do this in the background”, and that thinking will come naturally only after you’ve operated the basics for a few months.

The shape, in one paragraph

Start with AI Fluency: Foundations. Move into AI Fluency: Framework within two weeks. Then close the laptop and use Claude for thirty days, with CLAUDE.md files you edit as you learn. After that, do the prompting course if you’re frustrated, and the agentic ones only if you’re curious. Total time investment: around ten to twelve hours of courses, spread across a month and a half, with thirty days of actual work in the middle.

That’s the right order. I did it the wrong way around, and it cost me a couple of months. I’d rather you didn’t.

If you’d rather skip the curriculum entirely and have someone walk you through the install at the end of it, that’s what the Work OS install is for. Two hours, AUD $499, working at the end of your install or your money back. But if you’d rather learn it yourself first, the path above is the one I’d take if I were starting again.