Skip to main content

Rolling it out to your team

The session gets a few people started. The next month decides whether it sticks. Don't announce a transformation. Give the team a folder, a few connectors, and a reason to show their working.

How to access it​

A Team plan, on work emails. Minimum two seats. Standard seats for most people. Premium for the few who will live in it all day. Check the current price at claude.com/pricing.

Creating the Team on an email that already has Claude can pull that account in and cancel Pro or Max. Skills and connectors don't come with you. Tick the option to keep a personal account separate if someone still needs one.

The switch people miss: a shared About Company with one owner. If everyone edits it, you don't have a company file. You have six drafts.

Steps​

  1. Put the company on Team. Personal accounts are the wrong place for client work. See Security, privacy and compliance.
  2. One shared folder for company facts and shared skills. One named owner for About Company. Everyone else sends them corrections.
  3. Each person keeps a personal folder (about-me.md, about-business.md, tone, working style), set as the default, in their own OneDrive or Drive.
  4. Admin adds three connectors. Each person connects their own login. Connectors and permissions.
  5. For four to six weeks, the only jobs are email, calendar, and meeting follow-ups. No new internal products. No fifty skills.
  6. Every fortnight, half an hour: each person shows one real thing they did. Not a demo of the menus.
  7. Book a follow-up session for four to six weeks out, when the questions are specific.

The prompt for the owner​

GOAL
A first About Company file the whole team can use.

CONTEXT
I'll answer your questions. The business is [what]. The readers are colleagues, not customers.
Existing material I trust: [files].

CONSTRAINTS
Plain language. Flag anything you had to guess.
Ask me before you include a number.
This file will be shared. Don't include anything personal to me.

If anything is missing, ask me first.

Worked example. After a session, a consumer brand's ops lead owned About Company. Marketing wanted a different adjective in the first paragraph. They sent the change to the owner rather than keeping a private copy. The fortnightly show-and-tell was one shipping note and one follow-up email. That was enough for the people who hadn't been in the room to see the point. The skills library waited until week five.

What to share, and what not to​

Share skills that are the company's method. Sharing skills with your team.

Don't expect scheduled tasks to appear on everyone's laptop. They don't. Share the skill, or share the result of one person's task.

Don't share a personal tone file as the company voice. The company file is the company. Personal tone stays in the personal folder.

Pro tips​

  • Enthusiasm from one real example beats a mandate. A mandate gets you logged-in accounts and empty folders.
  • IT requests go out with names: connectors, Granola, Wispr Flow, Claude in Chrome. "Please approve AI" sits in a queue.
  • Email the team a week after the session with the one thing to finish. The folder, not a reading list.

Limits​

This doesn't fix a policy that forbids the tools. Sort approval before you book the show-and-tell.

A Team plan doesn't make judgement shared. People still send a bad draft if nobody told them to read it first. Put "don't send without reading" in the shared guardrails.

If the owner of About Company leaves, name a new one the same week. An unowned file goes stale, and then everyone pastes their own version into the chat.

Where to start in 30 minutes​

  1. Name the owner of About Company. Tell them.
  2. Confirm you're on Team, not a handful of personal Pro accounts.
  3. List the three connectors admin still needs to add.
  4. Put a 30-minute show-and-tell in the diary, a fortnight out.
  5. Write the email you'll send in a week: finish the personal folder, use it on one real email a day, bring one example.