Claude Code training

Engineers who ship with agents every day.

Live sessions for one engineering team, taught on its own work. Each session ends in shipped code, so the team goes from trying agents to using them daily.

Live sessions
run by the founder
Your own work
never a demo app
Fixed price
agreed before you join
This week Build a first agent your team will use
Checklist 5 of 6 done
Watch: how an agent uses toolsVideo, 18 min
Read: writing evals your team trustsGuide, 12 min
Map three tasks from your own teamExercise
Build a first agent on your own dataLab, 60 min
Share it in the cohort reviewLive session
Bring one question to office hoursOptional
Cohort progress79%
19 of 24 people finished this week
Next live sessionCohort review, Thursday 4pm
BookedAdd to calendar
Before and after

What changes for each participant

For engineering teams whose engineers already have coding agents and each use them differently.

  1. Before: it was taught on someone else’s code.

    A demo app has no history and no odd module. The first real ticket looks nothing like the exercise.

  2. Before: every engineer set it up alone.

    One person’s instructions live on one laptop, and the agent behaves differently for each of them.

  3. After: one shared setup in the repo.

    Instructions, permissions, specs and review rules live where the next engineer looks first.

The sessions

What your team has at the end of each session

Every session is live, run by the founder, on your own work.

  1. Session 1One shared setup: instructions and permissions in the repo.

    Leave with the setup committed.

  2. Session 2Tickets become specs before the agent starts.

    Leave with a spec skill the team runs on the next ticket.

  3. Session 3Context the agent reads first.

    Leave with the files that stop it guessing.

  4. Session 4Code review that checks each change does what the ticket asked.

    Leave with a review skill and a shared definition of done.

  5. After the last sessionRunning on your own work

    We run the sessions on your repo with your team. Every session ends in a commit, so the habit stays after we leave.

Fit

Is the Agentic SDLC Masterclass right for your team?

It fits when

  • For engineering teams whose engineers already have coding agents and each use them differently.
  • You bring your own work to the sessions.

It does not fit when

  • You want a recorded course to watch alone.
  • You want a demo app in place of your own work.
Fixed quoteOne price, agreed before work starts

The quote is fixed before you join, and you get the dates and the joining details before you commit. Full refund after Week 1 if not satisfied. No questions asked.

Apply on a callSee starting prices
FAQ

Questions about the Agentic SDLC Masterclass

Is there Claude Code training for teams?

Yes. This masterclass runs on your own repo with the whole team in the room.

Do you need access to our code?

We work in the repo you pick, with the access you give. Every file the sessions write is committed to your repo.

Can the training be remote or onsite?

Both. Remote sessions run live on a call with everyone in your repo. Onsite sessions run in your office.

What is the difference between training and a rollout?

Training teaches one team and leaves the setup files in its repo. A Claude Code rollout puts every engineer on the same managed setup across the company.

We run the sessions on your repo with your team. Every session ends in a commit, so the habit stays after we leave.

For engineering teams whose engineers already have coding agents and each use them differently. We share the next start dates on the call.