Claude training · from someone who runs his business on it
Claude training taught from a working system, not a slide deck.
Here's my unfair advantage as your trainer: the Digital Crew system this whole site describes runs on Claude. My chief of staff, my research agents, my content workflows, the connected tools that keep my calendar and pipeline honest - I built all of it, I run all of it, and I'll teach your team to build their own. When your people finish this training, they won't have notes about Claude. They'll have working agents doing their Admin Drag.
Book a strategy call Different platform? The same training runs on Copilot, ChatGPT, and Gemini.Why Claude
The right tool for building a crew.
If your organization lives in Microsoft 365, Copilot training is probably your door - it meets your people inside the tools they already use. Claude is the door for teams ready to go a step further: building agentic workflows. Projects that hold your team's context, skills that encode how your business actually works, and connectors that let agents reach into the systems where the work lives. That's the architecture a Digital Crew is built on - and it's the architecture I use every day, so the training comes with the scar tissue included, not just the demo.
The proof I live in
I don't demo this. I depend on it.
Every framework I teach got tested on my own work first. The agent that preps my podcast interviews. The chief of staff that challenges my positioning decisions before they ship. The research crew that maps a market overnight. When I show your team how to structure a Project, write a skill, or govern an agent's access, I'm showing you decisions I made for my own business - including the ones I got wrong the first time. That's the difference between training and a tour.
I also deliver contracted Claude training for client organizations - multi-week virtual cohorts and onsite team sessions. Those engagements stay unnamed, but the approach is the one on this page: real workflows, working agents, nothing theoretical.
Telemetry · 60 days out
Sixty days later: did it stick?
Most training testimonials get collected in the applause. I collect mine sixty days out, with one question - no fishing: are you still using what you built? Here's what came back from the Kellogg Business Summit, quoted by name with permission.
I've been trying to standardize the individual carrier reports… for at least a year but was a long way from finding something that was satisfactory. Claude has created an output that gives me more than what I thought I could ever do on my own… a process that masks PHI, collects all carrier reports, standardizes the reports, restores the PHI on my computer, and then distills them all into a dashboard.
Prior to the summit in May, I was very reluctant to start using AI and didn't think I had the time to learn it. Since then, I have used it every day, several times a day. I've realized that my staff and I don't have time not to learn it.
Same room, same session, two working systems sixty days later. That's what training looks like when you redesign the work first.
The approach
Redesign the work, then train the tool.
Same sequence, proven across platforms. The training runs on your team's real work - not sample prompts, not someone else's use cases.
Assess
First we find where the Admin Drag lives - a short pre-training survey and workflow review, so the hands-on time is spent on the tasks actually burying your people.
Train
The hands-on build. Your people create their first working agents on their own tasks - a Scout that researches, a Scribe that handles the follow-up and the documentation, a Coach that briefs.
Embed
When you're ready, those first agents become the foundation of a full Digital Crew - governed, scaled, and owned by your team rather than by me.
Who this is for
Any team whose best people are buried in busywork.
And who want agents, not just answers. Producers and advisors drowning in quoting portals and renewal paperwork. Revenue teams re-keying the same call into three systems. Marketers on the reporting treadmill. Founders who are their own admin department. If your people have already tried AI and it didn't stick - that scar is exactly where we start.
Governance
Sanctioned beats shadow.
Agents that can reach into your systems demand more governance, not less - which is why it's built into the training, not bolted on after. What each agent can touch, what stays human, and how to bring the Shadow AI your team is already using into the light. For regulated rooms, this section is usually what gets leadership to yes.
Payload · Free download
The Shadow AI Governance Launchpad
The amnesty email, the 3-minute team survey, the traffic-light data rules, and a complete AI use policy template. Built to launch in 48 hours.
FAQ
Pre-flight questions.
How long is the training?
Half-day and full-day formats, virtual or in-person, sized to your team.
Do attendees need Claude accounts?
Yes - we build in your real environment. I'll help you scope the right plan for your team before we start; Anthropic's current plan details are at anthropic.com.
We’re on a different platform.
Then start with the training for your stack - Copilot, ChatGPT, or Gemini. Same approach, your platform.
What happens after?
The agents your team builds in training become the seed of a full Digital Crew engagement, when you're ready.
Is this affiliated with Anthropic?
No - The AI Hat is an independent training practice. That independence is the point: you get the practitioner's version, not the vendor's.
Status: GO
Bring the training to your team.
Book a strategy call - thirty minutes to find where the Admin Drag lives on your team, and an honest read on whether and how I can help. Even if the answer is the Copilot room, or not yet.
Book a strategy callThe AI Hat is an independent training practice and is not affiliated with or endorsed by Anthropic. Claude is a product of Anthropic; plan and feature details live at anthropic.com.