A 2-day intensive for technical teams. You learn two things at once: how to use AI agents in your daily work with code, and how to build your own agents so they survive past the demo. Zero slideware theory — you leave with the knowledge and with working code.
Looking for training for a large group — dozens or hundreds of people at your own event, or a series of sessions across a season? That is a different offer from this page. This one is two days at open laptops, for people who write code. See the speaking offer →
days of intensive work
people max per group
hands-on modules
hands-on coding
Every module ends with working code. Not slides. Not discussion. Code you can ship to production the next day.
Strategic decisions on AI architecture and the technical roadmap.
Practical patterns and best practices to roll out across the team.
Deep knowledge of building and debugging agents.
Understanding what AI can and can't do, for better product decisions.
This workshop is for people who write code for two days — hence the open laptops and the group of up to 12. If what you have is a room that came to listen rather than to code — dozens or hundreds of people, technical or not — and what you need is a talk or a session at your own event, or a series of them across a season, that is a different job. I do that too; it just looks and costs differently.
See the speaking offerper team of up to 12 / 2 days
The same programme and the same exercises, without the travel and the time in transit — and that is the whole of the price difference. Hours are flexible around CET/CEST. Nothing to fly anywhere for, and nothing to negotiate before you can approve a number.
per team of up to 12 / 2 days
I come to your company. For teams with no agent experience I recommend a room — on site it is easier to catch the moment someone gets stuck and says nothing.
In both variants:
Bigger technical team, or a few editions a year? I'll quote a package.
Let's talk about a package
This price is for a team that writes code. A large group without laptops is quoted differently — the speaking rates
I don't teach from books. I teach from systems I built myself that run in production for real companies.
3 companies built from scratch. An exit to Diagnostyka. 55+ people in the tech teams I've led. I know what "the agent went down at 3 a.m." means. And I know how to avoid it.
I run this as a Claude Certified Architect (Foundations) and holder of the Claude Partner Badge — Claude Code.
Three rooms I can say something concrete about. The first two were the format described on the speaking page, not these two days at laptops; both left a public trace you can check yourself: the client's own page and a recording. The third left none, and that is normal too.
A room in Warsaw, TVP bureaus across the country on a stream, and chatbots in journalistic work as the subject. A non-technical audience, a public broadcaster as the client, a hybrid format. A room like that lets no jargon through, so the programme has to hold up without it.
A conference talk for people who build products. The recording is public, so you can check the tone and the level before you talk to me. The talk is in Polish.
Watch the recordingNot every client agrees to be named, and that is their call. I sign an NDA before the first detailed conversation. So a project stays described as a global brand or a medical distributor, with no logo and no company name.
Two delivery variants, two prices. Live online: from 4,800 USD per team of up to 12 people for 2 days. On-site at your company: from 6,400 USD, travel included. Both variants run the same programme, with the same exercises, the same materials and repository, 30 days of post-workshop support and certificates — nothing in the scope changes. The higher price covers the travel, the time in transit and what cannot be shipped to a screen: printed materials and a shared room. Larger teams or several editions a year — package pricing after a call.
Optimally 4–12 people — few enough that everyone writes code, enough for pair-coding sessions to work. Larger groups are split into editions.
The core of the program is hands-on and assumes engineering experience (senior developers, AI leads). CTOs and product managers take away the architecture, risks and decisions — no coding required.
No. This workshop is for teams that write code: up to 12 people, two days, laptops open. A room that came to listen — dozens of people or more, technical or not — is a talk or a department session. That is a separate offer, described on the speaking page: the rates and the inquiry form are there.
Both are full variants and each has its own price. Online is from 4,800 USD: the same programme live over Zoom or Meet, session recordings to replay, breakout rooms for pair coding and flexible hours around CET/CEST. On-site is from 6,400 USD: I come to your company in Poland or Europe with travel included, participants get printed materials, and two days in one room buy what a call cannot — the conversations beside the agenda, and a team that ends the workshop knowing each other better. If the team has never worked with agents, pick on-site: in a room it is easier to see the person who is stuck before they say so.
Live over Zoom or Meet, two days and six modules with nothing cut — the exercises are the same ones the on-site variant runs. Pair coding moves into breakout rooms. Sessions are recorded so the team can replay them; the recording is arranged before we start, because what it captures is people rather than slides. Hours are set flexibly around CET/CEST, the same way the dates are. There is no open-enrolment edition and no self-paced course to watch later: this is a led workshop for one team.
I come to your company in Poland or Europe and the travel is in the price. Two days at open laptops, up to 12 people, the same programme and the same exercises the online variant runs. Participants get printed materials to keep, and being in one room is what lets me see the person who is stuck before they say so. Dates are arranged individually, typically 3–6 weeks ahead.
They will have built an agent from scratch — from architecture to deployment — plus verification, security and monitoring patterns ready for production. If you need hands afterwards, I also deliver AI implementations and AI consulting.
You can. The workshop material touches the ground that Claude Certified Architect – Foundations tests. It is not exam prep and I do not promise a pass. Treat the certificate as a pleasant by-product. The workshop is about the team being able to use coding agents in their work and build their own agents properly.
Polish and English. Both are standard rather than an option on request: I run the masterclass in English at WaysConf 2026. A language-mixed team gets the materials in one language, and I match the delivery to the room.
Typically 3–6 weeks. A shorter lead time is sometimes possible, but then the programme adapts to what can be prepared rather than the other way round. Dates are arranged individually; there is no fixed calendar of open editions.
I reply within 24h. No strings attached.