§ 07.A // MODULES 4 COURSES
§ 07.B // OUTCOMES
// EFFICIENCY

Hours back, weekly.

Teams leave with a written audit of automatable work and the tooling choices to attack it. Most cohorts identify 12–30 hours of weekly toil in the first workshop alone.

// JUDGEMENT

Ship and don't ship.

The most valuable skill we teach is when not to deploy a model. Trainees leave with the discipline to push back on bad scope and the language to defend the call.

// SELF-SUFFICIENCY

Less reliance on us.

The point of training is that you stop needing consultants for the easy half of the work. We tell you what to read next and we mean it.

§ 07.C // HOW TRAINING WORKS
01
SCOPING

One call. Pick the module.

We talk to a sponsor and one or two attendees. We pick the right module, agree on a cohort size, and decide whether the capstone uses your data or ours. Free.

02
PRE-WORK

A reading list and an environment.

Two weeks before the cohort, attendees receive a short reading pack and a working code environment. About four hours of pre-work per person. Skipping it is allowed but discouraged.

03
DELIVERY

Onsite or remote, live.

The course runs over consecutive days, taught by a practitioner who has shipped what they're teaching. Mornings are concept; afternoons are hands-on. The final session is a written debrief.

04
FOLLOW-THROUGH

Sixty days of office hours.

For two months after the cohort, attendees can write to us with stuck-points from the work they're applying. We answer within two business days. No additional fee.

§ 07.D // BOOK