Development track

Turn AI into how your team builds

Training and adoption for engineering teams. We activate the individual, upskill the team, and equip the champions who carry it across your organisation. Rated 4.9/5.

The introduction is free and there is no pitch. We only recommend a program if it fits your team.

Why activation

The way developers work is changing fast

Claude Code ships new capabilities almost every week. Access is not the problem, your developers already have the tools. The gap is activation: turning scattered, individual use into one engineered way of building.

The craft is changing

Planning, building, reviewing and shipping now run through AI. The developers who adapt fastest set the pace for everyone else.

Activation, not access

Everyone can open Claude Code. Few teams have made it a reliable, shared part of how they build. That is what we activate.

A new way of working together

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

The program

Activation, Transformation, or full Adoption

Training delivers skills. Change management delivers adoption. Start with a one-day Activation. Add Day 2 for a full Transformation. Add Day C to bring the majority along instead of only the early adopters.

Activation
Day 1 · Activation
Module 1

Foundations & Building Blocks

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

  • What an LLM is: tokens, models, prediction
  • Context that persists: the working folder, session and project layers
  • The building blocks: agents, subagents, skills, commands, hooks and MCP
Day 1 · Activation
Module 2

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
Day 1 · Activation
Module 3

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
Transformation
Day 2 · Transformation
Module 4

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
Day 2 · Transformation
Module 5

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
Day 2 · Transformation
Module 6

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
Adoption
Day C · Adoption
Module 7

Champions & Rollout

One representative per team, equipped 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
ROI calculator

What your dev team saves

Conservative estimate: each developer saves at least 8 hours per week on routine work after the program. Adjust to match your team.

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 the engineering team adopts them.
  • Post-workshop support keeps the momentum going.

Not quantified above. Your actual return will be higher.

Book an introduction and we will map these savings to your dev team's actual work.

Book an introduction
Why teams choose us

Why development teams choose us

01

Designed around your codebase, your stack, and your real projects. Not generic AI training.

02

Practitioners, not consultants. Every workflow we run is AI-native. We teach what we use daily.

03

Jasper Staats speaks at official Anthropic Claude Code events. We are on top of every Claude release as soon as it ships.

04

1 senior Claude expert per 10 participants on the floor, so every developer stays supported.

05

Hands-on: developers leave with tangible improvements on their own work.

06

A dedicated workshop playground: your own build environment inside the workshop, prepared on your codebase before day one.

07

2000+ developers and business professionals trained in the Netherlands and Spain, ranging from startups to enterprise clients.

Development track

Ready to make your dev team AI-first?

Join a public Claude Code Masterclass, or book an introduction for an in-company program.