Claude AI Training and Courses for Teams
Hands-on Claude training for teams whose work is reading, writing and reasoning across long documents. Three half-day levels, from AI fluency to Cowork automation, built around the work your team actually does.
Our team has trained:
Who this is for
Organisations that have chosen Claude, or are choosing it, for document-heavy work: policy, legal, research, strategy, reporting and client advice. Claude tends to earn trust fastest where tone, structure and accuracy across a long document matter, and that is where we focus the practice.
Typical buyers are heads of People and Culture, L and D leads, IT and digital leaders, and operations managers. The usual trigger is a Team or Enterprise rollout where a few people have made Claude part of their day and most have not. That is a training gap rather than a tooling gap: the seats are bought, and what is missing is the habit.
We also work with teams evaluating Claude who want their people capable before the licence spend scales.
What your team will use Claude for
Claude is more than a chat box, and most of its value sits in the features people never find on their own. These are the ones we build the practice around, and what we do with each in the room.
Projects that hold the context
A Project keeps the reference documents, instructions and conversations for one piece of work together, so nobody pastes the same background in every time. On Team and Enterprise plans a Project can be shared, so a whole team works from the same brief.
In the room: We build a Project around a live piece of your work, with instructions your team writes and tests.
Long documents and careful writing
Claude reads long documents closely and holds tone and structure across a long draft. It suits policy reviews, tender responses, board papers and reports where the second half has to agree with the first.
In the room: We work through one of your real documents, then check Claude's summary line by line against the source.
Artifacts for finished work
When an answer should be a thing rather than a message, Claude produces an Artifact: a document, a table, a diagram or a small interactive tool that can be refined and shared.
In the room: We turn a recurring output, such as a status report or a checklist, into an Artifact the team reuses.
Claude inside Microsoft Office
Add-ins for Excel, Word and PowerPoint, with Outlook in beta, let people work with Claude inside the file instead of copying between windows. They are available on paid plans and installed through the Microsoft Marketplace.
In the room: Covered only where your organisation has approved the add-ins, which we confirm in discovery.
Connectors to your own tools
Once an admin enables them, connectors let Claude search and work with Microsoft 365, Google Workspace, Slack and other tools, so answers draw on your own files, email and calendars.
In the room: We show what Claude can see with your connectors on, and what that changes about what people should ask it.
Cowork, skills and scheduled tasks
Cowork lets Claude carry out multi-step work across files and connected tools. Skills package a repeatable task so anyone can run it the same way, and scheduled tasks run it on a timetable.
In the room: Level 3 only, once the team can judge which work is worth handing over.
What your team will be able to do
- ✓
Brief Claude properly: set up a Project with the right documents and instructions so the context holds from one conversation to the next
- ✓
Check Claude's reading of a long document against the source, and catch the summary that reads well and is wrong
- ✓
Apply your organisation's rules on what can go into Claude, including which plan and which connectors work data belongs in
- ✓
Tell which recurring work belongs in a skill or a Cowork task, and which should not go near a model at all
The training levels
Each level is a standalone half-day. Most teams run them in sequence, with time in between to put the last one to work. The content is set in discovery around the work your cohort actually does.
Level 1: AI Fluency with Claude
A shared foundation for a mixed room: how AI works, why it gets things wrong, what is safe to put into it, and the judgment to review what comes out. The thinking is tool-agnostic and holds whatever tool your people open next. The practice is in Claude, on your real work.
Modules
Level 2: Practical AI with Claude
Out of the chat box and into the way work gets done in Claude. Projects that hold your context, long-document work where the review matters as much as the draft, Artifacts that turn answers into finished work, and whichever connectors and Office add-ins your organisation has switched on.
Modules
Level 3: Automations and Agents with Claude
Level 2 makes one person faster at one task. Level 3 hands whole tasks to Claude through Cowork: multi-step work across files and connected tools, skills that package a task so anyone can run it, and scheduled tasks that run it without anyone starting it. Most ideas that arrive as "let's build an agent" turn out to be a skill or a Project, and sorting that out early is where the value is.
Modules
We would not recommend starting at Level 3, the level most organisations currently pick and the reason their AI programs stall. Building on a gap automates the gap.
What to settle before you roll Claude out
Four decisions that are specific to Claude. We work through them with you in discovery, because the answers change what we teach.
Put work on Team or Enterprise, not Pro.
Pro and Max are individual plans under Anthropic's consumer terms. On Team and Enterprise, Anthropic states that it does not use your inputs and outputs to train its models by default, and your organisation controls the workspace. We settle which plan work belongs on before anyone brings real work into the room.
Know where the data is stored.
At the time of writing, Claude's own apps do not offer Australian data residency. If residency is a hard requirement, confirm it with Anthropic before you commit. Organisations building their own tools can run some Claude models in Australia through cloud platforms such as AWS.
Decide which connectors and add-ins are on.
On Team and Enterprise, an owner or admin switches on connectors and Cowork. Whatever is enabled defines what Claude can see, so we match the session to your configuration rather than to the full feature list.
Name an owner for shared skills.
Skills published to the workspace are available to every Cowork user in it. Someone needs to review them, keep them current and retire them. We help you name that owner before Level 3.
Product details checked September 2026. Features and plans change, so we confirm them again in discovery.
Why fluency comes first
You cannot build on judgment your people do not have.
Skip fluency and you scale mistakes, not capability. A team that does not know why AI gets things wrong will not check it, and a team that does not understand what Claude can see through its connectors will put data where it should not go. The licences are already paid for; fluency is what makes them earn their keep.
Sessions are delivered by senior practitioners, not junior trainers reading from a deck. Our team comprises of people that have been learning designers at Canva and instructors at AWS.
Format and pricing
One cohort, one level
From $5,000 + GST
One cohort, any two levels
From $9,500 + GST
One cohort, the full pathway
From $13,500 + GST
No headcount limit.
For groups above 30, we recommend a teaching assistant in the room.
Delivery: Based in Australia. Onsite globally, or live online.
Prices are AUD, excluding GST. Travel billed at cost.
If it does not land, we run it again
If the session does not deliver what we scoped with you in discovery, we re-run it for the same group at no charge. We would rather fix it than keep a fee we did not earn.
What you own afterwards
Everything we build is yours to keep and reuse.
The session materials, branded for your organisation
A prompt library built from your team's real tasks
The Projects and skills your team set up in the room
A quick-reference pack
The session recording
Thirty days of follow-up in a private Slack or Teams channel, with a live session three weeks in
How we build your session
01
Discover.
A short discovery call with your leads to map real workflows and gauge the range of starting levels across the team.
02
Design.
A custom session built around those tasks and your tools, branded for your organisation.
03
Deliver.
Live onsite or virtual, hands-on, with tasks pulled from your own work rather than ours.
04
Embed.
A prompt library, quick-reference pack, and thirty days of follow-up including a live session three weeks out, so the fluency lasts.
Discovery is a build step, not a sales call. It is why the prompt library you keep is made of your workflows rather than our examples.
Build your AI training session
Not sure what to cover in the room? Answer five questions about your team and time, and we'll map out a running order of Claude demos that fits.
Proof
How other teams have done it
Let's Start a Conversation
No hard sales pitch.
Want to chat now?
Start a conversation below.
Frequently asked questions
What is Claude training?
Claude training teaches teams to use Anthropic's Claude for their day-to-day work. Our program runs as three half-day levels: AI fluency, practical use across Projects, long documents, Artifacts and the Office add-ins, and automation with Cowork, skills and scheduled tasks. Each session is built around your team's real workflows rather than generic examples.
How long does Claude training take?
Each level is a half-day, around four hours. Teams can take one level or run all three as a pathway, usually with a few weeks between sessions to put each one to work.
How much does Claude training cost in Australia?
Pricing starts at $5,000 + GST for one cohort at one level, $9,500 for two levels, and $13,500 for the full three-level pathway. We price the cohort, not the person. No headcount limit. For groups above 30, we recommend a teaching assistant in the room.
Do we need Claude licences before the training?
Yes, for the hands-on work. For work data we recommend Team or Enterprise, because Pro and Max are individual plans under Anthropic's consumer terms. We confirm what your organisation has enabled during discovery and shape the session around it.
Which level should we start at?
Most organisations should start at Level 1, including many who think they should not. Daily use is not the same as competent use. If your people can already explain why AI hallucinates, what Claude can and cannot see, and where the guardrails sit, we start at Level 2.
Do you deliver Claude training onsite in Australia?
Yes. We are based in Australia and deliver onsite globally, or live online for distributed teams. The curriculum and the hands-on approach are the same either way.
How is this different from Anthropic's own free course?
Anthropic's course teaches an individual, at their own pace, using generic examples. This is a live session for a whole team, built around your workflows, your data policies and your approved tools, so the room leaves at a shared baseline rather than a certificate.
Can Claude work inside Microsoft 365 or Google Workspace?
Yes, in two ways. Claude has add-ins for Excel, Word and PowerPoint, with Outlook in beta, on paid plans. Separately, connectors let Claude search Microsoft 365 and Google Workspace files, email and calendars once an admin enables them. We cover whichever your organisation has approved.
Does Claude keep our data in Australia?
Not at the time of writing. Claude's own apps do not offer Australian data residency. Organisations that need it for tools they build themselves can run some Claude models through an Australian cloud region, such as on AWS. If residency is a hard requirement, confirm it with Anthropic before you commit.
Does the training cover Claude Code?
No. The three levels are for people who write, analyse, plan and decide, and there is no coding in any of them. Claude Code is Anthropic's tool for software developers and calls for a different kind of session. If developers are your audience, raise it in discovery and we will tell you plainly whether we are the right fit.
We already use Copilot or Gemini. Does Claude replace them?
Usually not. Most organisations end up running more than one AI tool, and the useful question is which tool suits which work. Claude usually earns its place on document-heavy and writing-heavy work. We cover that in discovery rather than assuming you are switching.
Can you train our whole organisation?
Yes. Where teams have genuinely different workflows, each becomes its own cohort, because that is what lets us build around their actual work. One broad session for everyone is cheaper. Several tailored ones are what actually transfer.
Ready to get your team using Claude properly?
30-minute discovery call. We work out where your people actually are, which is rarely where the org chart says they are, and which level to start at. You will get a straight answer, including if that answer is that you do not need us yet.