Skip to content

Trainings

Your leaders know how AI agents change their teams' roles and rituals, and lead that change.

An AI leadership program for CTOs, VPs and engineering managers whose teams build with agents: typically two days, for your leadership group.

  • Benedikt Stemmildt
  • Stefan Munz
  • Björn Rochel
  • Alexander Greim
Get an offer

EUR 1,500 per participant

  • Typically two days
  • remote or on site
We went from 2 engineers playing with agentic coding to 20 using it daily. We created 17 skills and 9 agents available to every engineer. Skeptics now embrace it, with a Slack channel dedicated to sharing learnings and complaints when Claude goes down.
Tom Hibbert (opens in a new tab)
Chief Technology Officer Moonfare

What you get from the program

Your leaders lead the change themselves, and the speed your teams gain reaches your customers.

A program for the people who decide. What changes when agents write most of the code, what stays a human decision, and how to read what your teams report back. You come away with the mental models your engineers learn in Agentic Engineering for Developers and QA.

Who it's for

One company's leadership group: CTOs, VPs, heads of engineering and product, and engineering managers. Benedikt Stemmildt or Stefan Munz leads it, or one of our leadership trainers, Björn Rochel or Alexander Greim.

What you take away

  • A common language with your engineering and product teams
  • A view of what to measure and what to leave alone
  • Concrete leadership actions for the next weeks, and a roadmap for running the change in-house
  • A certificate of attendance for each participant, confirming the training

What the program covers

Day 1: Where you stand, what AI agents change
  • What changes: what changes when agents write most of the code, what humans still decide, and how to read what your teams report.
  • Leadership maturity: where your leadership group stands, between tolerating AI and shaping the strategy.
  • An honest look at your teams: how agentically each team works today, and where adoption gets stuck.
  • Ceremonies and cadence: which Scrum ceremonies you keep, which you drop, what replaces them.
  • Roles and team dynamics: product owners grow more technical, developers do discovery, agents handle routine work.
Day 2: Leading the change
  • Unblock usage: approve tools within weeks.
  • Make adoption visible: share productivity openly, and decide what to measure and what not to.
  • Take the fear out: agents strengthen your developers' skills.
  • After Scrum: what comes next when teams say the ceremonies slow them down.
  • Try it yourself (optional): the leaders build one feature with agents themselves.
  • Your coming weeks: concrete leadership actions and a roadmap for running the change in-house.

How it runs

  • Change that needs leadership

    Adopting agents is a cultural shift, much like the move to agile 20 years ago. Serious companies set up a program rather than running it on the side. For larger organizations, we work across several rounds as the rollout matures.

  • Preparation call

    Before the program, we agree on the agenda, the maturity level and your teams' actual stack. That way it addresses exactly the questions your leaders really face.

  • 1:1 coaching for leaders

    We also offer ongoing coaching for individual leaders. Ask us.

  • Lifetime access to our community

    Free for every participant: people from other teams share what works in the hackers&wizards community.

Runs in Claude Code, Codex, GitHub Copilot, Gemini CLI or Cursor.

Trainings by tool

Who delivers it

Benedikt Stemmildt or Stefan Munz lead it themselves, or one of our leadership trainers like Björn Rochel or Alexander Greim. For each group, we propose a trainer based on technical fit, language and seniority, and on whether they will get on with that group. In our experience, the personal fit matters most. You accept or decline, then you get to know them and we prepare the training together.

  • Benedikt Stemmildt

    Founder & Co-CEO

  • Stefan Munz

    Founder & Co-CEO

  • Björn Rochel

    Agentic engineering coach

  • Alexander Greim

    Engineering leadership

AboutAll trainers

What it goes with

The program works best alongside the team trainings and the mentoring. Leadership sets the frame, the teams apply it every day, and the knowledge stays in-house.

What clients say

What clients say about our trainings

We've streamlined our processes across the entire Scrum cycle, from cutting epics through sprint planning to deployment. What used to be manual and inconsistent now runs in a far more structured way. The team spends less time on alignment loops and more on creating real value. My advice to peers: just do it. You'll see the value quickly, and the earlier you start, the sooner you benefit.
Chris Dornhoff (opens in a new tab)
CTO Krombacher
From my point of view, day 2 was a success. I think it was very inspiring for all participants. The spark definitely caught, and that was the goal.
Florian Sauter (opens in a new tab)
CTO EGYM

Questions before booking

Who is Agentic Engineering for Engineering and Product Leaders for?

One company's leadership group: CTOs, VPs, heads of engineering and product, and engineering managers.

How long does it take, and where?

Typically two days, remote or on site

What does it cost?

EUR 1,500 per participant. Team training, EUR 15,000 at most for the two days: up to 12 people attend, and you pay for 10 at most. Net, plus VAT. On site, plus travel at cost.

A team of fewer than eight pays the same EUR 750 per participant and day, or brings a neighbouring team along.

Is this tied to one vendor's tool?

No. Each training runs in the tools your company already uses. Your leaders learn what differs between agents and what does not.

How quickly can we start?

Plan on about four weeks from the order to the first training day. We agree the date with you, and your team's calendar usually decides it. It can go faster: in 2026, our quickest start came 11 days after the order.

Not sure where to start? Take the self-check