AI Workshops for Dev Teams

I don't teach AI tools.
I get your team wanting to use them.

A full day on your team's real backlog — not a course. Real tickets, real workflows, no artificial exercises.

Up to 6 devs / session English or Czech Built around your stack & backlog 2-week adoption follow-up

AI workshops built around your stack

No artificial exercises. I map the workshop to your tools, codebase, and team level — so developers leave with real habits, not theory.

check_circle Work on your actual backlog tickets — not fake exercises
check_circle Real workflows, real codebase, real results
claude · ~/aimi-workshop-site
╭─────────────────────────────────────────╮
│ ✻ Welcome to Claude Code                │
│                                         │
│   /help for help                        │
│   cwd: ~/aimi-workshop-site             │
╰─────────────────────────────────────────╯
> write me a fake claude code session for an AI workshop landing page
that trope's tired. tell them what's true — 9 workshops, plus a lecture and a management consultancy. 5 repeats from one client. three years tracking agentic development since the field formed. people book on proof, not a staged bug fix.
> fair. headline?
"i don't teach AI tools. i get your team wanting to use them." — your line, not mine.
╭─────────────────────────────────────────╮
│ >                                      │
╰─────────────────────────────────────────╯
? for shortcuts claude opus-4-7
Workshops delivered · 2025 → 2026 5× repeat, one client
Same client, repeat New client
9
workshops
same client
30
people, one client

The signal isn't velocity. It's repeat bookings.

Most workshop pitches lead with productivity metrics — and those are infamously hard to track honestly. The signal that actually means something is who books again. One client has run 5 sessions, reaching 30 people across engineering, UX, DevOps, and management.

“Simon delivered exactly that. The workshop was very well received by everyone who attended.”

Alexandros Koukovistas · Kentico
Šimon Demočko teaching at a whiteboard

Why teams trust me with this

I don't teach from a manual. After years as a developer and three years tracking agentic development since the field formed, I know where AI tends to fail in a real codebase — and the friction points keep shifting. I follow that shift through my own work and the community I'm in, so what we cover reflects what's currently breaking, not last year's pain points.

My approach is deeply technical. Across 9 workshops, plus a company-wide lecture and a 90-minute management consultancy, I've refined a curriculum that bypasses the “chat interface” hype and focuses on the underlying logic of AI-native development.

“…help our team adopt AI tools, gain confidence in the results, and improve their overall mastery. Simon delivered exactly that.”

Alexandros Koukovistas · Kentico

What's included

One focused format. Designed for teams ready to actually change how they work.

Private Team Workshop

Full day  ·  remote or on-site

Flat scoped rate per engagement — based on team size, location, and depth.

A full day working on your actual backlog — no artificial exercises, no theory. I prepare around your stack, your tools, and your team's real situation.

  • circle Up to 6 developers per session
  • circle Custom agenda built around your codebase
  • circle Remote or on-site (travel covered separately)
  • circle English or Czech
Book a 30-min Discovery Call

Open Cohort — coming soon

Pricing TBD

Individual seats — learn alongside senior developers from other companies.

Structured curriculum, peer networking, shared experience.

  • circle 12–14 seats per cohort
  • circle Structured curriculum
  • circle Peer networking

Real feedback

Verbatim, from Kentico.

“We were looking for someone with real hands-on experience using Claude in development workflows who could help our team better understand how to adopt AI tools, gain confidence in the results, and improve their overall mastery. Simon delivered exactly that. The workshop was very well received by everyone who attended. Simon was professional, engaging, and accommodating throughout the process, even working flexibly with our timelines.”

Alexandros Koukovistas Kentico

What a workshop day looks like

Hands-on work on your real backlog, with theory and Claude Code features woven in where they fit. The day is shaped to wherever your team actually is — below shows what a foundations-leaning day looks like next to an advanced-leaning one. Yours lands somewhere on that spectrum, not on either extreme.

Foundations-leaning day

Sample — when the team is new to agentic AI tools.

9:00

Welcome & setup

Environment check. Each person shares role, current AI usage, and what they want to leave with.

9:30

Why most teams plateau on AI

The mental models that make AI tools click — why typing more isn't the answer.

10:30
Live demo

I work a real ticket, end to end

A realistic ticket solved live. The team sees the full cycle before doing it themselves.

11:00
Hands-on

Foundations

Productive setup, scoping context, the daily-use patterns experienced developers rely on.

13:00

Lunch

Often where the most interesting questions surface.

13:30
Hands-on

Working with unfamiliar code

A refactor or coverage gap that's been postponed for months — the team works it through together.

15:00
Hands-on

Effective workflows

Patterns that compound: when to delegate, when to verify, when to step in.

16:00
Hands-on

Your real backlog

The team applies everything to a ticket of their choice.

16:30

Team presentations

Each group shares the problem, the approach, the wins, the surprises.

17:00

Wrap-up

Security, staying current, follow-up. I check in 2 weeks later.

Advanced-leaning day

Sample — when the team already uses AI tools daily.

9:00

Welcome & setup

Where each person currently is and where they want to push next.

9:30

Beyond first-year adoption

Where senior users get stuck. The leverage moves you don't get from a tutorial.

10:30
Live demo

A non-trivial problem, live

A demo that uses the parts of the toolset your team probably hasn't tried yet.

11:00
Hands-on

Power features

Parallelism, delegation, automation. The compounding moves.

13:00

Lunch

Same lunch, different conversations.

13:30
Hands-on

Customizing the agent

Adapting the tool to your team's workflow — not the other way around.

15:00
Hands-on

Scaling responsibly

Security, ops, configuration. What changes when this goes from one developer to the whole team.

16:00
Hands-on

Ambitious project work

Full autonomy on the most ambitious thing in your backlog.

16:30

Team presentations

Each group shares findings — discoveries compound.

17:00

Wrap-up

Security, staying current, follow-up. I check in 2 weeks later.

Common questions

9
Workshops
EN/CZ
Languages
Repeat, one client
≤6
Devs / Session

Ready to stop waiting?

Every month of delay is a month your competitors are getting ahead. It starts with a 30-minute call.

1 30-min discovery call
2 Custom agenda built around your stack
3 Workshop day — your team ships real work
Book a Discovery Call arrow_forward

Join the Waitlist

Get a single email when the open cohort opens for booking. No newsletter, no follow-ups.