Ten modules · Two hours each · Free, permanently

The only AI course where the executive builds.

A free, hands-on course for senior executives. You build a working AI document-analysis system — the same architecture behind the products vendors pitch you — then you test it, measure its accuracy, and learn what it costs to run at scale.

Start the course — freeTen modules, self-paced. No card, ever.

Nobody demoted you. The stack did.

You ran engineering organisations. You shipped systems on client-server, on ERP, on warehouses and networks that are still running tonight. That judgment was earned and it has not expired.

But models, embeddings, inference and agents arrived after your hands left the keyboard. So in AI conversations you have been quietly reassigned to nodding — and the worst version of it is the meeting where a board member asks an AI question and you defer to the youngest person in the room.

The gap is vintage, not aptitude. It is also smaller than anyone selling to you would like it to be. This course is not a briefing. It is the restoration of your authority to say no in your own boardroom.

The one system

You build an AI analyst that reads a company's board packet — the deck, the investor memo, the customer contract — and answers questions about it with citations. Then you plant a lie in those documents, watch your own system repeat it back with total confidence, and rebuild your judgment from what you saw.

What you will have built by Week 9. Every box on it is one week of work.

The three phases

PHASE 1 · WEEKS 0–2

Build

Set up a free environment, ingest real documents, and assemble the complete retrieval-and-generation system with cited answers.

The complete system, working, with your own hands on it — and a clear view of exactly how much a working demo does and does not prove.

PHASE 2 · WEEKS 3–5

Test

Verify accuracy. Insert a known-false fact and observe the system cite it. Build a 20-question evaluation set and score against ground truth.

Retrieval misses, confident invention, stale knowledge. You cause each one on purpose, name it, and write down what true looks like.

PHASE 3 · WEEKS 6–9

Operate

Harden and cost it. Catch silent data errors, write a guardrail, and model the cost at production volume.

Guardrails, silent data failure, the real number at ten thousand documents. Then you reread every proposal on your desk with new eyes.

The ten modules

Every week ends with one sentence you can say in a meeting the next morning.

WkWhat happensWhat you can then say
00

You Will Not Spend a Dollar and You Will Not Break Anything

Environment, three free accounts, first query.

“I have run this myself. Show me your version.”
01

Document Ingestion

Documents in, text out. Text extraction and OCR, including scanned pages.

“Where does your pipeline lose the scanned pages?”
02

The Retrieval System

Full retrieval with citations. The demo high.

“That is retrieval, not intelligence. What is it retrieving from?”
03

Accuracy Test One

You insert a false fact. Your system cites it back to you.

“Your demo is only as true as the documents behind it.”
04

Failure Modes

You collect your own system's three best lies.

“What does it do when the answer is not in there?”
05

Evaluation

A twenty-question eval set in a spreadsheet — the artifact nobody in any vendor meeting has.

“Send me your eval set before the next meeting.”
06

Data Quality

Silent data failure, reproduced on your own desk.

“Every check passed. Who noticed the number was wrong?”
07

Agents and Guardrails

Agents, and the guardrail you write yourself to contain one.

“What is this agent permitted to do without a human?”
08

Cost and Model Selection

Open against closed models on a live price meter. Then price it at ten thousand documents.

“That is the pilot price. Show me the number at production volume.”
09

Capstone: The System Card

Capstone: your System Card. And the glossary as field guide — every term mapped to the scar that taught it.

“Here is mine. Walk me through yours.”

What this course will not teach you

Five topics, deliberately closed.

Five topics come up constantly in AI conversations, and this course deliberately leaves each one closed. You do not need what is behind it to evaluate a proposal, and pretending otherwise is how ten-week courses become eighteen-month ones nobody finishes.

We name the door each time we pass it, so you know the shape of what you are not learning. That is a different thing from not knowing it exists.

Behind the door

  • Gradient descent, and local versus global minima
  • Backpropagation
  • Fine-tuning mechanics
  • Transformer internals beyond attention
  • CUDA and GPU programming

The setup

Two browser tabs. Three free accounts. Nothing installed, nothing to break, nothing to expense. If a week ever requires a credit card, that week is wrong and we will rewrite it.

2
browser tabs
3
free accounts
$0
for ten weeks
2 hrs
a week, one sitting

This is for you if

  • You are a CIO, CTO, COO, GM, EVP or board member whose technical career was real.
  • You are currently being pitched copilots, platforms and fine-tuning projects you cannot evaluate.
  • You will actually type, not watch.

This is not for you if

  • You want a strategy overview. There are good ones. This is not one.
  • You want to be shown rather than to build.
  • You are a practising ML engineer. You will be bored by Week 3 — though the glossary may still earn its keep.

Who is teaching this

Boardroom and keyboard, thirty years.

A career run in both rooms at once: boards, budgets and granted patents on one side; code deploying to production on enterprise data platforms this quarter on the other. The instructor is the student, thirty years in.

“I am not teaching this because I studied it. I am teaching it because it bit me, recently, at work.”

The failure in Week 6 — an FX rate that silently defaulted to 1.0 while every check passed — is not a textbook example. It is a Tuesday.

First run

This is the first run. There are no testimonials yet — the first students are the proof. What there is: ten weeks written end to end, Week 0 through Week 9, and an instructor who will be in the thread. If that is not enough, wait for the second run. It will be better, because you will have made it better.

Questions you are already asking

What is the catch?
The course is free, permanently — all ten modules and the endorsement. A paid tier may exist later (capstone review, live groups); the course itself stays free. A room full of executives who cannot evaluate what they are buying is expensive for everyone, including me.
Do I need to code?
You need to type, read an error message without panic, and be willing to be wrong in front of a machine. Copy, run, read, change one thing, run again. No prior Python.
What if I am more technical than you think?
Weeks 0–2 will be fast for you. Weeks 3–9 — evaluation, silent failures, cost modeling — are the part most technical people have also never done. Skim Weeks 0 to 2 and start at Week 3.
Two hours — really?
Two in one sitting. Four under interruption. Miss a week and nothing collapses; the weeks stay where you left them.
What do I have at the end?
A working system, a twenty-question eval set, a guardrail you wrote, a cost model, and a System Card with your name on it.
Is my data going anywhere?
You work on a fictional company's board packet that we supply. Nothing of yours needs to leave your building for any of the ten weeks.

Start the course.

Self-paced · Join any time

Subscribers get it first, plus the Boardroom Field Guide preview: three questions that collapse a fake AI demo.

One email to start, then one per module. Nothing else.