What you'll walk out with

In short: This course is about four hours of reading. The biggest piece of doing is a six-hour Business Brain capture across Lessons 3 and 4, and then one workflow runs for a week in Lesson 5. At the end you will have a Business Brain document, a scored list of the workflows in your business worth automating, an honest readiness score with named gaps, one workflow running as draft-and-approve, and a 30-day plan you could hand to someone on your team Monday morning. Setup takes five minutes and costs nothing.

Who this is for

You run things. A business, a team, or a department. You have customers or internal stakeholders, people who report to you or contractors you lean on, an inbox that never empties, and no interest in becoming an AI person. You're not building an app. You're trying to get four hours back a week and stop dropping follow-ups.

I've spent my career building software and shipping products, and years before that working in a snowboard shop. Retail is where I learned most of what I know about operations, because retail punishes bad systems immediately. Today I run two businesses on the exact pattern in this course. I'm not reporting on it from a distance. It's how my Tuesday works.

The one sentence everything rests on

Here's the whole thesis, and it fits on a sticky note.

Claude drafts. A named human approves. Nothing reaches a customer without a yes.

That's the operating system. Everything else in this course is detail hanging off that sentence. I know it's underwhelming. You were promised an autonomous workforce and I'm handing you a permission slip. But the businesses getting real, boring, repeatable value out of AI in 2026 are all running some version of draft-and-approve, and the ones that blew up were all running some version of "we wired it up and let it go." The gap between those two outcomes is one review step that takes seconds.

It also means the risk of what we're building is close to zero. Claude writes, you read it, you send it. That's why it's the right first thing.

What you'll have when you're done

• A Business Brain. One document that holds your voice, what you sell or deliver, who it's for, and how work arrives. Every draft reads it first. This is the reason output sounds like you instead of like a polite stranger.
• A scored shortlist. Every recurring chore in your business, or the department you run, rated on three scales and multiplied, so the first workflow is chosen by a number instead of by irritation.
• A readiness score with named gaps. Thirty yes/no questions. The number matters less than the list of no's, which becomes your to-do list.
• One workflow running. Built as draft-and-approve, wired into the place your team already looks, with a flag rule so the model tells you what it doesn't know instead of guessing.
• A 30-day plan and a real decision at the end. Ship it, fix it, or kill it. All three beat a pilot that limps for eight months.

What it feels like when it's working

Not futuristic. That's the part people aren't ready for.

It feels like opening a queue in the morning where eleven things are already written. The follow-ups, the categorizations, the three replies you were dreading. You read them, change a line in two of them, delete one, and approve the rest. Fifteen minutes. Then you go do the work you're actually good at.

That's the whole experience. It's not impressive. It just gives you back your Tuesday morning, every week, forever.

The five-minute setup

This is the least interesting part of the course, so let's get through it fast.

Go to claude.ai and sign up. Free plan. Don't pay for anything yet. I'll tell you exactly when money should enter the picture, and it's not today.

What you get is a chat box. That's the whole thing, and that's also the trap. Use it as a chat box and you'll get chat box results: generic, vaguely useful, the kind of output that makes people say "I tried AI, it wasn't that impressive."

The difference between that and something that runs part of your business is one concept. Projects. Left sidebar. Create one and name it after your business or your department.

A Project is a container that remembers. Anything you put in its instructions or files gets attached to every conversation you have inside it. You don't re-explain your business every time. You explain it once. That's the entire architectural insight, and most people never find it because they live in the default chat window forever.

The project instructions box is going to stay empty until Lesson 3, because filling it in correctly is the part that actually matters.

On money, said up front

The free plan is enough to do everything through Lesson 5. You'll hit usage limits if you push hard, you'll wait a few hours, you'll be fine.

Where it changes: when you want Claude connected to the tools your business already runs on, your email, calendar, files, and CRM, and when you want your team in there with you instead of it being just your account. That's a Claude Team plan: $25 per seat per month billed monthly, or $20 billed annually, for teams of 2 to 150. Two people is $50 a month.

I'm telling you the real number before you invest an afternoon. For most owner-led businesses it's less than the software you're already paying for and not using. But don't buy it today. Build your first workflow free. If it's worth $50 a month to have running against your real inbox, you'll know, and it'll be your own evidence instead of my pitch.

Do this now

1. Create a free account at claude.ai. Do not upgrade.
2. Create a Project and name it after your business or your department.
3. Find the project instructions field and leave it empty. That's Lesson 3's job.