A Claude training day built on your real work
A full day inside your business, teaching your team to use Claude, Claude Code and Claude Cowork on the work they actually do. Not a generic deck, not theory. They map their real workflows, learn the tool against those jobs, and leave the day genuinely using it.
A full day, hands-on, inside your business.
Most teams have Claude and use a sliver of it. They open it, ask a question, copy the answer out, and treat it like a slightly better search box. A training day closes that gap. I come into your business for a full day, we work through the jobs your team does every week, and by the end they are using Claude on real tasks in front of them.
It is practical, not a lecture. People bring their own work to the day: the emails they write, the reports they pull together, the research they do, the admin that eats their afternoons. We put Claude to work on those exact things, so what they learn maps straight onto Monday morning.
Not a stock deck about a business that isn't yours.
The day is built around your workflows before I turn up. I map how your team actually works, where the time goes and where the repeatable lifting sits, then design the training against that. It means nobody spends the day on a hypothetical case study. They spend it on their own jobs.
That is also why it lands with people who think AI is not for them. When the first thing they do with Claude is a task they already know inside out, the tool stops being abstract and starts being useful.
Claude, Claude Code and Claude Cowork on real tasks.
Depending on the team, the day covers Claude for everyday drafting, research and document work, and Claude Code or Claude Cowork for the heavier jobs that string several steps together, drafting and revising long documents, working through research, handling files, connecting the tools you already use.
We do not try to cover everything. We cover the handful of workflows that will save your team the most time, get them confident, and give them a repeatable way to apply Claude to the next job themselves. Teaching people how to think about the tool matters more than a list of features.
Wherever your team is.
On-site is the default for a hands-on day, because sitting with people at their desks and working through their own tasks is where the change happens. I travel across the Northern Rivers, the Gold Coast and South-East Queensland for in-person days, and further for the right engagement.
Remote works well for distributed teams and is often the right call when your people are spread across locations. The substance of the day is the same either way.
Behaviour first, technology second.
My background is in behavioural science, a Bachelor of Social Science and a Behavioural Science and Marketing masters. That is the reason the training holds after I leave. Getting people to genuinely change how they work is a behaviour problem, not a software problem, so the day is designed around habit and real tasks rather than novelty.
To be clear and honest: I am an independent Claude and AI specialist. I am not an official Anthropic partner and I do not claim their endorsement. I have completed Anthropic's courses so the training is grounded in the current tools, and independent is the point, I work for you, not a vendor. When a business wants the tool itself built rather than taught, that goes through Under Seage Studio.
Is this a generic AI course?
No. The day is built on your workflows, not a stock deck. Before we run it, we map the jobs your team actually does, then teach Claude against those jobs. Nobody sits through a talk about a hypothetical business, they work on their own.
What tools do you cover?
Claude, Claude Code and Claude Cowork, depending on what your team needs. For most businesses that means using Claude for drafting, research and document work, and Claude Code or Cowork for the bigger jobs that string several steps together. We teach what fits your work, not everything at once.
Can you run it on-site or remotely?
Both. On-site works best for hands-on days because we can sit with people at their desks and work through their real tasks. Remote works fine for distributed teams and is often the right call when your people are spread across offices.
Who is a training day for?
Any team that already has Claude and uses a fraction of it, treating it like a chatbot. It suits small businesses, operations teams, marketing teams and professional services, basically anyone whose day is full of writing, research, admin and repeatable work.
Why does the training actually stick?
Because getting people to change how they work is a behaviour problem before it is a technology one. My background is in behavioural science, so the day is designed around habit and real tasks, not novelty. People leave with a few workflows they are already using, which is what makes it hold.
Get your team genuinely using Claude in a day.
The fastest way in is the phone or an email. I read everything.