Development track

Turn AI into how your team builds

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.7/5.

There is no pitch. You only get a recommendation if the program fits your team.

Why activation

The way developers work is changing fast

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.

The craft is changing

Planning, building, reviewing and shipping now run through AI. The teams that adapt fastest set the pace.

Activation, not access

Everyone can open Claude Code. Few teams have made it a shared part of how they build.

A new way of working together

Shared standards, agents and workflows in your own environment, so your whole team builds the same way.

The program

Activation, Transformation, or full Adoption

Training delivers skills, change management delivers adoption. Day C brings the majority along, not only your early adopters.

01

Foundations & Building Blocks

The shared base. What Claude Code actually does, and the pieces you build with.

  • Why tokens and models matter: cost, memory, quality
  • Context that persists: the working folder, session and project layers
  • The building blocks: agents, subagents, skills, commands, hooks and MCP
02

Spec-Driven Development

Stop improvising. Write the spec first, then build against it.

  • PRD, epics, features and tickets: working spec-driven
  • Coding standards as context, with CLAUDE.md as a living document
  • AI governance: responsible usage, permission modes, the 4D framework
03

Build, Review & Ship

The full flow on your own stack: plan, build, review, ship.

  • Build feature by feature, with pull requests and real review
  • Run the review and fix what matters, plus a security audit with Claude
  • Structured bug reporting, deploy, and ship a feature after deploy
04

The Harness End to End

From individual skill to one pipeline the whole team runs.

  • Artifacts as history: how work moves and where handoffs break
  • Your system as a graph: reading the map, dependencies across teams
  • Team roles and lanes: everyone owns a lane, and stays in it
05

Lay the Rails

Sprint 1 in breakout teams. Scope it, agree it, ship it.

  • Roles, way of working and tooling, then scope the MVP
  • Write your CLAUDE.md together and set up the repo
  • The gate: no feature code until the rails are up
06

Automate & Govern

Sprint 2. Stop being the trigger, then package what you built.

  • Automate your harness with skills, agents and hooks
  • Publish it as a plugin: your plugin is your governance
  • Team demo: present as a team, on the clock
07

AI Leadership Training

Leaders and one champion per team, ready to carry adoption after we leave.

  • The J-curve, the 10/20/70 rule and the five adopter types
  • Champions, the majority and resistance: the two kinds of "no"
  • A company-wide 30/60/90 plan, built in the room
Custom harness engineering

Trained on your harness, not on ours

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.

Your own repositories, tickets and access

Your current agent next to Claude, on the same feature

A morning on how your setup carries context and where handoffs break

An afternoon building your own features, in your own environment

Your platform

Before, during and after

Your team works in one place, from the intake to the follow-up.

Before
  • Intake Team SurveyResults feed into program design.
  • Program Intake CallWe discuss the survey results with you and present the program, fine-tuned to what they show.
  • Client DashboardInvite your participants by email, follow who has completed the intake survey and export the answers.
During
  • Online AcademyYour dedicated learning playground, with the framework, a cheat sheet, a glossary and downloads.
  • Workshop Learning MaterialsSlides, exercises, modules and more.
  • Curated AI Tool Library48 hand-picked AI tools our team uses every day, with deals on selected tools.
After
  • Personal Certificates of CompletionFor every participant.
  • Impact Measurement SurveyA feedback survey shortly after the program.
  • Client Evaluation CallWithin 14 days after the program. To evaluate the program and agree on next steps.
After the program: Office Hours for three months
ROI calculator

What your dev team saves

Adjust the numbers to match your team. The estimate below is deliberately conservative.

Annual savings
€0
for your dev team
Hours saved / year
0
across the team
Developers
0
activated
Adjust to your team
20
€95,000
Assumes 8 hours saved per person per week, 48 working weeks, 1920 working hours per year. Savings only, before any softer gains.

Beyond the hours saved

  • Faster onboarding and fewer knowledge silos as your developers share the same AI-first workflows.
  • Shared patterns compound: gains stack as more of your engineering team adopts them.

Not quantified above. Your actual return will be higher.

See what these savings look like on the work your dev team does now.

Request a training
After the training

Keep the momentum

The first three months decide whether AI sticks. Office Hours give your team a fixed moment to bring its questions, and leave with them solved.

See Office Hours
Why teams choose us

What you get here and nowhere else

Not another AI course. Not another consulting firm. Here is the difference, line by line.

What AI training usually looks likeWhat 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 academy

Business, 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 professors

Hands-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 people

Only 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

Your own platform, before and after

A Client Dashboard to invite your team and run the intake, and an Online Academy with your playground, framework and downloads. What your team builds 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 curve

Every 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.

Development track

Ready to make your dev team AI-first?

Bring it in-company for your own team, or join a public Claude Code Masterclass.

Stefan Luttik, Founder
For teams

Train your team.

Finish the sentence. Send your request.

We want to train people in , starting .

Add your name.

Check your email address.

Add your company.

Stefan Luttik, Founder