Generic AI training teaches a to-do app. We ask for your repository or your syllabus first, then write the labs against it — so the day ends with something that belongs in your world, not a sandbox.
Every format covers real material with real hands on keyboards. The difference is how much depth and how much of it runs against your own code.
One day · 6 hours live
One track, one day, one working artefact. We spend the morning on the mental model and the afternoon building, and nobody leaves without something running on their own machine.
Two days · 12 hours live
Day one covers the ground the intensive covers. Day two applies it to your codebase, your data and your constraints, with time set aside for the problems that only appear in your environment.
Four weeks · two evenings a week
Spaced practice beats a single long day when you want the material to stick. Two live evenings a week, a project that grows across the four weeks, and a cohort channel that stays active between sessions.
Scoped to your syllabus
Built around what your course actually requires. Send us the module outline, assessment criteria or dissertation brief and we shape the sessions and the final project to match, at student rates.
One to five days · on-site or remote
A curriculum written after we've read your code and talked to your engineers. Your repository, your data, your deployment target — and the awkward internal constraints that generic training always skips.
Pricing depends on format, group size and how much preparation your stack needs — so we quote per engagement rather than publish a number that would be wrong for most people. Students, university groups and non-profits get their own rate; just say so in your enquiry.
Small enough that every participant gets debugged personally. Beyond twelve we split into two sessions rather than let the room go quiet.
Delivered at your office, at a venue, or fully remote. Remote sessions run the same labs with the same hands-on time.
Questions don't stop when the session ends. Every participant keeps a direct line for two weeks afterwards.
We read your repository or your syllabus first. The examples are yours, not a generic to-do app.
Whether you're a CTO with a migration ahead or a student group with an assessment brief, the process is the same — and the first two steps cost nothing.
Who's attending, what they already know, and what you need them to be able to do afterwards. A syllabus, a module outline or a repository link is ideal.
Within two working days: a session-by-session outline, the format we'd recommend, the labs, and a price. Usually one revision round, sometimes none.
The labs get rebuilt on your tools and your data shape before day one, so nobody spends the morning on environment setup.
The session runs, everyone leaves with working code, and we send a written summary with the prioritised next steps for your team.
Pick one, or tell us the outcome you're after and we'll suggest the combination.
Group size, rough dates, and the syllabus or repository we should build it around. You'll have an outline and a price within two working days.