AI training on your team's real work
We set up Claude for your company and teach your people to use it on tasks they already do. They leave with something that already does part of their job, and plain rules on what is safe to put in.
Team training is part of AI Transformation, and you can book it on its own. Looking for the free public sessions? Those are our free Claude workshops for Tampa Bay small businesses.
Two ways in. The difference is depth.
Pick either one.
One to four people, hands-on
For the people who own a process end to end. We work through it at their own keyboard, on real files, and you get a written map of that workflow.Up to ten people, broader
For getting a group off zero at once. Everyone leaves with prompts and a workflow of their own that already runs.
What the session can cover.
We choose the mix with you before the session.
ChatGPT and AI essentials
A shared method for getting useful output from the tools the team already has.Claude, Cowork and Claude Code
Claude for everyday work, Cowork for multi-step tasks across files, Claude Code when the work needs a build.Building internal tools
Turn a process held together by spreadsheets and memory into a tool the team can run.Agents and automation
Build recurring work into a system that runs inside limits you set.AI security for teams
What information stays out, how connected tools can be misused, and where checking is required.AI policy
Practical rules on ownership and approved tools, without turning every decision into a committee.
How a session runs.
Length is set with you on the call.
Before
We collect the real work: the emails, documents, reports and requests your team repeats every week.During
People work on their own tasks with guidance, so what they build fits their work.After
The prompts, workflows and notes stay with your team. Nothing depends on us being in the room again.
Questions before a workshop.
What makes this different from generic AI training?
We run the session against your work, not a demo dataset. Before the workshop we collect the repeated tasks your team does, then build the session around those examples.
How long is a session and how many people can attend?
A working session is hands-on with the one to four people who own a process and returns a written map of that workflow. A team workshop covers up to ten people and is less hands-on with each person. Length is set with you on the call: one afternoon, two mornings, or weekly blocks.
Who should be in the room?
The people who own the work, plus whoever will make decisions about changing it. Mixed rooms of operators and their manager work better than either group alone, because the judgment calls about what to automate get made in the session instead of afterward.
Do people need technical experience?
No. The workshop is about judgment: when to trust output, when to edit, when to escalate, and how to describe work clearly enough that a model can help with it. Those skills matter more than tooling knowledge.
What happens after the workshop?
You keep the prompts, workflows and operating notes from the session. If it surfaces a process worth building, we quote the build separately.
Bring the team and one task each.
Tell us the people, the tools and the work that repeats.