Skip to main content
Back to services

AI service · Team

Practical AI training
Learn with your team’s real tasks.

A training call and a reference document, both built on your own files: writing, searching, summarizing, answering, while staying clear on the limits and on your data.

From $349

One-time, for the training call and the reference document built on your own files. A second session is quoted separately.

Problems solved

Some of your staff already use AI, the rest have never opened it
The prompts people type in stay too vague
Nobody can tell whether an answer is any good

Possible deliverables

Training call
Reference document on your cases
Privacy rules
Agreed follow-up support

How it runs

Every mandate follows these steps, in this order, and none of it depends on one particular tool.

  1. 01

    Your files, not generic examples

    Before the call I collect a few real cases: a typical email, a report to summarize, a client answer to write. That is what we work on.

  2. 02

    The training call

    We go through your cases one at a time, screen shared. You see the question asked, what comes back, and what had to change before the result was usable.

  3. 03

    The limits, at the same time

    What the tool makes up, how to spot it, and which information must never be pasted into a chat window.

  4. 04

    The reference document

    What we covered, written down and handed over: the phrasings that worked on your cases, the traps we hit and the privacy rules we agreed on. That is what remains once the call is over.

  5. 05

    The support afterwards

    The follow-up is agreed up front rather than left vague: how long you can come back with questions, and through which channel. Without that, training fades in a fortnight.

What the mandate covers

The scope is settled before anything starts, and none of the below arrives as an extra once it is agreed.

Your cases collected before the call

A typical email, a report to summarize, a client answer to write. Your own files are the exercises, not demonstration examples.

Rules written down, not implied

What may be pasted into a tool and what may not, decided with you. A team left to guess those rules always ends up breaking one.

The agreed follow-up support

How long you can come back with questions, and through which channel. Settled when the mandate is scoped rather than left vague.

The call itself, screen shared, on your files

We go through your cases one at a time, live. You see the question asked, what comes back, and what had to change before the result was usable. Nobody watches a slide deck.

The document handed over afterwards

The phrasings that worked on your own files, the traps hit along the way, and the confidentiality rules agreed together. It is what remains once the call ends, and what lets someone who missed it catch up.

When this is the wrong mandate

This is not a certified course and it prepares for no exam. If your people are after a diploma, a college or a university serves them better. Here we work on your files, and what counts is what is still usable the next morning.

Privacy and simplicity

I write down which data the tool can see, which answers it is allowed to give, where it stops, and at what point a human takes over. It is the dull part of the mandate, and it is what separates a tool you end up using from one that only looks impressive.

What people ask me before we start

How does it actually run?
A call, screen shared, on your own cases. You then get a document covering what we went through, with the phrasings that worked and the privacy rules we set. The support that follows is agreed when the mandate is scoped.
How many people can attend?
A small group works better than a full room: everyone has to be able to ask their own questions about their own files. We set the number together before booking a date.
Is a paid subscription required?
Not necessarily. We start from what you already have, and a good part of what we cover holds up on the free versions.
What if nobody has ever touched this?
That is the most common case, and the easiest: there are no bad habits to undo. We start from zero on tasks everyone recognizes.
Is the document useful to someone who missed the call?
That is a good part of the point. It is written to be read on its own, with your examples in it, so someone who joins later or replaces a colleague can pick it up without redoing the call.
Do you see our data during the call?
Only what you choose to show. The cases are picked by you in advance, and one of the rules we write together covers exactly what must never leave your business, including in front of me.
Should the audit come before the training?
Often, yes. The SMB AI audit is for knowing which tasks are worth it; the training is for doing them. Training a team on uses that do not hold up costs you twice. If you already know what to learn, the training on its own is enough.
Does this still hold in six months, with tools changing constantly?
The tools change; the way you frame a request changes far less. What goes into the document is your cases and your rules, and those outlive a version number. Where a button moves, the document says what the step was for rather than which menu it sat in that month. I would rather be straight about the rest: some of what we cover together will be out of date one day, and that is true of any training on a piece of software.

Let’s see whether AI truly has a place in your case.

Schedule a call