A workflow audit before any training
We interview your team about how the work really flows, then rank the candidates by hours saved against effort to automate. You get the ranked list whether or not you continue. It is useful on its own.
AI & Automation
Train your team to automate their own work.
Most AI training teaches people to chat with a model. We teach them to hand it real work, and leave your team with automations they built themselves and can maintain without us.
Your team has AI accounts. They're using them as a search engine.
Nearly every company has AI licences by now, and most are getting a fraction of the value. People use the tools to rewrite emails and summarise documents. That is genuinely useful, and nowhere near the point. The work that actually eats the week is still done by hand.
The gap is rarely enthusiasm. It's that nobody has sat down with your team, looked at how they specifically work, and shown them which of their own recurring tasks a model can take over. Generic training doesn't do that, because generic training doesn't know that your ops lead rebuilds the same report every Monday morning.
We train on your actual workflows. By the end, your people have built working automations for their own jobs, and know enough to keep building after we leave.
What the engagement covers
Hands-on sessions using your real work
No sample datasets. Each session takes a task someone on your team actually does and automates it live, so people learn on the thing they care about.
Claude Code for people who aren't developers
Claude Code can read files, run tools, and take multi-step actions rather than just answer. That is what makes non-engineers able to automate genuine work, and it is the core of what we teach.
Reusable skills your team writes
We show your team how to package a working automation as a reusable skill, so a good prompt becomes shared infrastructure rather than something living in one person's history.
A written playbook, not just a recording
Your team leaves with documented practices: what to automate, what never to automate, how to review AI output, and where the failure modes are.
Everything handed over.
Listed explicitly so there is no argument later about what was in scope.
- Ranked workflow audit: every candidate scored by hours saved vs. effort
- Live training sessions, recorded and captioned for people who join later
- At least three working automations built by your team during the sessions
- A starter library of reusable AI skills in your own workspace
- Written AI playbook covering review, escalation, and data-handling rules
- 30 days of follow-up questions by email after the last session
Honest scope
Is this right for you?
We would rather lose the enquiry than take on work we are the wrong people for.
A good fit if…
- You have 5-100 people and at least a few obviously repetitive workflows
- You would rather build internal capability than add a permanent vendor
- Someone internally is willing to own AI practice after we leave
- Your team is non-technical or mixed: this does not require engineers
Not for…
- Teams wanting a motivational keynote about AI. These are working sessions, and people leave with homework
- Organisations that cannot let a tool touch real (even anonymised) work samples; the training does not function on toy data
- Companies looking to reduce headcount. We are poor at that and will decline the engagement
- Anyone needing formal AI-governance certification. We will document practice, but we do not certify compliance
Ways to start
Pick an entry point.
Larger engagements vary enough that a headline number would mislead, so those are quoted after a free call. We always tell you what drives the number.
AI Workflow Audit
Finding out where AI would actually pay off before spending on it.
Free
Free. No cost, no obligation
About one week
- Interviews with up to five people on your team
- Ranked list of automation candidates with estimated hours saved
- A written recommendation, including 'do nothing here' where that is the honest answer
- A 45-minute walkthrough call
- Implementation
- Tool licences
Team Workshop
One team that needs to get productive with AI quickly.
Quoted
Priced on team size and number of sessions
2 weeks
- Workflow audit included
- Three half-day hands-on sessions for up to 10 people
- Three automations built live on your real work
- Written playbook and session recordings
- Company-wide rollout
- Ongoing maintenance
Enablement Programme
Rolling AI practice across several teams and making it stick.
Quoted
Priced on how many teams take part
6-10 weeks
- Audit across every participating team
- Role-specific tracks: ops, sales, finance, support
- Internal champions trained to run future sessions themselves
- Shared skill library set up in your workspace
- Adoption review 60 days after completion
Questions, answered.
Do we need engineers on our team for this training?
No. The enablement track is built for non-technical teams: operations leads, founders, finance, marketing, and support. We handle any technical setup, and sessions are run in plain language. If you do have engineers, they usually join to learn the skill-building side and then support their colleagues afterwards.
What is Claude Code, and why train on it rather than just ChatGPT?
Claude Code is an AI tool that takes actions (it can read your files, run tools, and complete multi-step tasks) rather than only replying in a chat window. That distinction is the whole point: chat assistants help a person work faster, while an action-taking tool can own a recurring task end to end. We also cover general assistants where they are the better fit; the goal is the automated workflow, not loyalty to one product.
How much time will this take from my team?
The Team Workshop is three half-days over two weeks, plus roughly an hour of homework between sessions. We deliberately spread it out. People need to try the automation against a real week of work before the next session, or none of it sticks.
What if AI turns out not to be worth it for our workflows?
Then the audit says so, and you have saved yourself a much larger spend. It happens: some processes are too variable, too rare, or too regulated to automate profitably. We would rather tell you that in week one than sell you a programme that quietly underdelivers.
Start with a free conversation.
Thirty minutes, no pitch. We will tell you what we would do, what it would take, and whether you need us at all.