Claude Code Training

Ship with Claude Code on one shared setup

Your team learns to use Claude Code on its own repo and issues.

Book a free audit call
companies helped
60+
to first use case
10 days
code and IP yours
100%

How it connects

One team request comes in. Your team learns on real work.

You tell us who needs training and what they do all day. We build the sessions around your real tasks. People leave with a working setup, not slides.

Simulation runningHandled in this demo 0
REQUEST INAY PLANSYOU APPROVEKICKOFFTEAM GETSEmailteam and goalIntro callfree callRequest formroles and sizeAY training planbuilt on your work✓ lists the roles✓ finds real tasks✓ sets the skill level✓ picks the exercises✓ drafts the agendaYou approveagenda sent for reviewapprove, or change itApproveEditSessions bookeddates are setattendees are listedsetup steps go outLive sessionshands-on, your tasksWorking setuptools ready per personPlaybookprompts that workedFollow-up callfix what got stuckREQUEST INAY PLANSYOU APPROVEKICKOFFTEAM GETSEmailteam and goalIntro callfree callRequest formroles and sizeAY training planbuilt on your work✓ lists the roles✓ finds real tasks✓ sets the skill level✓ picks the exercises✓ drafts the agendaYou approveagenda sent for reviewapprove, or change itApproveEditSessions bookeddates are setattendees are listedsetup steps go outLive sessionshands-on, your tasksWorking setuptools ready per personPlaybookprompts that workedFollow-up callfix what got stuck

Built on your real tasks, not generic slides. Your team keeps everything we make.

Who
You or your team lead
Tool
Inbox, intro call or request form
What happens
You tell us who needs training, what they do and what they use today.
Logged
Request, channel, time received

Quick answer

AY Automate, an independent Claude implementation agency, offers Claude Code training: a free 52-Day Claude Code Challenge for self-serve learning, and a live team workshop on your own repository that ends with a shared Claude Code environment installed. Pricing: Free 52-day course: no charge.

Trusted by teams at

  • Sage
  • Wonderbox
  • Neoday
  • XGrowth
  • Arcads
  • Argil
  • Earleads
  • Just Russel
What it is

Two ways to learn Claude Code with us

The free route is the 52-Day Claude Code Challenge. Every day is a project: setup, hooks, MCP servers, subagents and a second brain. You can start today and stop whenever you have what you need.

The team route is a live workshop on your own repo. It covers setup, hooks and skills for your stack, MCP with scoped access, prompt injection and permission basics, and a shared CLAUDE.md your team keeps. It ends with the environment installed on every laptop, which is the difference between a workshop people enjoy and one they use the next morning.

If you want an engineer to keep the setup current after the session, that is our regular partnership: an engineer on your team, set up in hours, from $3K a month. A 90-day replacement guarantee applies. Training does not require it.

Comparing options before you commit? Read: Claude Code training for teams.

Fit check

Is this the right fit?

Where this wins

  • Developers who want to learn on their own

    The 52-Day Claude Code Challenge is free. One project a day, from first install to hooks, MCP servers and agent swarms.

  • Teams where every developer has a different setup

    One live session on your repo gets everyone onto the same CLAUDE.md, hooks, skills and permission policy.

  • Technical leads who need a safe rollout

    We cover what the agent may read and run, which MCP servers to allow, and how to spot prompt injection before it reaches production.

When NOT to use this

  • Nobody on your team uses an AI coding tool yet. Try the free course first, then book a workshop once there is something to standardize.
  • You need a security review of a setup that already runs. Book the Claude Code security audit instead.
  • You want a general AI course for non-technical staff. Custom training covers that and is not specific to Claude Code.
How it works

How a team workshop runs

A 30-minute call first, so the session fits your stack instead of a generic agenda.

  1. 01

    Free call

    We look at how your developers use Claude Code today and what worries your tech lead.

    DeliverableA short list of what the session covers

  2. 02

    Prepare on your stack

    We read a slice of your repo so examples use your code, not a toy project.

    DeliverableExercises built on your repository

  3. 03

    Live session

    Setup, hooks, skills and MCP servers, with permissions and prompt injection covered along the way.

    DeliverableEvery developer on the same environment

  4. 04

    Install and hand over

    The shared CLAUDE.md, hooks, skills and allowlist go into your repo.

    DeliverableA setup your team owns and can change

Typical timeline

Setup on every laptop takes hours. Workshop format and length are agreed on the call.

Stack we build with

Claude Code · Claude · MCP · TypeScript · Python · GitHub

Use cases

What we teach

Hooks and skills

Block commands that should never run, and package your repeat work so Claude Code does it the same way every time.

MCP servers with scoped access

Connect Claude Code to your database, CRM and internal tools without handing it every key.

Permissions and prompt injection

What the agent may read, run and send, and how a hidden instruction in a file turns into an action.

Scope

What the team leaves with

In scope

  • The same Claude Code setup on every laptop, in hours
  • A CLAUDE.md, hooks and skills built on your own code
  • An MCP allowlist and a permission policy
  • A short playbook the team keeps

Not in scope

  • Slide decks with no installed setup behind them
  • Training on tools your team does not use
  • Security sign-off, which stays with your security lead
The team is super fast - sometimes we had to slow them down. We managed to scale the company without investing into hiring.
Elie Salame
Elie Salame
COO, Adstronaut.io
Their communication is fast and easy. The team is very skilled and works quickly - you can really see the quality in what they deliver.
Ana Maria Martinez
Ana Maria Martinez
Founder, EasyClickWeb
Pricing

What it costs

The course is free. A team workshop is priced after the call. Our regular partnership has one published price.

Free 52-day course

No charge

The 52-Day Claude Code Challenge. Self-serve, one project a day, no signup wall.

Team workshop

Shared on the call

Live, on your own repo, ending with the shared environment installed.

Monthly partnership

From $3K a month

An engineer on your team keeps the setup current. A 90-day replacement guarantee applies. You keep what we build if you cancel.

FAQ

Claude Code training questions

Is there a free Claude Code course?

Yes. The 52-Day Claude Code Challenge is free, with one project a day. It covers setup, hooks, MCP servers, subagents and a second brain, with no signup wall.

Do you run Claude Code workshops for teams?

Yes. A live session on your own repo that ends with the shared environment installed. Format and length are agreed on a free 30-minute call.

Who is the training for?

Developers and technical leads who already use an AI coding tool and want a shared, safe setup.

What does the team leave with?

The same setup on every laptop, a CLAUDE.md, hooks and skills built on your own code, an MCP allowlist and a permission policy.

Can training lead to a longer engagement?

Yes. An engineer on your team, set up in hours, from $3K a month. A 90-day replacement guarantee applies. Training does not require it.

I.Next step

Get your team on one Claude Code setup

A free 30-minute call. We look at how your developers use Claude Code and tell you what a session on your repo would cover.
  1. i. Today

    Tell us what you need

    We discuss the problem and what a good outcome looks like.

  2. ii. This week

    Share the details

    Send relevant examples so we can identify a practical starting point.

  3. iii. Next call

    Review the plan

    We discuss scope, responsibilities, timing and cost.

What we need from you

A short description of the problem, the tools or team involved, and any examples you can share.