Training and adoption for engineering teams. Your developers get going first, your team builds one shared way of working, and your champions carry it across the organisation. Rated 4.9/5.
There is no pitch. You only get a recommendation if the program fits your team.
Claude Code ships new capabilities almost every week, and your developers already have access. The gap is activation: turning scattered, individual use into one way of building that your whole team runs.
Planning, building, reviewing and shipping now run through AI. The teams that adapt fastest set the pace.
Everyone can open Claude Code. Few teams have made it a shared part of how they build.
Shared standards, agents and workflows in your own environment, so your whole team builds the same way.
Training delivers skills, change management delivers adoption. Day C brings the majority along, not only your early adopters.
The shared base. What Claude Code actually does, and the pieces you build with.
Stop improvising. Write the spec first, then build against it.
The full flow on your own stack: plan, build, review, ship.
From individual skill to one pipeline the whole team runs.
Sprint 1 in breakout teams. Scope it, agree it, ship it.
Sprint 2. Stop being the trigger, then package what you built.
Leaders and one champion per team, ready to carry adoption after we leave.
You work on a snapshot of your own harness, so nothing here runs on a demo project. This module is booked separately, next to the Development track.
Adjust the numbers to match your team. The estimate below is deliberately conservative.
Not quantified above. Your actual return will be higher.
See what these savings look like on the work your dev team does now.
Book an introductionApply for one of ten hosted seats. The ticket, coffee and lunch are on us.
Apply for a hosted seatNot another AI course. Not another consulting firm. Here is the difference, line by line.
| What AI training usually looks like | What you get |
|---|---|
| Almost nobody covers all three. Development teams get a coding assistant, and that is where it stops.One discipline only, usually a coding assistant | All three disciplines, one academyBusiness, creative and development under one roof. Your engineers, your marketing team and your creative team learn on the same method, shaped around your own processes, tools and real workflows. |
| A slide deck about what AI can do, with very few hours inside the tools.A slide deck, with very few hours inside the tools | Practitioners, not professorsHands-on from the first hour, in your own tools and your own codebase. Every workflow we teach is one we run ourselves, daily. |
| Groups of thirty or more, so attention thins out and people leave with less than they came for.Groups of thirty or more, so attention thins out | One senior instructor per 10 to 15 peopleOnly senior instructors, each with hands-on experience at leading brands. No junior trainers, no filler, and enough room to look at everyone’s screen. |
| A sandbox login and a demo repository, so nothing anyone builds during the day survives the day.A sandbox login and a demo repository | A dedicated workshop playgroundYour own build environment inside the workshop, prepared on your codebase before day one. What your team ships on the day stays with your team. |
| A curriculum written once and taught for a year, while the models move every month.A curriculum written once, while the models move monthly | AI-native, always ahead of the curveEvery Anthropic release applied in your team the same week it ships, not next quarter. Jasper Staats speaks at official Anthropic Claude Code events, so we know what is coming before it lands. |
Bring it in-company for your own team, or join a public Claude Code Masterclass.
We use cookies or similar technologies for technical purposes and, with your consent, for other purposes as specified in the cookie policy. Use the "Accept" button to consent.
Cookies are small files a website stores on your device. Similar technologies, such as local storage and pixels, do the same job. We use them for three purposes. Two of them are your choice.
These keep the site working. We store your cookie choice in your browser, so we do not ask again on every page. The ticket button and the ticket checkout come from Luma, our ticketing platform. Luma and its security provider Cloudflare set cookies that protect the checkout against bots. These need no consent and are always on.
Umami counts visits and clicks without cookies and without identifying you, so it always runs. Google Analytics and Google Tag Manager show us in more detail how people use the site, and Microsoft Clarity shows where people click and scroll, with heatmaps and recordings of visits in which what you type is masked. Google Analytics sets cookies such as _ga, kept for up to 2 years, and shares data with Google Ireland Limited; Clarity sets _clck and _clsk and shares data with Microsoft. They run only if you allow them.
On our event pages the Meta pixel tells Meta which pages you saw and when you start a checkout, so we can see which ads work. It sets the _fbp cookie, kept for 90 days, and _fbc when you arrive from a Meta ad. The data goes to Meta Platforms Ireland Limited. It runs from the moment you open an event page. Switch off Marketing below to stop it.
Separately from these switches, when you buy a ticket our server reports that purchase to Meta, with your email, name and location in hashed form. Our privacy policy explains this.
Switch off what you do not want and press Save choices. You can change or withdraw your choice at any time through Cookie settings at the bottom of every page. The cookie policy lists every tracker, who provides it and how long it is kept.
