Half-day workshop · 5–25 people
AI Training for Employees
Your team is already using AI. This makes it safe, and then makes it useful. Half a day, hands-on, nothing to buy.
Ask about a session for your team →Nobody approved it. Everybody is doing it.
Somewhere in your company this week, someone pasted a customer list into a free chatbot to tidy up the formatting. Someone else dropped in a contract to get a summary before a meeting. Neither of them was being careless. They were trying to get their work done, using the fastest tool available.
The instinct is to ban it. Banning it does not work — it just moves the same behaviour onto personal phones and personal accounts, where you can no longer see it at all.
The version that works is narrower and duller: agree what is safe, change a handful of settings, and teach people to use the right tool properly. That is a morning's work, and this is that morning.
What the four hours cover
AI literacy: where your team already is
An honest look at what is already happening — which tools, for which tasks, with which data. Most leaders are surprised, and it is not because anyone did anything wrong.
Data handling and your AI usage policy
What should never reach a chat window, and the far more useful discovery that most of it was never needed. Plus the settings pass, and your one-page AI policy written during the session rather than promised afterwards.
Applied skills: prompting and tool fit
Which tool for which job, so people stop using one chatbot for everything — then hands-on practice on your team’s actual work, not toy examples. Everyone leaves with prompts they keep.
Advanced workflows: what to automate next
The difference between chatting and delegating, and the specific repetitive work in your business worth handing to an agent that drafts and waits for approval.
Why this one
Most AI training is delivered by people who sell AI tools, or by platforms selling seats in a course library. I come at it from security — which is why the session starts with what your team is already exposing rather than with a feature tour.
I do not resell software and I have no vendor to push. If the right answer is a setting you already own, that is what you will hear.
Questions
What is AI training for employees?
Structured, hands-on instruction that teaches a team to use AI tools safely and productively in the jobs they already do. In practice it has three parts: an AI usage policy that says what may and may not go into a chat window, tool fit so people stop defaulting to one chatbot for every task, and practice on the team’s own real work. Training without the policy leaves the risk in place; a policy without the training gets ignored.
How long is it and what does a session cover?
Half a day, four hours, for teams of roughly five to twenty-five. Four blocks: where your team is already using AI and what that exposes, the settings and policy pass that closes it, hands-on work on your own tasks, and what to automate next. Anything larger than twenty-five stops being hands-on and becomes a lecture, which is not what this is.
What should our team never paste into an AI tool?
Customer names tied to identifying details, payment information, government ID numbers, health information, unreleased financials, credentials, and anything covered by a client confidentiality agreement. The more useful realisation is that most of it was never needed in the first place: a draft proposal needs the scope, the budget and the deadline, not the client’s name and account number. Teaching people to strip a prompt down to what the model actually needs is more durable than a settings change, because the habit survives switching tools.
Do we need to buy any software?
No. We work with the tools your team already has, and we do not resell anything. Most teams find the fix is a settings change on a subscription they already pay for, not a purchase. If a paid tier genuinely is the right answer for your situation we will say so, and you will buy it directly, in your own name.
Our team already uses ChatGPT. Is this still useful?
That is the usual starting point, and it is exactly the problem. Almost everyone uses one chatbot for every task, on default settings, with no agreement about what is safe to paste into it. The session is less about introducing AI than about replacing the habits that formed while nobody was looking.
Is it technical?
No. There is no code and no IT background assumed. If your team can use email and a browser they can follow the whole session. Bring laptops and the accounts you already use.
Do you cover AI policy and governance?
Yes, and you leave with the policy written rather than promised. For most small companies the useful version is one page, not the twenty-page document a consultancy would sell you. We build it during the session and cover how to actually roll it out, which is the part most legal templates skip.
Who is this not for?
If you have a security team, a compliance function, and an existing AI governance programme, you do not need this — you need something deeper and more specific to your regulatory position. This is built for companies that have neither, which is most of them.
Want one for your team?
Tell me roughly how many people and what they do, and I will tell you whether this is the right thing — or whether it isn't.
Ask about a session →