Claude Code Workshop for Your Engineering Team

The person in the room

Nicu Constantin, our CTO, builds the agent systems we put in front of clients and breaks them on purpose before anyone else can. He has also taught 38 people to build this, across two structured programmes with six live sessions each, individual project work and a final assessment. You are getting the engineer, and he happens to be good at teaching.

Most training is a trainer reading someone else's deck. Nicu has written over 90 technical articles on agent architecture, prompt injection defense and AI red teaming, and he will spend the day arguing with your engineers about how a hook should fail. That argument is the product.

38

engineers trained

90+

technical articles written

200+

components in the stack he runs

2024

building agents since

His specialty is the part most training skips: what happens when the agent is wrong. Prompt injection, credential handling, access scope. He asks those first, and by the end of the day your team asks them too.

Straight about one thing: this workshop is a new offer and no company has run it yet. That is why the first one is free, in exchange for a case study we can publish. You get the full day at no cost, we get the proof. If you would rather not be first, wait for the case study.

Read the team page.

What your team walks away with

Four concrete outputs: an honest audit of your current AI dev tooling maturity, a working sub-agent your engineers built during the session on one of your real workflows, the production patterns behind it (sub-agents, hooks, MCP, skills), and a written roadmap for scaling Claude Code across the team.

• An audit of where you are now. What your team already does well with AI tooling, and where the time is actually going.
• A sub-agent that runs. Built during the workshop, on a workflow you picked, on your stack. Not a toy example.
• The production patterns. Sub-agents, hooks as enforcement, MCP integrations, and reusable skills. Why each one exists and when it is the wrong tool.
• A rollout roadmap. A written document your team can act on after we leave, not a feeling that it was a nice day.

One day or three days

The one-day format covers the core: setup, the patterns, and one working sub-agent. The three-day format adds depth on reliability and enforcement, integrations into your own systems, and a second agent your team builds with less help, which is where the learning actually lands.

Who this is for, and who it is not for

This is for engineering teams that already write code and want to use AI agents seriously in their own workflow. It is not an introduction to AI for non-technical staff, and it is not a sales session for our build work.

• Good fit: a team of 3 to 12 engineers, with a real workflow they want to automate and access to their own systems during the session.
• Poor fit: a general AI awareness session for a mixed audience. We will tell you so instead of taking the booking.
• Not a pitch. If your team can do the work themselves after the workshop, that is the correct outcome and we are fine with it.

Price

1,500 EUR for the one-day workshop, 5,000 EUR for the three-day format, remote. The first workshop we run for a company is free in exchange for a case study we can publish.

The price covers preparation on your stack, delivery, and the roadmap document. Travel is quoted separately if you want it on site. There is no per-seat fee: the price is for the team.