Curriculum
All 28 lessons, published in full.
This is the registry the course is built from, not a summary of it. Every lesson below has its objectives on the page, because a course you can only evaluate after paying is a course asking you to guess.
- lessons
- 28lessons
- days
- 28days
- minutes a day
- 5–15minutes a day
- of the lessons earns the certificate
- 90%of the lessons earns the certificate
The order is yours; the content is everyone's.
Every buyer gets all 28 lessons. The quiz sets the sequence — a builder reads the Claude Code week earlier, someone drowning in email reads week two earlier — and a lesson that needs an earlier one refuses to be placed before it. A course that withheld lessons from the track it assigned you would be three products in a coat.
Week 1
Foundations
Understand what you are actually working with, and get one real thing done with it.
- Day 1
What Claude Actually Is — and What It Isn't
You will be able to
- Describe in one sentence what happens when you send Claude a message
- Name three tasks it is reliably good at and two it is not
- Get set up and send one request that produces something you keep
- Day 2
Asking Better: Context, Task, Format
You will be able to
- Structure any request as context, task, then the shape of the output you want
- Rewrite a vague prompt into one that lands on the first try
- Day 3
Working With Documents Longer Than You Want to Read
You will be able to
- Attach and reference source material so answers stay anchored to it
- Ask questions that keep the document in view instead of drifting into invention
- Day 4
Judging the Answer: A Verification Habit
You will be able to
- Recognise the three failure shapes: confident wrong facts, invented sources, quiet omissions
- Run a two-minute check before you use anything that leaves your desk
- Day 5
Steering: Iterate Instead of Starting Over
You will be able to
- Correct a reply with a targeted follow-up rather than rewriting the prompt
- Use "what would you need from me to do this better?" as a diagnostic
Assumes you have readAsking Better: Context, Task, Format
- Day 6
Your Voice, Not Its Voice
You will be able to
- Use a writing sample to get output that sounds like you wrote it
- Name the specific tells you want removed, and check they stayed removed
- Day 7
Projects: Stop Re-Explaining Yourself
You will be able to
- Set up a Project holding the context you would otherwise retype every day
- Decide what belongs in persistent context and what belongs in one conversation
Week 2
Everyday Productivity
Move the work you already do every week from hours to minutes.
- Day 8
Email and Messages, in Your Own Words
You will be able to
- Draft, reply and decline in your own register without a template library
- Build one reusable instruction that handles most of your inbox
- Day 9
Turning Meetings Into Decisions
You will be able to
- Convert a transcript or rough notes into decisions, owners and dates
- Catch what was agreed but not said, and flag it rather than invent it
- Day 10
Research Without the Rabbit Hole
You will be able to
- Scope a question so the answer is usable rather than exhaustive
- Separate what was found from what was inferred, every time
- Day 11
Spreadsheets and Numbers You Can Check
You will be able to
- Get analysis out of a messy sheet without trusting arithmetic you did not see
- Ask for the working, not just the answer, and verify it in under a minute
- Day 12
Documents and Decks From a Rough Outline
You will be able to
- Go from three bullets to a first draft you are willing to edit
- Keep structure under your control while the prose is drafted for you
- Day 13
Reading Faster: Summaries You Can Trust
You will be able to
- Ask for a summary that names what it left out
- Decide from the summary whether you still need to read the original
- Day 14
Your Week, Planned
You will be able to
- Build a weekly rhythm where Claude has three fixed jobs, not thirty ad-hoc ones
- Measure one hour you actually got back, so week three has a baseline
Week 3
Automation & Agents
Stop doing the task and start describing it once.
- Day 15
What "Agentic" Actually Means
You will be able to
- Tell the difference between a long answer and a model taking steps on your behalf
- Identify one task of yours that is worth handing over, and one that is not
- Day 16
Tools, Files and the Outside World
You will be able to
- Explain what a tool connection lets Claude do that a chat window cannot
- Connect one and watch it read something real
- Day 17
Designing a Workflow You Only Describe Once
You will be able to
- Write a task description precise enough to run twice with the same result
- Find the step that always breaks, and put a check on it
Assumes you have readWhat "Agentic" Actually Means
- Day 18
Connecting Claude to Your Own Data
You will be able to
- Get your documents, notes or sheets into reach without pasting them every time
- Decide what you are willing to connect, and write that decision down
- Day 19
Guardrails: When Not to Automate
You will be able to
- Name the three properties that make a task unsafe to hand over unattended
- Add a human checkpoint that costs seconds rather than re-doing the work
Assumes you have readWhat "Agentic" Actually Means
- Day 20
Work That Starts Without You
You will be able to
- Put one recurring job on a schedule and read its output like a report
- Decide what a failed run should do, before it fails
Assumes you have readDesigning a Workflow You Only Describe Once
- Day 21
Measuring Whether the Automation Helped
You will be able to
- Compare against the week-two baseline instead of against how it feels
- Retire the automation that did not earn its maintenance
Assumes you have readYour Week, Planned, Work That Starts Without You
Week 4
Claude Code & Building
Build a thing that runs whether or not you are watching it.
- Day 22
Installing Claude Code and Asking for a Change
You will be able to
- Install it, point it at a folder, and understand what it is allowed to touch
- Ask for a change in plain language and read what came back
- Day 23
Your First Small Tool
You will be able to
- Build something with one job that you will genuinely use this week
- Keep the scope small enough to finish in one sitting
Assumes you have readInstalling Claude Code and Asking for a Change
- Day 24
Reading a Codebase You Didn't Write
You will be able to
- Get oriented in an unfamiliar project without reading all of it
- Ask for the map before asking for the change
Assumes you have readInstalling Claude Code and Asking for a Change
- Day 25
Debugging as a Conversation
You will be able to
- Give an error the context that makes it solvable in one pass
- Insist on the cause before accepting the fix
Assumes you have readInstalling Claude Code and Asking for a Change
- Day 26
Shipping It: Deploy, Share, Maintain
You will be able to
- Put your tool somewhere other people can use it
- Decide what you will do when it breaks in a month
Assumes you have readYour First Small Tool
- Day 27
Cost, Limits and Choosing a Model
You will be able to
- Understand what you are paying for and what makes a request expensive
- Pick the smallest model that does your job, and know when to stop doing that
- Day 28
Your Next 90 Days
You will be able to
- Turn the twenty-eight days into a practice that survives a busy week
- Pick the one capability you named at the start and plan the route to it
Assumes you have readWhat Claude Actually Is — and What It Isn't, Asking Better: Context, Task, Format, Working With Documents Longer Than You Want to Read, Judging the Answer: A Verification Habit, Steering: Iterate Instead of Starting Over, Your Voice, Not Its Voice, Projects: Stop Re-Explaining Yourself, Email and Messages, in Your Own Words, Turning Meetings Into Decisions, Research Without the Rabbit Hole, Spreadsheets and Numbers You Can Check, Documents and Decks From a Rough Outline, Reading Faster: Summaries You Can Trust, Your Week, Planned, What "Agentic" Actually Means, Tools, Files and the Outside World, Designing a Workflow You Only Describe Once, Connecting Claude to Your Own Data, Guardrails: When Not to Automate, Work That Starts Without You, Measuring Whether the Automation Helped, Installing Claude Code and Asking for a Change, Your First Small Tool, Reading a Codebase You Didn't Write, Debugging as a Conversation, Shipping It: Deploy, Share, Maintain, Cost, Limits and Choosing a Model
The last lesson is the one that closes it
Day 28 assumes every lesson before it and is the only one that does. It is where the tool you built in week four gets a plan attached to it.
Certificate of completion
Finish at least 90% of the lessons and a certificate of completion of this course is issued. It is not an accreditation and we do not describe it as one.
See which order you would get.
The quiz takes a few minutes and shows you the full schedule with real dates before anything is charged.
Build my plan28-day money-back guarantee. See the refund policy for the requirements.