AI Training
Part of What We Do
Is your team actually using AI, or quietly avoiding it?
What is AI training?
AI training is a hands-on session that gets a team confidently using AI tools on the work they do every day. It isn’t a lecture. The time goes on doing: writing, summarising, researching and drafting alongside the tools until people can get a good result without being walked through it. A session built around the tasks a team actually has will stick, where a session built around generic demos won’t, which is most of the difference between training that holds and training that everyone forgets by Thursday. The practical guardrails come with it, what’s safe to put into a tool and what isn’t. It’s a workshop rather than a formal course, and there’s no certificate at the end. The point is capability on Monday, not a line on a résumé.
The question nobody asks out loud.
Nobody says it out loud, so we will: half the room is wondering whether this is the first step toward replacing them. Pretending otherwise for three hours doesn’t work, because everyone can feel it. It gets answered at the start, briefly, and then the day moves on.
The honest answer is that the people who get good at these tools become harder to do without. They clear the routine parts of the job faster and spend the recovered hours on the parts that need judgement, which is the work you hired them for in the first place. A team that’s good with AI gets hours of its week back and spends them where a person is needed. That’s the whole argument, and it holds up better in practice than in a paragraph, which is why the rest of the session is just getting good at the work.
The five people in every room.
Every team we've trained has roughly the same five people in it. Worth naming them, because the session is built around the fact that they don't all want to be there.
The one who's already using it
Quietly, usually well, and often doing something with client data they shouldn't. We put them to work. They demo something in the first hour, which lands harder coming from a colleague than from us, and they leave with the safety rules nobody ever gave them.
The one who tried it once and wasn't impressed
They asked a vague question, got a vague answer back, and reasonably concluded the whole thing was oversold. Easiest person in the room to win over. The gap between how they used it and how it works is about three techniques wide, and it closes in ten minutes.
The one who thinks this is about their job
Addressed at the start, briefly, then dropped. The rest of the day does the convincing on its own, because it's hard to feel replaced by something while you're busy making it do the task you like least.
The one who's embarrassed to ask a basic question
Often the most senior person there, which is exactly why they won't ask in front of everyone. Groups stay under a dozen for this reason, and the back half of the session is spent moving between desks, so the basic question gets asked quietly and answered without an audience.
The one who was told to be here
On their phone for the first twenty minutes. That's fine. They look up when the talking stops and the work starts, usually on the report they hate building, because the fastest route past scepticism is handing someone back an hour of their week.
Why train your team instead of leaving them to it?
Most people are already using these tools at work, quietly and badly. Some opened a chat assistant once, got something mediocre, and wrote the category off. Others are getting genuinely good results and pasting client data in to get them, with nobody having told them where the line sits. Left alone, a team drifts into a wide gap between the one person who’s good at this and everyone who isn’t, with no shared sense of what’s alright to do.
An afternoon closes it. Everyone reaches the same baseline on the tasks that actually matter, picks up the same handful of techniques that separate a useful result from a waste of time, and learns the same rules about what goes into a tool and what doesn’t. Much of that is prompting. The ones worth keeping end up in a reusable prompt library rather than in somebody’s notes app.
The cost comparison isn’t close. A session runs $1,200 to $2,000, against the hours a team is currently losing to work the tools would do in seconds, and against the considerably more expensive version where someone learns the data lesson the hard way.
What a session actually looks like.
Half a day. A working one. Nobody watches slides for three hours. It opens with a short plain-language grounding (what these tools are good at, where they fall over, and what you can safely put into them), and that’s the only stretch that looks anything like teaching. Kept short on purpose.
Then the actual work starts. Everyone brings a task they do every week, the weekly report, the client email, the research nobody enjoys, and it gets worked through with the tools, person by person. People try things and get them wrong with someone in the room to fix it, which is where confidence comes from and why a recorded course doesn’t produce any. By the back half most of the room is moving faster than it arrived, on its own jobs.
The last part is saving what worked. Prompts, small workflows, whatever got built during the day, written against the tasks they were built for so they’re still there on Monday. Not lost in a notebook. A short follow-up a few weeks later catches whatever slipped, if that helps. Everyone leaves having done real work with the tools rather than having watched someone else do it.
What does success look like?
The test lands three weeks later, and it’s a simple one. Is the team still using the tools, or has everyone quietly drifted back to the spreadsheet? When it holds, and it holds when people learned on their own work rather than on a demo, it shows up in ordinary places. The Monday report takes twenty minutes instead of two hours. The routine replies stop eating the first hour of the day. Nobody has to be reminded to use anything. Not a good day out, a habit that stuck.
AI training FAQs
We sit with your team and work on their actual tasks, the emails they write, the reports they build, the research they do, and show them how to do those faster and better with AI tools. It’s hands-on the whole way through. People leave having done real work with the tools, not having watched a slideshow about them.
No. It’s a practical workshop, not a formal course, and there’s no certificate. We’re not a training organisation and we won’t pretend to be. The value is that your team can use these tools well on Monday, not a line on a CV. If you need a formal course with a certificate, we’re not the right fit and we’ll say so.
That’s the whole design. Training on the work people already do, rather than on abstract examples, is what makes the habit stick: everyone walks out with prompts and workflows saved against their real tasks. A short follow-up a few weeks later irons out whatever didn’t land the first time.
Usually yes, and it’s the most common thing clients tell us beforehand. Reluctance is nearly always about the framing. People expect a lecture about being replaced. We run it as a working session on their own tasks instead, and the mood in the room tends to turn once someone gets an hour of their week back in front of everyone. If a person genuinely doesn’t want to be there, we won’t make a scene of it. They’ll still pick up the basics by osmosis.
One of us, Aidan or Caleb, not a trainer we contracted. That matters more than it sounds: the questions people ask in these sessions are usually about their specific job, and the useful answer often involves knowing what could be built for them later. You get someone who can answer both.
Not at all. The session is built for people doing everyday work: admin, ops, marketing, sales and support. Developers aren’t the audience. If someone can use email and a spreadsheet, they can do this, and we pitch it to the room in front of us rather than to the most technical person in it.
A typical session is half a day, hands-on. Groups of up to about a dozen work best, so everyone gets time on their own work; larger teams we split across sessions. We keep it small enough that it’s a working session, not a lecture.
The ones your team will actually use: general assistants for writing and research, plus whatever’s relevant to their role. We focus on using tools well and safely rather than chasing the newest one, and we cover the basics of what not to put into them, so nobody creates a data problem trying to save time.
Sessions are priced by team size and format, and quoted up front. It’s a fixed price for the session, not a per-person licence. We’ll give you the number and what’s included before you book.
Happy to tell you whether a session would help
A couple of lines is enough. It goes straight to Aidan, not a sales team, and if it isn’t worth building he’ll tell you.
- You deal with Aidan directly, not a sales team.
- A straight answer on whether it's worth building, and what it'd cost.
- You own everything we build. No lock-in and no per-seat fees.
Thanks, we've got it.
It's gone to Aidan, not a shared inbox or a sales team. If it's urgent, call 0415 525 006.
Related reading
Is AI automation worth it
Does AI automation earn its keep for an Australian SMB? A plain ROI breakdown: the real costs, the real returns, and what decides whether it pays.
BlogAI strategy for small business
You don't need an AI department. You need a plan. A simple AI strategy for Australian small businesses: where to start, what to ignore, and how to see a return.
BlogWhat is an AI automation agency
An AI automation agency builds working systems that run your business processes for you. What one actually does, and when you need one at all.