// Teaching people & organizations how to use Claude
We teach your people
to use Claude.
A small, elite unit deployed into your organization — training your team on Claude inside the work you actually do, so the capability stays in-house. Bounded cohorts: a start, an end, a definition of done.
AVAILABLE FOR DEPLOYMENT — ONE ENGINEER, FLEET VELOCITY
Most AI training ships a certificate.
We ship capability — your team working with Claude on your own operation, in production, before we leave. Training that never touches the real work is theater. Section 9 deploys.
The cohort builds the capability; the handoff makes it yours.
Claude Code for your engineers. Cowork for everyone whose work lives in documents, inboxes, and spreadsheets. Taught live, on your actual workflows — not toy exercises — so the first thing your people automate is their own job's worst hour.
The capability stays when we leave — people who reach for Claude without asking permission, the playbooks they learned on, and an honest read of who's ready for more. When you want to go deeper, that's the next cohort, not a retainer.
The person teaching your team runs an entire company with Claude.
One human, a fleet of agents, a whole company running on Claude — every day, in production. That operation is the curriculum. What your team learns on Tuesday was used for real on Monday, not written into a course two years ago.
No certified-trainer bench reading someone else's slides. No curriculum frozen the day it was printed. One practitioner, teaching the exact patterns he runs his own business on, current to this week's frontier.
A training company sells you a syllabus and a rotating trainer who has never shipped with the tools they teach. Section 9 sends the practitioner. A small unit, deployed into the hard situation, operating semi-autonomously. That is the entire meaning of the name — and it is exactly why it works.
Assess. Train. Hand off.
We baseline your team — who's ready for what, honestly measured — and pick the real workflows the cohort will learn on. The brief comes from the floor, not a syllabus.
A live, bounded cohort inside your operation — Claude Code for the engineers, Cowork for the domain teams — working on your actual work. It sticks because it happens where the work happens, not in a sandbox.
When we leave, the capability is yours: people who use Claude daily, the playbooks they learned on, an honest assessment of where each person landed. No dependency, no retainer trap.
Have a team that should be running on Claude?
Start a cohortWorking capability, not certificates.
Agentic engineering as a discipline: skills, agents, worktrees, the loops that turn one engineer into a fleet.
Claude for the people whose work never touches a code editor — taught on that work, not on demos.
Honest measurement of who can do what with Claude — before the cohort, and when it ends.
The workflows a one-human company actually runs on — automation loops, agent fleets, taught from production.
Provenance, not invented proof.
Section 9 runs on a private operational system — Ghost — an entire company operated by one human and a fleet of Claude agents. It is the proof that what we teach works, because it is what we run. The public evidence is the open source forged inside it. We don't borrow other people's logos to look bigger.
No dodge, no deck-speak.
Deployed where it matters.
If your people should be working with Claude and aren't yet, open a line. You'll talk to the person who teaches it — not a pipeline that routes you to one.