Your team, multiplied by 10.In a room or at their own pace.
Claude Code training built on your team's real files and workflows, in the format that fits: a one-day workshop at your office, a custom self-paced course as a benefit for your people, or seats in the program with a volume discount. They arrive knowing ChatGPT. They leave with work that does itself, the habit of delegating it and a certificate each. No coding.
Teams at 10+ companies took the workshop. NPS 90+ from participants.
Three ways to train your team.
Same method, same exercises, on your team's real work. Pick the format that fits how your team works, or combine them.
A one-day workshop, in person
A day at your office with an instructor at their side. Exercises built on your files, working systems by the evening, and 30 days of email support after. Best when you want the habit to form in one day, together.
A custom self-paced course, as a benefit
We build a course on your team's workflows and tools. Each person takes it inside their own Claude Code, at their own pace, wherever they are. Offered to your people as a corporate benefit, with a certificate for each person who completes it.
The program, with a volume discount
Seats in the regular self-paced program for the whole team, at a volume discount. The same modules one person gets, each in their own Claude Code, with a certificate at the end. The fastest way to get everyone started.
The same week, before and after.
What changes when everyone on the team can hand work to AI, not only the one person who is into it.
Before
- Monday's report takes the whole afternoon, every week.
- Data lives in five tools and moves between them by copy and paste.
- One person is the one who knows AI. Everyone else waits for them.
- A small internal tool means a ticket to IT and a quarter of waiting.
- Everyone has tried ChatGPT. Nothing has changed in how the team works.
After
- The report builds itself from the data. Someone reads it; nobody assembles it.
- Files sort, rename and summarise themselves in seconds.
- Everyone delegates. The work spreads across the team, not around one person.
- The tool the team needed exists, built during the training, and it grows every week.
- AI is part of how the team works, within rules your company is comfortable with.
How it works.
Three steps, from a call to a team that keeps running it on its own.
- 01
A 30-minute call
We map your team's week: what eats their hours, which tools they use, what they would hand over first. That decides the format and the content.
- 02
Designed on your work
We build the exercises on your real files and workflows, not on examples. In a room or in the chat, every block ends with something of yours finished.
- 03
The team does it, and it sticks
Your team learns by delegating real tasks, live with an instructor or module by module in their own Claude Code. They leave with working systems, the habit and a certificate each.
What your team will be able to do after.
Every person on the team, not only the one who is into AI. On their own files, from the first week.
Without writing a line of code, and without a ticket to IT.
Hand over a folder of hundreds of documents and get back the answer.
Invoices, contracts, reports: read, sorted and summarised while the team gets on with the day.
Have the weekly report build itself from the data.
Monday's deck, written with your numbers and your template. Someone reads it; nobody assembles it.
Get proposals, emails and briefs in each person's own voice.
It knows their role, your business and their tone, because they told it once.
Work on your real data without opening Excel.
Connected to the tools the team already uses, with no copy and paste between them.
Turn anything the team repeats into a one-word command.
Set up once, shared across the team, running every week.
Build the internal tool the team needed, and grow it every week.
Live for the team or your clients, without a ticket to IT.
Work within rules your company is comfortable with.
Which files are in scope, which are not, and how each person sets that up.
Spread the work across the team, not around one person.
Everyone delegates. The habit that makes the rest stick.
What your team leaves with.
Not a slide deck. Working systems, built on your own work, and what it takes to keep going.
- The systems built during the training, ready to run on Monday.
- A memory file for each person: who they are, how they write, what they work on.
- A library of reusable skills for the tasks your team repeats.
- A cheatsheet of more than 50 ready-to-use commands.
- A certificate for each person who completes it.
- Access to the alumni community.
The numbers from the room.
Every workshop ends with a survey. These are the results so far.
1 day
from the first brief to a working prototype the team built itself
90+
NPS from workshop participants
100%
of participants finish the day and leave with something working
NPS and completion measured at the end of each workshop, across every workshop run so far.
Questions teams ask first.
Straight answers. Anything else, ask in the form and a person replies.
Does the team need to know how to code?
No. Not one line. Every format is for people who do not code and never intend to. If they can explain a task to a colleague, they can delegate it.
Which format is right for us?
A workshop when you want the whole team to form the habit in one day, together. A custom self-paced course when people work at different rhythms or in different places, or when you want to offer it as a benefit. The program with a volume discount when you want everyone started fast, with no custom work. We help you choose on the call.
How many people can join?
A workshop works best with 6 to 15 people. Bigger teams run in groups, same content, one day each, so every person gets the instructor's attention. The self-paced formats have no limit.
In person or remote?
Workshops are in person, at your office: it is a day of doing, not watching, and a room is where the habit forms. Remote sessions are possible for distributed teams. The self-paced formats are remote by design: each person works in their own Claude Code, wherever they are.
What does the team need?
A Mac or Windows laptop each and a Claude subscription, which we help you set up beforehand. Nothing to install on your servers and no IT project.
Is our data safe?
Claude Code works only in the folders each person opens and sends Anthropic what the task at hand needs. We start with the rules: which files are in scope, which are not, and how to set that up. Bring your policy and we design around it.
English or Spanish?
Either, or both. Workshops and courses run in English and in Spanish.
How is it priced?
It depends on the format: one price per workshop, a project price for a custom course, and a per-seat price with a volume discount for the program. We quote after the call, once we know the size of the group and the scope.
What happens after?
The team keeps the systems it built and the habit of using them. After a workshop we stay on email for 30 days. When the team is ready, the next step is natural: a second day, the advanced modules or the next set of tasks.
Tell us about your team.
Five questions. We read every one, and a person replies within one working day to set up a 30-minute call and find the format that fits.
Received. Thank you.
A person will reply within one working day to set up a 30-minute call. Check your inbox.
Prefer to start with one person?
The self-paced program opens soon: the same method, one person at a time, at their own pace. Join the waitlist and be first in.