Workshops
An AI workshop for your team
using what you already pay for
Much of the AI in an ordinary office is sitting unused inside software the company already buys. The workshop starts there, with your own work on the screen.
Most teams have already been handed AI and told to get on with it. A workshop fixes that by putting their own work on the screen and showing, task by task, what it can and cannot do.
It is hands-on. Everyone brings a laptop and a real job they have to do that week: a quotation to write, a sheet to clean up, a long document to summarise, a reply to draft. We do those jobs in the room. By the end each person has something that works and knows why it worked, which is the part that survives the week after.
Your work, not slide examples
Everyone brings a real task from their own week. We do it in the room, on their own laptop, in the software they already have open.
It starts with what you pay for
Most offices are already paying for AI inside tools they have. I show what is sitting unused in those before anything new is suggested.
Built for people who are not technical
No code and no jargon. Every term is explained the first time it comes up, and nobody is put on the spot in front of the room.
A short form before the day
Everyone answers a few questions about what they actually do. I read the answers and build the session around the jobs that came up most.
You keep the material
The prompts, the examples and the notes written in the room go to you afterwards, along with my free book, 101 Rules for Teaching Your AI.
No tool is sold at the end
I am not reselling anybody's software. If the honest answer is that your team needs practice rather than a purchase, that is what I will say.
What happens in the room
We start with the tools you are already paying for, because that is usually where the unused AI is. Then I work through the jobs people brought with them. Writing a quotation from a few lines of notes. Turning a messy sheet into the columns a manager wants. Reading a long document and pulling out the dates that matter. Drafting a reply to a client, then arguing with the draft until it sounds like your company.
What makes it stick is repetition on real work. People do not learn this from a demonstration. They learn it by getting a bad answer, seeing why it was bad, and fixing the instruction. That happens again and again in a session, on work they would have had to do anyway.
- Everyone on their own laptop, with a real task from that week
- The AI already included in software you pay for
- Writing, summarising and cleaning up records
- How to tell when an answer is wrong
- Where to stop, and what to keep doing by hand
Who it is for
Two kinds of room work well. A team of staff who have been handed AI without being shown how to use it, and a room of owners and senior people deciding what to do about it. The content is different for each, and I will ask which one you want before quoting.
I have run a session for a room of business owners. That version spends less time on typing and more on judgement: which work is safe to hand over, what to ask a vendor, and what it takes to keep a system honest once it is running. A workshop is also a reasonable way to find out whether you need anything built at all, which is the same question an audit answers in more detail.
The free book, and whether you need me at all
There is a free book on this site, 101 Rules for Teaching Your AI. It is the written version of most of what I say in a room. If you read it, hand it round your team and they start using it, you do not need a workshop, and I would rather tell you that now than after you have paid for one.
Send it round first. The people who get something out of it are the ones worth putting in the room, and the questions they come back with are better than anything I could prepare on my own.
How a workshop is priced
A workshop is quoted as a session. The quote names how long it runs, how many people are in the room, whether it is in person in Mumbai or over video, and whether the follow-up material is included. There is no per-person fee, so a larger team does not multiply the number.
What moves it: the size of the group, whether I travel to you, how much of the session is built from your own records rather than general examples, and whether you want a second sitting for the people who could not attend. A repeat session for the same company is quoted lower, because the preparation is already done.
How it runs
- 01
The form
Everyone answers a short set of questions about the work they actually do. Nobody has to describe their job to me in person.
- 02
The build
I read the answers and build the session from the jobs that came up most, using your own documents where you let me.
- 03
The room
A session in person in Mumbai or over video, with everyone on their own laptop and a real task in front of them.
- 04
Afterwards
You get the prompts, the examples and the notes from the room, and a list of the jobs worth building properly.
Built, not described
Questions people ask
How much does a corporate AI training workshop cost?
It is quoted as a session, with no per-person fee. The quote names how long it runs, how many people are in the room, whether I travel to you and what material you keep. Travel, group size and how much is built from your own records are what move it.
Is the workshop hands-on or a presentation?
Hands-on. Everyone brings a laptop and a real task from that week, and we do those tasks in the room. There are slides, and they are short. Most of the session is people working and getting the answer wrong first.
Do we need to buy any software first?
No. I start with the AI already inside the tools you pay for, because that is usually the part sitting unused. If something new is genuinely needed I will say so, and I do not resell anybody's software.
Can you run it over a video call?
Yes. The session works over video, and screen sharing makes some of it easier to follow. I am in Mumbai and travel for a session in person where the team can be in one room together.
What if my team is not technical?
That is the usual room. Nothing requires code, every term is explained the first time it appears, and nobody is put on the spot in front of colleagues. Somebody who types slowly still finishes the task.
Will any of it stick afterwards?
That depends on repetition, which is why the session is built on work people have to do anyway. You also keep the prompts and notes from the room, and the free book covers the same ground in writing for anyone who missed it.
Can the workshop lead to something being built?
Often it does, and it does not have to. You leave with a list of jobs worth building properly, and you can bring that back to me, hand it to your own IT person, or sit on it. A workshop is a cheap way to find out whether a build is worth it.
Next step