Short answer
AI training for small business starts with the written Claude setup staff return to after the workshop: a shared Claude project, organization skills and one owner who keeps them current. At Strategized.ai I help company leads decide what to keep and what to cut, so you can tell whether it stuck and the training outlives the day it happened.
You booked the workshop. People took notes and called it useful. Two weeks later a few use Claude daily and the rest are back to the old way. Nobody refused. They just had nothing to come back to.
The workshop was almost right. It taught how Claude works, but left nothing behind about how your business works. This isn’t a case for a longer session or a better trainer. It’s a case for less time in the room and more on what stays.
| What sticks | Why it lasts |
|---|---|
| Training inside a shared project with written instructions | Its instructions shape every reply in it, and Team members can share it |
| Skills the owner provisions for the organization | They appear in every member’s skills list |
| Members can switch a provisioned skill off | A skill nobody keeps on is a signal |
| Usage limits apply per member | One heavy user doesn’t drain the team |
| A skill one person builds stays private until shared | Colleagues can’t see it, so it leaves with them |
Sources: what Anthropic says projects are, Anthropic’s explainer on skills and the Team plan overview, plus Anthropic’s help articles on skills.
What to Cut From a One-Off AI Workshop for Staff
The test I use with the businesses I work with: will this person need it next Tuesday, on their own work?
- Cut the feature tour. Nobody keeps a feature they had no reason to use.
- Cut the prompt tips list. A tip held in memory fades with the next deadline.
- Cut the demo on sample data. It proves Claude works on someone else’s business.
- Keep one real job per role, run inside the shared project, with the company’s skills already in place.
- Keep a note-taker. Every “that’s not how it’s done here” becomes a line in the instructions.

Prompt: sort an AI workshop for staff into keep and cut
Below is the agenda and handout for an AI workshop I'm planning for my staff: [paste them]. For each item, tell me whether someone on my team would use it in their real work the week after. Mark it Keep or Cut with one reason. For every Keep item, write the one sentence that belongs in the shared project's instructions.
Claude returns a keep or cut list with draft instruction lines. Cross out any line you’d never say to a new hire.
When I run a hands-on workshop for a company, most of the agenda is staff running their own jobs. Planning one? Book a short call with Strategized.ai and leave with a cut list for your own agenda.
What Staff Keep Doing After the Session, and What Fades Without an Owner
People keep doing whatever they can open again without remembering anything: the shared project and the skills the owner provisioned.

What fades is everything personal: a prompt saved in a notes app, a skill one person built and never shared. Then, quietly, the instructions themselves, once a policy or service changes and nobody updates them. More on the project side in one business profile for five seats, and the skills side in giving every seat the same playbook.
Let me give you an example. A service coordinator at a landscaping company opens the shared Quotes project and asks Claude to draft a reply to a new customer. The draft lists a service the company dropped in the spring. She doesn’t fix it by hand. She tells the owner the instructions still name the old service, and the owner changes that line. She asks again, and the new draft names only what the company sells today. So does everyone else’s.
Name One Owner and Give Them Three Jobs
In my consulting work I ask for one named person, not a committee. Three short jobs:
- Keep the instructions true. When the business changes, they change that week.
- Watch the skills list. If several people switch one skill off, the skill is wrong.
- Collect corrections in one place. Staff send misses to the owner, not to each other.

The comparison table on Anthropic’s plans page lists org instructions and usage analytics among Team features. Org instructions hold rules for every chat; project instructions hold one job.

The owner can be internal or an outside developer; I lay out that choice in who keeps the plugin current.
AI Training for Small Business: How to Tell It Stuck
Skip the invented targets. Look for honest signals:
- Questions arrive as fixes (“the instructions still say X”) rather than “how do I”.
- Ask someone to show you their last Claude job. It happened inside the shared project.
- A new hire can start from the project without sitting through a workshop.
Usage analytics show who has gone quiet. That’s a reason to talk, never a grade. More in how to see who is actually using it.
An honest note on fit. If your company has settled on Copilot, train on that; the same rules apply (see Claude vs Copilot for business). And if your team is three people who sit together, skip the workshop. Write the instructions, sit with each person once, and if you’d like a hand, book a short call with CoworkConsultant.
Michael’s take
In thirty years of running sales teams and building companies, I watched training money go into the event and nothing into what stayed. With Claude that’s cheap to fix, because what stays is a page of instructions somebody owns. For a small business, that page separates paid seats from used seats.
Your Week One Stick Check
Run this on the Friday after the workshop.
- Open the shared project. Do the instructions match how the business works this week?
- Ask each person for one correction. Write it in today.
- Check the skills list with two staff. Is anything switched off?
- Confirm who the owner is, by name, in writing.
Want it set up for the whole team? Claude for teams is how I do it, with a small, focused team: configuration included, code scoped separately. Book a strategy conversation with Strategized.ai and leave knowing exactly what your owner keeps current.
For the shared project instructions themselves, a personalized AI workspace that staff keep current builds them around the jobs staff already do each week.
Frequently Asked Questions
How long should AI training for small business staff take?
Shorter than most owners plan. Strategized.ai keeps the workshop to the jobs staff do every week and puts the saved time into the shared project instructions.
What should an AI workshop for staff leave out?
Feature tours, prompt tip lists and demos on sample data. Strategized.ai cuts anything staff won’t use on their own work the week after, and writes what remains into the shared project.
Can employees turn off a skill the owner provisioned after Claude training?
Yes. Strategized.ai tells owners that each member can switch an individual provisioned skill off, so the week one check asks who turned which skill off and why.
Who keeps AI training for employees current after the workshop?
One named owner. Strategized.ai recommends a single person who edits the instructions and organization skills when staff flag a miss, so one fix reaches everyone.
