Loading…
Loading…Loading…
Loading…Growth Operations · Programme
You and your team using AI tools properly inside your own work, by the end of the day.
Hands-on training for business owners and their teams on using AI tools in real work: setting up the tools, working with code and documents, building a first workflow, and knowing what not to put into them. A day on-site or remote for up to five people, with two weeks of follow-up, or a series of three sessions.
Discuss this engagementWho this is for
The tools are already on every laptop in the building. What is missing is the skill to use them on real work, and that gap shows up as a person opening a chat window, typing a vague question, and closing it again a minute later, unimpressed.
Usually one person in the business, often the founder, has actually spent real hours learning how these tools behave: what they are reliable for, what they get subtly wrong, what should never go anywhere near them. Everyone else is waiting to be shown, and the founder is the only one who has time to show them, which means the bottleneck is exactly the person who is already busiest.
By the end of the day, the team is not guessing anymore. Everyone who attended has set up the tools on their own machine, run a real piece of their own work through it, and left with a finished task rather than a demo they watched someone else do.
Skill spreads through a team the way habits do: by watching someone else do the task successfully once, on work that mattered to them.
What spreads afterward is not just familiarity with a tool but a shared sense of the rules: what is safe to paste into a chat window, when to trust an answer, and when to check it against something real. The team now works from the same floor instead of five different private habits nobody else can see.
Agree participants, tools and one real task each
Set up the tools together
Work each task through, with the method explained as we go
Write the team guide and the follow-up plan
Before the day starts, we agree who is coming, which tools are in scope, and one real task each person will bring, not a hypothetical exercise built for the room. Getting everyone set up happens first and together, account by account, so nobody spends the morning waiting on a password reset while the rest of the room moves ahead.
The day itself moves in one direction: work every real task through from start to finish, with the method narrated as we go rather than handed over as a slide at the end. A question that comes up for one person usually matters to the whole room, so it gets answered out loud, on the spot, against the task in front of everyone. Nobody leaves until their own task is actually done, and the team guide is drafted from what actually came up during the day.
Working setups on every participant's own machine, configured on the tools they will actually use going forward, and the real task each person brought, already finished. Nothing about the day was theoretical: what leaves the room is work the team can point to.
A short written guide for the team, covering what was set up and the rules agreed on the day, plus two weeks of follow-up support while the habit is still forming. Questions from the first week of real use get answered directly, so the skill has a real chance to stick before the old habits return.
The engagement
No, every participant works on a real task from their own job for the full session. The room works through actual documents, actual code and actual decisions, with the method explained as it happens. Everyone leaves with their own task finished, ready to use again the next morning.
We train on the tools you already have or plan to adopt. Where nobody on the team has picked one yet, we recommend one based on the work in front of us that day. Either way, the day ends with tools chosen, set up and already in use.
Yes, part of the day covers what can and cannot be shared with these tools, and how to recognise the difference in the moment. We work through your own examples, a client file, a contract, a piece of financial data, until the rule is second nature. Everyone leaves knowing where the line sits for their own work.
You get two weeks of follow-up support and a short written guide for your team, covering what was set up and how to use it. Questions that come up in the first fortnight of real use get answered directly, while the habit is still forming. The guide stays behind as the reference once the follow-up ends.
A conversation first, then a written scope.
Discuss this engagement