How do we bring the team with us rather than around them?
Automation without training becomes shadow work: people rebuild the old way in a spreadsheet. We train the people who do the job, on the job, in the tools they will actually use, and we write the operating notes with them. Redeployment is planned, not assumed, and none of it is framed as headcount reduction.
Half day A$1,400; full day A$2,400; built into every pilot at no extra charge.
Trained staff who can run and improve what was built, written operating notes, and a short list of the next skills worth adding.
At your premises or online, in groups of up to eight, on your real work.
What it is
Most AI training is a tool demonstration to people who did not ask for the tool. Ours starts from the job: what this person does on a Tuesday, where the hours go, what would make it better. The tools follow the job, and the operating notes are written during the session, by the people who will use them, in their words.
Where a pilot has changed a role, we plan what the person does with the hours that came back, before the pilot goes live. That plan is part of the training, because a rollout the team works around has failed regardless of the demonstration.
This is for you if
- A pilot or a tool is arriving and the people who will run it have not been asked
- You want operating notes that survive the person who wrote them
- You want the hours that come back planned into something
Not for you if
- You want a general awareness session with no job behind it
- Attendance is compulsory and the manager will not be in the room
- The tool has not been chosen yet; that is a conversation first
How it runs
- 1 · before the day
Understand the job
Thirty minutes with the manager and one person who does the work. What happens on a normal day and where it hurts.
- 2 · half or full day
Train on the work
Their real files, their real systems. Each person leaves with one workflow running and notes they wrote.
- 3 · included
Operating notes
Assembled from the session, checked by the people who wrote them, stored where the team already looks.
- 4 · two weeks later
Follow through
A short check on what stuck, what did not, and the next skill worth adding.
In writing, before we start
Three sentences that hold on every engagement. They are the method, written as promises.
The measure, the budget cap and the point at which we stop are set in the written scope before anything is billed. Nothing moves the goalposts afterwards.
Everything we build runs in your accounts and is yours: code, configuration, documentation and measurements. We hand over; there is no dependency on us.
If the pilot does not hit the measure we agreed first, we keep working at no further cost until it does, or we stop and say so in writing. You will not be sold the next step by the first one.
What you receive
Questions
Who should attend?
The people who do the work and the manager who owns the process. Leadership sessions are separate and are the coaching programme.
Do you train on specific tools?
On the tools you have or the pilot introduced: Microsoft 365, Google Workspace, Xero, your CRM, and the AI assistants inside them. We do not sell tools.
Is this the same as the coaching programme?
No. Coaching is for the person who makes the calls and is one on one. Training is for the people who do the job and is done on the job.
Who will run what you are about to build?
Tell us the team and the tool, and we will say what a day with them should cover.