What drives agentic AI workshop cost
Price is set by four things, and none of them is content. Content is nearly free to duplicate. The cost sits in trainer time, ratio, customisation, and follow-up.
- Trainer time. Delivery hours plus preparation. Preparation on a client's own repository is real work, usually a day or more before the session.
- Ratio. One trainer to twenty is a lecture. One to six is training. The second costs more per head and is worth more per head.
- Customisation. Generic slides cost nothing to reuse. Exercises built against your codebase and your test suite do not.
- Follow-up. A session with no return visit is cheaper and fades faster. Two weeks later is when the real questions arrive.
We quote per engagement rather than per seat, because the seat count is the least important variable. Ask any vendor to break the number down along those four lines. A supplier who cannot separate preparation from delivery is selling a fixed product with your logo on the cover.
What belongs in the curriculum
A syllabus worth paying for covers how the tool fails, not just how it works. Ours runs roughly like this on a one day engagement:
- How agents read a repository, and why context selection decides output quality more than prompt wording.
- Writing the repo instruction file. On a real codebase, with the team arguing about their own conventions.
- Task shaping. Turning a vague ticket into something with a stated file boundary and a verification command such as
npm test -- --run. - Reviewing agent output at speed, including the confidently wrong diff that passes CI.
- Where to refuse. Migrations, auth, anything touching money.
Notice what is missing. No history of language models. No slide on the future of work. Nobody has ever shipped better code because of either.
Line items that are usually padding
Certificates. They cost the vendor nothing and mean nothing to a hiring manager. Recorded video libraries bundled at a premium, when the same material exists free from the tool makers. Per-seat licence markup on tools you can buy directly. Multi-day formats where days two and three repeat day one at a slower pace.
One more, less obvious: a large audience presented as value. Training forty people at once is cheaper to deliver and worse to receive. If the price per head drops sharply as the group grows, you are watching the ratio collapse.
Questions to ask before you sign
Four of them, in this order. Will we work in our repository or yours. How many trainers are in the room. What happens two weeks after. And what does the workshop teach people not to do with an agent.
The last question is the one that separates practitioners from resellers. If the answer is enthusiastic and vague, keep looking.
We are two trainers, Rogier in Amsterdam and Vasilis in Athens, both working engineers. We have run this with over a hundred teams. Send us the repo and the constraint you are worried about, and we will tell you whether a workshop is even the right spend.