Frequently asked questions

Yes, provided you use a paid business plan and set a short internal policy first. We train on Claude business plans, which do not use your prompts to train the underlying model. The real risks come from staff pasting client data into free consumer accounts, or from not agreeing what is and isn't in scope. We cover both in the workshop and help you write a one-page usage policy so the whole team is on the same page.

During the four sessions, meeting recordings and transcripts are held on Fathom and Otter, which are US-based platforms. Any working notes and plans live in our internal systems, which sit behind MFA and are accessed only by Toby Carroll and our operations manager. Australian tax law requires us to retain business records for seven years, so engagement files are kept for that period and then destroyed. If you would prefer we do not record sessions, tell us before session one and we will run without recording.

Yes. We will sign your NDA before session one on request. If you do not have one, we can send ours. Either way it is signed before any commercial or client information is shared.

We ask for the minimum needed to do the work in the room, and we prefer a limited test account over your live logins. Where a real system is required, we work alongside your admin during the session rather than holding standing credentials. Any access granted is revoked as soon as the session ends. If a task can be demonstrated on a sandbox or a copy of a document, that is what we use.

Yes, you need one, and yes, we help you draft it as part of the engagement. A short internal policy sets what tools are approved, what data can and cannot go into them, and who to ask when in doubt. It usually takes an hour in the workshop to draft, and your legal or ops team can then sign off. Without it, individual staff make their own calls, which is where most incidents come from.

The workshop is the third of four sessions and is delivered in person at your office. Before it, we have run a discovery call and built a written plan tailored to your team's actual work. On the day, we work through real tasks from your business using Claude, so your team leaves having done the work themselves, not watched a demo. It runs as a working session, not a lecture.

No. We train your team to build and own them, so you are not dependent on us or on any vendor. Our view is that a system nobody in the building understands is a liability, not an asset. You leave able to change and extend what you have without needing us back. That is the whole point of the training model.

Each person leaves with working prompts and small workflows they built during the session, tied to tasks they actually do. The team walks out with a shared reference document covering the tools chosen, the usage policy, and the agreed next steps. Nobody leaves with a stack of theory and no idea what to do on Monday. If a person could not attend, the reference document is enough for them to catch up.

About two to four weeks later we run a follow-up session online. That session is used to look at what has actually been used, what has stalled, and to unblock the specific things that came up once your team started applying it. It is not a second training day, it is a working review. Most of the value from the whole engagement compounds after this session, because that is when the habits stick.

Four sessions of 90 to 120 minutes, usually spread across four to six weeks. The gaps between sessions are deliberate, so your team has time to use what they built.

We take the concerns seriously rather than trying to sell past them. Most resistance is either a well-founded worry about the tool being sloppy, or a worry about the person's own role. Both get addressed directly in the room, with real work rather than slides. By the end of the day, resistant people tend to be the ones asking the sharpest questions about where to use it and where not to.

That is the normal case, not the exception. The workshop is built around real tasks from your business, so people work at the level of the task, not at the level of a generic tutorial. Senior people tend to focus on judgement and review, junior people on the mechanics. Nobody sits bored and nobody sits lost.

Group size follows the pricing tiers, from a solo operator up to a full department of fifteen, and enterprise engagements above that. In practice the useful ceiling for one workshop day is about fifteen people in one room. Beyond that, we split into two sessions so everyone gets hands on the tools and gets their questions answered. Larger organisations usually run several cohorts over a few weeks.

Training people to use AI well is not what makes a job redundant, ignoring AI is. Roles do change, and the honest conversation is about which parts of a role become faster and what the freed-up time is used for. That conversation is much better had by your leadership with a team that understands the tools than by leadership guessing. We do not make redundancy recommendations, that is your call.

For most Australian businesses doing knowledge work, Claude on a paid business plan is our default recommendation, and it is what we train on. ChatGPT is a strong alternative and Copilot is well suited to organisations already deep in Microsoft 365. The right answer depends on where your work already lives and what your data policy allows. We give you a straight recommendation during discovery based on your actual setup, not on affiliate deals.

Claude on a paid business plan does not use your prompts to train the underlying model, which matters for anyone handling client information. It also tends to be better at long, careful reasoning tasks and at following instructions precisely, which is what business work actually needs. We have used it across a lot of client work and know where it is strong and where it is weak. Training on one tool deeply beats training on three tools shallowly.

Tell us in discovery and we will factor it in. If you have Copilot or ChatGPT Enterprise already paid for, we will usually recommend you keep using it and layer Claude in only where it clearly wins, or train on what you already own. We are not going to tell you to throw away paid licences for the sake of the training. The goal is your team getting good outcomes, not us being tidy.

Training starts from $3,800 + GST. The final price depends on the size of your team, and we confirm it with you on the discovery call. Travel outside the Gold Coast is charged at cost and is agreed upfront.

The four-session programme works one on one. You get the same structure with the workshop shaped around your own workflows rather than a group. Solo operators usually get more per dollar out of the engagement than teams do, because everything applies directly to their own work. It is a common starting point.

Yes, we deliver in person across the Gold Coast, Brisbane, Sydney and Melbourne. Travel within the Gold Coast is included. Travel outside is charged at cost, quoted upfront and agreed before we book anything. There are no per diem or agency mark-ups on travel.

Discovery calls are usually available within the same week. From discovery, we need about a week to build your plan, then we book the in-person workshop day into the next available slot that suits your team. Start to workshop day is typically two to three weeks, faster if diaries allow. The follow-up session is booked in when the workshop is confirmed.

Nothing formal. It helps if the decision-maker joins discovery so we can be direct about goals, constraints and any concerns. A rough list of the tasks that eat the most time in your business is useful but not required. We take it from there and come back with the written plan before the workshop.

Ask whether they build systems for you or train your team to own them, and be clear which you actually want. Ask which specific tool they train on and why, and whether that tool's paid plan uses your data to train its model. Ask what your team walks out with on the day that they can use on Monday. Ask what happens after the training day, because the follow-up is where most of the value lands.

The honest signal is what your team is actually doing two to four weeks after the workshop, which is what the follow-up session is for. If people are using the tools on their own work without prompting, and the AI policy is being followed, the engagement worked. If tools have gone quiet, we use the follow-up to find out why and unblock it. We do not promise specific percentage gains, because they depend far more on your team's follow-through than on the training day.