Team Coaching & Training
Workshops and ongoing coaching so your team can run with AI on its own — without depending on me.
Who this is for
Teams that already passed the “is AI useful?” stage and now need to make it stick. Engineering managers who want their team confident, not anxious, about the new tools.
Typical cohort: five to twenty engineers, two to four tech leads, optional product owner.
What you get
- Two workshops (live, on-site or remote) — one on prompt engineering for code, one on quality and security gates for AI output.
- A written playbook — the patterns we use, the prompts that work, the review checklists. Yours to keep.
- Four weeks of coaching — one 60-minute session per week with your tech leads. Async questions answered within one working day.
- Optional follow-up — a second cohort, a deeper workshop on a specific topic, or a quarterly check-in.
How it works
1. Discovery call (45 min)
We agree on the team, the goals, and the dates. No 40-page needs analysis.
2. Workshop week (3 working days)
Two half-day workshops, recorded, with the playbook handed out at the end. Attendees leave with patterns they can use the next morning.
3. Coaching month (4 weeks)
Weekly session with the leads, async access for the rest of the team. We work on whatever you are actually shipping.
4. Optional follow-up
Most teams book a second cohort two months later. Some book a quarterly check-in. Some stop here and that is fine too.
Deliverables
- Two recorded workshops.
- The playbook (Notion or PDF).
- Four weekly coaching sessions.
- Async support during the coaching month.
FAQ
Do you do this fully remote? Yes. Workshops on Zoom or your video tool. Coaching on the same.
What level are the workshops pitched at? Senior engineers and tech leads. If your team is mostly junior, we should do an extra foundations workshop first.
Can product managers attend? The prompt engineering workshop is fine for PMs. The quality and security gates workshop is more useful for engineers — PMs usually skip that one.
What languages and tools do you cover? TypeScript, Python, Go most often. Cursor, Copilot, Claude Code, and self-hosted models. The patterns transfer even if your stack is different.
Do you sell this as a course? No. It is a workshop, recorded once, run live for your team. The playbook is yours to adapt.