Live Claude training for the whole team at once. A small-team sprint on Zoom with everyone on their own screen, or an in-person event for a chapter, member group or company offsite split into beginner and advanced tracks. Same seven modules; the shape changes with the room.
We run the same session for a founder, their ops lead and their admin at the same time — and each of them walks out with Claude working on the part of the job they actually own. Everything is built on the team’s own Claude plan, so the skills and projects stay with the company when someone new joins or someone leaves.
A small team adopting Claude together — CEO, ops lead, admin, PMs, coordinators — or a chapter, member group or company offsite of 15 to 30 people across beginner and advanced tracks.
Live over Zoom for a small team of up to eight. In person for a full day or a group event, with two or three trainers in the room on the larger ones.
Weekly for a team learning Claude together, or a one-time half or full day for a group event. Teams usually start with one or two sessions and decide whether to keep going.
The team's real work — the shared inbox, the policy doc everyone answers from, each person's own week — not slide-only theory.
Everyone logged into the team's Claude plan with connectors wired, each person has built something for their role, and the team has a shared library of skills.
Setup call before session one, Team plan admin walkthrough, a session deck, a recap email after every session, and email support between.
Modules 1–5 are a day one session: foundations, connectors, and making things with Claude. Modules 6 and 7 — skills, scheduled tasks and agents — are day two, once the team is on their feet. A 4-hour training day covers three or four modules in depth; a 2-hour session covers one or two. Every module runs the same way: we show it on our screen, then each person builds the same thing on theirs, on their real data.
Apps and sign-in, the Team plan, admin settings, and what the admin controls vs. what everyone else does.
Everyone installs the desktop and phone apps, accepts the Team invite, and picks their model. Admin sets skill sharing, spend caps and connector permissions on their own screen.
Why Claude vs. the others, the model lineup, usage limits, chat vs. code, cloud vs. local, and when to reach for Claude at all.
Attach a real document — a policy, a schedule, a contract — and get a summary. Point Claude at a messy folder, see the plan first, then let it organize. Each person lists three tasks from last week and sorts them: Claude does it, Claude drafts and I finish, or I own it.
Global instructions, how memory works, and projects — one per client, launch or workstream so every chat starts already knowing the context.
Each person writes their own instructions (who they are, who they write to, their hard lines) and builds one project they'll actually use — loaded with 2–5 docs and tested on three real questions.
Connecting Gmail, Calendar, Drive, Dropbox and the rest. How to ask well. Reviewing what comes back. The safety rules.
Each person connects their own inbox and calendar, reads the week, sends one real email they actually owe, and sets send/create to Needs approval. One message per person goes out in the training, written in their voice.
Artifacts (shareable pages, dashboards, trackers), research with sources, and Claude inside Excel, Word and PowerPoint.
One real question each, from research to a shareable artifact to an Excel file. Then everyone installs the Office add-in and makes a change on a sheet or doc they use every week.
Skills — a reusable prompt that acts like a teammate the whole team can share. Scheduled tasks — the daily inbox brief, the Monday morning review, the monthly report. How an admin shares a skill out to the org library.
Each person turns one thing they did by hand last week into a skill, then schedules a recurring task they'd actually read on Monday morning. The admin publishes one skill to the shared library so everyone else has it.
Projects with a role and a goal — when an agent is the right shape and when a skill is. How Claude picks a tool and iterates. Connected folders in Dropbox and Drive as tools. Browser use for the work the connectors don't cover.
Each person builds one role-based project with a stated goal (research a new market, screen a venue list, triage a shared inbox), runs it on a real question, and reviews the trace before anything is sent or saved.
A founder plus their ops and admin learning Claude together isn’t the same room as a chapter of thirty members at a half-day event. We run both — same curriculum, different delivery.
A founder plus their ops and admin, working through the modules together week by week. Everyone on their own screen, on their real data. The format the Jam On It team is on now — two 4-hour sessions, then decide whether to add more.
A chapter, a member group or a company offsite in one room, split into a beginner track and an advanced track running in parallel. Same seven modules; each track pitched to the people in it. Half a day or a full day.
Every topic lands on the team twice: once as a demo on our screen, then again as hands-on practice on theirs. People don’t learn Claude by watching someone use it. They learn it by using it, on their real data, with someone watching who can unstick them in real time.
We write “draft,” never “send,” until the team trusts the output. Every connector starts on Needs Approval. Reads are always allowed; sends, creates and deletes click first.
We explain one idea and show where it lives, on our screen first.
Each person tries it on their own laptop, on their own data. We watch, direct, and unstick.
Whoever built the best version shows it. Everyone copies the pattern.
Three things to try before next session, written down and said out loud.
Four shapes. Setup, a tailored deck, a recap email and email support between sessions are included on every one. Pricing on request — tell us the group and the length and we’ll scope it.
A focused two-hour working session on one area — getting the Team plan set up, connecting the right tools, or running through making things in Excel and Word. Good as a jump-start or a one-off.
The four-hour session we run with most teams, and the shape the Jam On It team is on. Day-one foundations or day-two automation, end to end, with everyone in their own account building on their real data.
All seven modules in one block — foundations through automation and agents. Done remote when the team is distributed, in person when you'd rather spend the day in one room.
A chapter, member group or company offsite in one room, split into a beginner track and an advanced track running in parallel. Two or three trainers, same seven modules, each track pitched to the people in it.
Nonprofit? Claude’s Team plan has a nonprofit rate — we’ll walk the admin through applying for it on the setup call.

Tell us roughly who's on the team and which tools matter most. We'll scope the right session and get a setup call on the calendar.
Book a group session