Claude Code Bootcamp
The hands-on agentic coding course with Claude Code for enterprise development teams. At the terminal, tailored to your stack and your codebase. Up to 10 participants per session, on-site. Not a demo to watch, but a method to take home.
All our projects are covered by £10 million of professional indemnity insurance (verify here)
+ an additional £1 million dedicated to data security (verify here).
























Three formats, one method.
From a kickstart day to a full bootcamp tailored to your repo. All on-site, up to 10 participants, always hands-on. The right path depends on the team: we define it together.
- Parts 01 and 02 complete
- Part 04 as a guided demo
- Environment setup as pre-work
- Prompt handout + templates
- Complete programme, all 4 parts
- Hands-on exercises for every participant
- Real group exercise, all the layers
- Complete material to take home
- The whole Bootcamp, lab on your repo
- Real CLAUDE.md on your codebase
- 30-day follow-up included
- Team .claude/ setup assistance
- optionalLab customization on your repoExercises and prompts on your real codebase
- optional30-day follow-up½ day of review on your real PRs
- on requestInternal repeat licenceMaterial and the right to re-run the course
Four pillars, one hands-on training.
Four parts that build on each other: first the levers that move Claude Code's quality, then the prompt at the terminal, then teamwork, finally real code. Each part alternates a short explanation with live exercises.
What Claude Code is and isn't. Context, prompt, verification: the three levers.
Mini-exercises at the terminal that produce results in the next 60 seconds.
Roadmap, ownership, git flow, PR review, CI as a safety net.
Group exercise: a complete real case, all the layers, on real code.
Claude Code is an agent, not an autocomplete.
Claude Code lives in your terminal.It sees the whole repo, plans before acting, runs real commands (test, git, build) and hands you back the diff — you sign off. You don't "press" it: you steer it. It's a very fast junior; you stay the senior who does code review and decides the architecture.
Quality doesn't come from magic prompts, but from three levers: context (what Claude can see), prompt (what you ask) and verification(how you check). We start here because it's the level that makes the biggest difference, on any stack.
CLAUDE.md is the most important file in the repo; attach files with @ instead of pasting; /clear when you switch task.Four exercises, a result in 60 seconds.
Straight to the terminal with Claude Code. Four live exercises, each designed to produce a verifiable result in about 60 seconds: a function, a test, a refactor, a fix. The point isn't speed for its own sake, but feeling the plan → code → test → verify loop under your fingers.
Eight commands give you 90% of the flow — /init, /context, /clear, /compact, /resume, /model, /agents, /review. Every participant works on their own terminal: with a maximum of 10 people, nobody just watches — everyone does.
Claude Code in the team flow.
The same flow as always — Commit → Push → PR → CI → Merge — only Claude helps at every step and CI is the final judge. Before the human reviewer, a code-reviewer sub-agent reads the diff and flags the easy issues (missing tests, secrets, dependency rule): the human lands on a clean PR and focuses on architecture and intent.
We see how agentic coding enters the team's real work: the 5 layers of configuration, parallel git flow, PR review with AI as the first reader, and CI as a safety net — no skips, no exceptions.
A real case, all the layers.
The most hands-on part, and the one that generates the most perceived value. In groups, on a ready demo repo, we carry a small endpoint end-to-end through all the layers — Domain, Application, Infrastructure, API and tests — with Claude Code proposing and the team verifying. The whole method from the previous parts, in a real case.
Plan mode mandatory before every change, small commits, peer review and CI as the final judge. With 10 people the hands-on is worth more than the demo: every live exercise stretches 3–4× compared to the instructor's demonstration. That's why it needs room, and why the full Bootcamp runs over two days.
What the team takes home.
Not slides, but a method the team uses from Monday morning. By the end of the bootcamp every developer can steer Claude Code on real code, with the right guardrails.
Every dev steers Claude Code on their own: context, atomic prompts, plan-first.
30 seconds of plan save 30 minutes of rollback. Diff before save, always.
Claude does the pre-review: the human focuses on architecture and intent.
CI as judge: green tests, layers respected, no secrets. No exceptions.
What we get asked the most.
Transparency first. If your question isn't here, write to us: we reply within 24h, from a real person.
Who is the Claude Code Bootcamp for?
Is it a theory or a practical course?
Why Claude Code and not an autocomplete?
Do we work on our own code or prepared examples?
What do we need to take part? Any prep beforehand?
How much does it cost?
Ready to get your team coding with AI?
A 30-minute call to understand where Claude Code can make a difference in your workflow, and build the right path. No commitment, from a real person.