The reason this is the thing people ask for first
Most owners come to us expecting to buy automation. They have seen the ads, they know a competitor is doing something with AI, and they assume the answer is a piece of software that runs in the background. Sometimes it is. But nine times out of ten the faster win is that the eight people already on payroll have no idea what the tool on their laptop can do.
They have an account. Somebody set it up. They have used it to write an email and thought "that was fine, I suppose," and then gone back to doing everything the way they did it before. That is not a people problem and it is not a motivation problem. Nobody ever showed them.
Your people aren't the problem. The tool was handed to them with no instructions, in the middle of a week that was already full.
Everybody in one room, not role by role
Plenty of training companies will sell you separate tracks. A sales track, an operations track, an admin track, each with its own day and its own invoice. We don't do that, because when you actually watch people work, the fundamentals are the same job in every seat.
Your estimator, your bookkeeper, your office manager and your service coordinator are all doing some version of the same four things: reading something long and pulling out what matters, writing something they don't enjoy writing, checking their own work, and answering the same question they answered last week. Teach that once, properly, to everyone at the same time, and the majority of every role in the building is covered.
It also does something a split track can't. When the whole team learns it together, they start swapping what they figured out. The estimator shows the coordinator a trick, somebody in accounts finds a shortcut and it spreads by lunchtime. Training people separately kills that entirely.
What we actually teach
Claude, the fundamentals
How to actually ask for something. What it is genuinely good at, where it will be confidently wrong, and how to catch that before it reaches a client.
Projects, context that sticks
Tell it about your business one time. Every conversation after that already knows your pricing, your clients and how you talk, so nobody starts from scratch every morning.
Cowork, for files and documents
Receipts, notes, transcripts and spreadsheets turned into finished work. Real document and spreadsheet output, no code, nobody has to become technical to use it.
Claude Code, for everyone
Yes, everyone. Most people find out it is closer to writing instructions than writing software, and the fear goes away in about twenty minutes.
The code lesson, and why everybody sits through it
This is the part other trainers skip, and it is the part that changes companies. We give the code session to the whole room, not just to whoever has "technical" in their job title.
Most of them will never write anything serious, and that is fine. What matters is that the mystery goes away. Once somebody has watched a working tool get built out of plain English in front of them, they stop treating the whole category as somebody else's department. They start asking better questions and they stop assuming every problem needs a new subscription.
And then the thing we are really looking for happens. One person in every company lights up. They stay after, they ask the question nobody else asked, they email you that night with something they built. That is your builder, and you almost never know in advance who it will be. We have found them in dispatch, in accounts payable and once in a service van.
Every company has one. Find them, point them at the right tool, and you have someone building what you need in house instead of buying it in.
How a first engagement runs
- A teardown first. Twenty minutes on a call before anything is booked. You walk us through a normal week and we work out what is actually worth teaching. If training is not the right answer we will say so.
- We build the session on your work. Your quotes, your files, your emails, your real week. Nothing in the room is a made-up example, because made-up examples are exactly why training doesn't stick.
- The session itself. On site or remote, the whole team, fundamentals plus the code lesson. Everybody leaves having done something real, not having watched somebody else do it.
- The deep runthrough. Whoever took to the code side gets a longer session on their own, aimed at what your business actually needs built.
- We come back. This is where it either becomes permanent or quietly dies, which is why the retainer exists.
Why a one day class is out of date by spring
This is the part most owners get wrong, and it costs them the whole investment. They buy a training day. The team is genuinely fired up for about a month. Then the tools change underneath them, the workflow they were taught stops matching what is on screen, two people leave, and six months later everyone is back to how they worked before. The money is gone and the conclusion is "AI didn't really work for us."
It did work. It just wasn't maintained. This is not a category where you can learn something once and be finished, because the ground genuinely moves. Features that did not exist in January are the fastest way to do a job by June.
You wouldn't buy a truck and never service it. This is the same argument, and it is the reason we would rather have you on a retainer than sell you one good day.
On the retainer we come back monthly. We show the team what shipped and translate it into your business rather than handing over a changelog nobody reads. We fix the workflows that did not survive contact with a real week. And your builder goes a layer deeper each visit, until somewhere around month six there is a person inside your company teaching this without us in the room. That is the goal. We stay for what is new, not because you cannot function without us.
Who is in the room
Everyone. Sales, estimating, operations, admin and front desk, finance and bookkeeping, marketing, field and service, and leadership. The management track is not a separate day, it is woven into the same session: how to lead a team that works this way, and how to tell whether it is actually working rather than whether people say it is.
Common questions
Do you train people role by role?
No. Everybody sits in the same session. The fundamentals cover the majority of what every role actually does day to day, so splitting into separate tracks mostly wastes people's time and multiplies your invoice.
The one place we go deeper is code, and that is with whoever naturally takes to it rather than whoever has the job title that suggests they should.
Is this about replacing staff?
No, and we would turn down the work if that were the goal. The entire premise is the opposite: make the people you already have faster at the job they already do.
In practice what changes is capacity. Same headcount, more work through the building, and considerably less of it happening on a Friday evening.
We are not technical. Is that a problem?
Not at all, and it is the most common thing owners worry about. The large majority of the training needs no technical background whatsoever.
The code lesson is included for everyone specifically because being scared of it is the thing holding most teams back. Watching a tool get built out of plain sentences takes the fear out of it faster than any amount of reassurance.
Can we just do a one time session?
You can, and some businesses do. We will be straight with you though: in our experience the one time version fades. The tools move, the habits slip, and within a couple of quarters you are close to where you started.
If budget means one session is what makes sense right now, we would rather do that well than talk you into something you are not ready for. We will just tell you honestly what usually happens next.
How does this fit with the systems you build?
Training almost always comes first, and it makes the build cheaper. Once the team knows what is genuinely possible, they can tell you which parts of their week are still worth automating, which is far better information than we would get from guessing.
Plenty of businesses do both. The team handles what a person should handle, and we build the systems for the jobs nobody should be doing by hand.
Where to go next
Give every person their week back
The outcome training compounds with. Hours measured before we build, so you know what came back.
Every lead gets answered
One system on a clock. Text back during hours, receptionist after five.
All five outcomes
What we build, and what each one is worth when it is fixed.