4 dedicated team sessions
Private to your team, built around the work you actually have in front of you — not a generic syllabus. We pick real problems and ship against them, together.
← Goal‑Driven Design · the team plan
The same cohort, focused on your team's real work. Up to 7 people learn to build with Claude Code together, on the same problems, in the same shared way of working — so the practice survives the cohort and lives in how the team ships.
One price, €2,700, for up to 7 people. Everything in the Standard tier for up to 7 people, plus four dedicated sessions for your team.
Private to your team, built around the work you actually have in front of you — not a generic syllabus. We pick real problems and ship against them, together.
All 10 live sessions + recordings, weekly homework and Show & Tell, plus a team project review.
Your team stays in the same room between sessions — questions, wins, and blockers shared as they happen, not saved for the next call.
The same goal-first templates and skills the cohort uses, ready to drop into your repos and adapt to how your team already works.
A one-off workshop wears off. The goal with a team is a shared way of working that outlives the cohort — the same mental model, the same vocabulary, the same goal-first habit, held by everyone who ships.
The dedicated sessions aren't a demo deck. We take problems your team already has — a slow process, a manual report, a prototype you keep putting off — and build against them live. Learning by doing on real projects, never passive consumption. Show, don't just tell.
The thing that breaks every cohort is undefined jargon and a zoo of tools. So we put the whole board — agent, sub-agent, skill, MCP, plugin, goal — on one map, and no concept gets used before it's named. A team that shares one model can actually hand work to each other.
Across five cohorts the lesson was the same: new terms arrived faster than people could absorb them. So we hold a hard budget — a few tools per session, the rest in an appendix. Cutting is the fix, not adding. A team leaves with a small set of things it genuinely owns, not a long list it half-remembers.
Start from the change you want in the world, not from how it looks — then keep taste all the way through to ship. For a team this is the real upgrade: a common standard for what "good" and "done" mean, so the work coheres no matter who built which piece.
Every session opens with a short unblock clinic, and people who are behind get direct support, not a public spotlight. A safe room where questions aren't judged and mistakes are how you learn — under Chatham House Rule, so a team can be honest about what it doesn't yet know.
No toy demos. By the end each person has deployed a real thing and the team has a sustainable practice — context discipline, reusable skills, a goal-first habit — that keeps working long after the last session.
Motka — a product-design & UX/UI studio (Moscow / Ljubljana, founded 2005, ~11–15 people) — brought its team through the cohort over six weeks. Long-tenured Figma masters, openly skeptical at the start. They picked their own real projects — a Figma → Webflow exporter, a commercial-proposal generator, a 20-year studio knowledge base, a telecom client portal — and built against them, together. What follows is verbatim, translated from the sessions.
“Night and day between where we started and where we are. A while ago I was a real skeptic — I deliberately held that position. Now it’s a genuine shift in my thinking. I’m definitely ready to recommend your training to anyone who asks.”
“We’re already using it in real combat — it really accelerates us. A landing page that used to take hours, done in a couple of iterations.”
“It really changed my way of thinking about what you can do with this. And the main thing is that I managed to make something myself.”
“A really huge tool suddenly appeared in my hands. It’s like a whole new chunk of life appeared — I’ve become quite bold with all of it.”
What the team shipped during the cohort:
Beyond Motka, Gleb has facilitated corporate group sessions in other settings — including a retail operations team working through where AI actually belongs in their processes. The pattern holds: start from the team’s real work, not a syllabus.
Teaching one person is teaching a skill. Teaching a team is changing how a group works together — and that's a different job.
Product, design, and founder-led teams of up to 7 people who want to adopt Claude Code together, on purpose — not one champion poking at it alone.
You want one shared, goal-first way of building with AI — and a standard of taste that holds across everyone's work.
You're small and fast and want the whole team fluent at once, building on the real problems in front of the company.
You've seen one person get results with Claude Code and want it to become how the team works, not a one-off.
Not sure it fits? Message Gleb on WhatsApp and we'll work out whether a team seat or individual seats make more sense for you.
Make this
how your team
works
Up to 7 people, four dedicated sessions, one shared practice. €2,700.
← Back to the main page · need an invoice? WhatsApp +49 176 85278763