Skip to content

Blog

When the CEO sits in the developer training

AI stopped being a tooling purchase and became an investment in the environment: the harness, the context layer, the trained team, the hiring filter. A CEO doing the exercises next to their staff engineers shows the shift.

Written by

Adoption

Published: 30 July 2026 Updated: 1 min read

Last month a CEO spent a full day in our agentic engineering workshop. They did the advanced exercises, skills architecture and MCP servers, right next to their own staff engineers.

That is the moment I started reading new clients differently.

Who used to be in the room

For most of the last two years the staffing looked the same at midsize companies. The VP of Engineering books the workshop. A director organizes it. Senior engineers attend. The CEO gets a one-page summary on Friday.

This time the CEO was in the room, notebook out, asking questions, working through the exercises with the team. That changes what the day is about. AI stops being a developer-tooling decision. It becomes a decision about the environment the whole team works in, and the person who funds that environment is sitting in the seat.

The tool is a line item, the environment is P&L

The tool itself is a line item. The harness around it, the context layer, the trained team, the hiring filter: those are P&L. And P&L belongs to the CEO.

The company was already paying for Claude Code before the day started. That alone tells you the tool side is solved. The CEO showing up is the signal that they are now investing in the part that matters more.

Where the constraint sits now

The companies I see pulling ahead are the ones where the most senior person has personally sat through a developer training day. Once, maybe twice. Enough to know what the real constraint is.

The tool budget is close to settled everywhere. The environment around it, the harness, the context layer, the people trained to run both, is where the money and the constraint now sit. Most companies have never put a line in the books for it.

Go look at where your AI spend sits today. If all of it is a subscription, you have bought the cheap half.

Further reading

  1. Run the migration you keep postponing as the training Train agentic engineering on the legacy migration the team has postponed for years, not on a sandbox. The team learns on its real codebase while the debt shrinks. 2 min readShort post
  2. Agentic coaching is the new agile coaching Adopting agentic engineering has the same shape as adopting agile twenty years ago: an organizational change, resistance among senior people, and the same three levers that worked the first time. 2 min readShort post
  3. Agentic adoption is harder than agile, because you can't fake it Agile rollouts could rename roles and keep the waterfall. Agentic engineering returns nothing on half-measures, because every gate sits upstream in architecture, context and the team. 2 min readShort post

All 13 posts on Adoption

ClientsCase study: Tegtmeier Internet Solutions

Test the constraint in your system

The Factory Readiness Assessment connects this research to your value stream, your data, and the next decision.

Training on this topic: Agentic Engineering for Engineering and Product Leaders
See the assessment

Want to check one team first? The self-check: twelve yes or no questions, three minutes, instant result, no account. Take the self-check