The leverage gap is already here.

The one-sentence version

Claude Code is a way to have a conversation with your computer. You type what you want to happen. It does the thing.

What that actually looks like

You open a window. You type a sentence. Claude reads it, looks at the files on your computer, and gets to work.

You type: "Make a file called plan.md with my Q2 goals in it." Claude makes the file.

You type: "Summarize every board deck in the /decks folder and tell me the three topics that keep coming up." Claude reads every deck. Claude writes you a summary.

You type: "Draft three subject lines for the Thursday launch email in our brand voice." Claude reads the past campaign drafts you keep in a folder, picks up on how you write, and drafts three subject lines.

This is not a chat app. It is not a webpage. It is a tool that lives on your computer, reads your files, and writes new files when you ask it to.

The mental model

Three pieces:

1. Claude. The same model you already know from claude.ai. Reads, thinks, writes.
2. Your files. The documents, spreadsheets, notes, and folders already on your laptop.
3. A place to type. A small window where you give Claude instructions.

Put those three together and the same assistant you have been asking questions in a browser can now do the work on your actual computer. In your actual files. In your actual voice.

What you can do with it

Real examples from real operators:

• A marketing lead drafts a weekly newsletter from a folder of past issues and a topic list. One command.
• An ops manager takes the messy notes from a fifty-person all-hands and produces a clean recap, a decisions list, and three follow-up emails ready to send.
• A founder reads twelve months of board decks and pulls out every time revenue growth came up, with dates.
• A sales lead takes a CRM export and writes personalized follow-ups to thirty leads that sat cold for a quarter.

None of these people write code. They write sentences. Claude handles the rest.

Why the typing window

The typing window is called a terminal. Every computer has one. Most people never open it.

The terminal looks intimidating the first time you see it. Black window, blinking cursor, no buttons. That is fine. You are going to type exactly one thing in it: the word claude. After that you are back to typing sentences, the same way you would type a prompt in your browser.

The reason Foundations uses the terminal path is speed. Claude can read your files, write new files, edit things, and run tools in one flow, all from the same place you typed the instruction. No copying and pasting. No switching tabs. You ask. It happens. Once you are comfortable here, moving to the Desktop app later is trivial.

What is next

In the next nine lessons we are going to:

1. Make sure your computer is ready (lesson 2).
2. Install Claude Code step by step, with screenshots, on Windows or Mac (lesson 3).
3. Open a terminal for the first time and run your first prompt (lesson 4).
4. Turn one-off prompts into reusable commands you can run whenever you want (lessons 5, 6, 7).
5. Build one real thing end to end, the kind of thing you would actually use at work (lesson 8).
6. Cover the handful of things that go wrong and the fix for each (lesson 9).
7. Point you at what to do next (lesson 10).

By the end of this Foundations track you will have Claude Code installed, one real workflow running, and enough of a feel for it that you can start asking "could I have Claude do this?" about the rest of your job.

That is the whole point.