Train your teams on AI — using your own files

Why generic training doesn’t survive Monday morning

You may have seen it before: a full-day workshop, slick slides, an impressive demo on an invented example. Everyone leaves enthusiastic. The next Monday, they open their inbox, their quotes, their spreadsheets — and nothing matches. The tool from the demo isn’t theirs. The examples look nothing like their work. The enthusiasm fades as fast as it came.

The problem isn’t your people. It’s the training: generic content has nothing to attach itself to in their day-to-day work.

What we do differently: your files, your tools

Before the session, we look at how your teams actually work. What documents they produce, which tools they use, where they lose time. The training is built on that.

On the day, there are no fictional examples. We open a real quote, a real report, a real customer reply — chosen together, with nothing sensitive inside. Everyone leaves with uses that work at their own desk, on their own files. Not a bag of tricks: working habits.

What your teams will be able to do

Spot the tasks where AI genuinely helps — and the ones where it wastes time.

Write a clear request, and rework it when the answer misses the point.

Check before using: an AI can state something false with complete confidence. Your teams learn to verify an answer before it goes anywhere near a customer.

Protect your data: know what must never be submitted to an AI tool — customer data, personal information, confidential material — and why.

Work within a simple written framework we set with you: who uses what, for what, within which limits.

Leaders and teams need different training

Deciding and doing are not the same job.

For you, as a leader: what AI could change in your business, what to demand from it, what to refuse. The questions to ask a vendor. The real risks — legal, data, dependency — without doom-mongering or promises.

For your teams: hands-on practice, on their own tasks. Less theory, more “try it, we’ll fix it together”.

Afterwards, everyone speaks the same language. That’s often what’s missing: a leader deciding without knowing what happens on the ground, and teams improvising without a framework.

When this training is not the right answer

Training doesn’t fix a broken process. If the same order is re-typed into two systems that don’t talk to each other, the problem isn’t your team’s skills — training won’t change a thing. The route needs straightening out first.

Training is not a substitute for a project either. If you need a tool, it has to be built — not worked around: see Custom AI solutions and Custom software development.

And if no one in your business has a single task where AI adds anything — it’s rare, but it happens — we’ll tell you in the first conversation. Training “to tick the box” would be money wasted. In those cases, a Cap Diagnostic — our first review of where you stand — is sometimes the right starting point. Sometimes the right answer is to do nothing for now.