Live workshops · small groups or 1:1

Learn AI on your actual work.

Short, practical courses for busy business people. One skill per week, a live demo, and a guided lab where you leave with something finished — not notes to catch up on later.

See the courses How a session runs

The Claude Intensive The Engineering AI Intensive More announced regularly

The Catalogue

Current and upcoming courses

Each course is a self-contained arc. Pick the one that matches the bottleneck you are actually hitting, and we start there.

Now enrolling 6 weeks · 2 hours per week

The Claude Intensive

Six weeks. One skill a week. Applied to your actual work.

A practical, no-rush programme for busy business owners and professionals who want real, measurable value out of AI. Two hours a week for six weeks, and every session ends with something finished on your own work — not homework for its own sake.

View full syllabus Ask a question

What you walk away with

✓ Delegate real work to Claude with prompts that actually hold up
✓ Organise files and research with proper permissions and safety habits
✓ Turn messy research into client-ready documents and decks
✓ Automate recurring work with projects, schedules and plugins
✓ Know what not to paste, and how to review what comes back

Effort

~2 hours a week, plus light prep

Weeks

6 weeks

Session time

2h per session

Formats

1:1 private · Small group (max 6)

Now enrolling 6 weeks · 2 hours per week

The Engineering AI Intensive

Recover engineering time across the whole lifecycle — not just the coding step.

A six-week programme for an intact engineering team. Not Claude training, and not another dev-tool license: six sessions spent finding where engineering time actually leaks — review backlogs, stale docs, manual QA, onboarding, ticket triage — and reclaiming it with Claude Code and Cowork. Run it for the whole team, because the value shows up in handoffs, not just in commits.

View full syllabus Ask a question

What you walk away with

✓ A measured before-and-after on PR cycle time, onboarding time or review turnaround
✓ Team conventions for AI-assisted code: shared prompts, project setups, review guidelines
✓ Claude Code used for real delegated work, not autocomplete
✓ Cross-functional workflows that PM, support, docs and QA can run themselves
✓ A company-specific starter kit the team keeps using after the programme ends

Effort

2 hours a week for the whole team, plus homework

Weeks

6 weeks

Session time

2h per session

Formats

Whole-team workshop · Optional IC and lead/manager tracks

Next up

More courses are being written

The format stays the same: one skill a week, real work as the lab, and a plan you keep afterwards. Tell me which bottleneck you want covered next and it shapes the next cohort.

Suggest a topic

Session Structure

The same shape every week, whichever course you take

Two hours goes fast if nobody knows what is happening. Every session runs the same rhythm, so the only new thing each week is the skill itself.

15 min

Recap

Where you got to, what got stuck, quick wins.

30 min

Concept + demo

One idea, shown live on a real example.

45 min

Guided lab

You work, I coach in real time.

20 min

Industry breakout

Tailored to your sector and your actual files.

10 min

Homework

One concrete task before next week.

Every course runs this shape. Team sessions shift a few minutes into role breakouts, and this is a baseline rather than a rule — multiple batches per week are possible, and the time split gets rebalanced depending on what a group is struggling with.

Ways to Take It

One person, a small cohort, or your whole engineering team

The same discipline every time: real work as the lab material, and something your team keeps using after I leave.

1:1

Private coaching

The full syllabus, run against your own files, your industry and your week. Pacing adjusts to your calendar, and we can split the two hours across more sessions when that fits better.

✓ Your own tools, your own documents, your own pace
✓ Rescheduled when a real week gets in the way
✓ Labs redesigned around what you actually do

Small group

Cohort, capped at six

Same material, same structure, shared live session — and other people’s approaches to steal. Breakouts split by industry so a marketing week still lands for a finance audience.

✓ Lower cost per participant
✓ Industry breakouts inside each session
✓ Fixed cohort schedule, easy to plan around

Whole team

Engineering organisations

Run for an intact team — developers plus a PM, QA lead or tech writer, because the handoffs between them are where the time leaks. Tailored to your stack and your biggest time-sink before the first session.

✓ Examples drawn from your own repository
✓ Baseline measured before, re-measured after
✓ Company-specific starter kit you keep