A team trained to build with AI, not just chat to it
Hands-on sessions where your staff build a working tool for their own job before the session ends, because capability you grow in-house compounds.
The problem
How it works by hand
Most UK firms now use AI, and most of that usage stops at drafting text. That is the gap between adoption and advantage: a team that asks a chatbot to rewrite emails has not automated anything, and a one-off webinar about AI changes nothing except the calendar. The belief that AI is something your team can build with, not just chat to, does not come from slides.
A worked example
What a working version looks like
This is training built like the systems we ship: everyone leaves with something that runs. Before the session we find the real repetitive jobs inside your business, the report someone assembles, the data someone retypes, the email someone sends forty times. In the session, each person builds a working tool for their own job, hands on keyboards, with us cooking alongside rather than presenting at them. The tools are real: they run on your actual work, and they keep running after we leave. The session ends with each person knowing not just how their tool works but how to spot the next thing worth automating, which is the point. The follow-up is structured so the tools survive contact with the following Monday.
The exact tools change per business. The shape does not.
What it needs
Honest inputs, nothing exotic
- 01A few hours of your team’s time, hands on keyboards, no spectators
- 02The honest list of repetitive jobs people do each week
- 03Access to the tools those jobs live in: spreadsheets, inbox, CRM
- 04A leader willing to let people automate parts of their own role
The payoff
What you get back
What changes is what your team believes is possible, and what they automate next without asking you. Capability grown in-house compounds month after month. A webinar does not.
Do it yourself
How you would build this yourself
No course, no upsell. This is the order we would build it in, with the tools named, and a prompt to start from.
- 1
List the repetitive jobs first: the report someone assembles, the data someone retypes, the email someone sends forty times. Ask the team, they know exactly what wastes their week.
- 2
Get everyone a proper AI account (Claude or similar) and block out a half day, hands on keyboards, no spectators. A webinar changes nothing.
- 3
Each person builds a tool for their own job in the session, on their real work, not a demo dataset. Finished beats clever.
- 4
End with each person naming the next thing they would automate. The capability is in spotting the next one, not building the first one.
- 5
Diary a follow-up a few weeks later to see what survived contact with the real world, and fix what broke.
I run a [type of business] with a team of [number]. I am planning a hands-on AI session where each person builds a working tool for their own job. Here are the repetitive jobs the team does each week: [list]. For each one, tell me whether it is a good first build (small, real, finishable in one session) and sketch what the tool would do. Then help me plan the session: what each person needs set up beforehand, and a build plan per person they can follow at their own pace.
Copy it into Claude Code, fill the brackets, and it will plan the build with you before writing a line of code.
We would rather show you how than bill you. The whole ladder of free help, answers, guides and the weekly build-along, is on the do-it-yourself page.