Skip to content
Claude for Operators

Team Rollout

Last verified: 13 February 2026 | Applies to: Team, Enterprise

In 30 seconds

Section titled “In 30 seconds”

Rolling out Claude to a team is different from setting it up for yourself. You need to consider seat types, permissions, training, adoption, and compliance. This workflow covers a practical 4-week rollout from pilot group to full deployment — including the most common pitfalls.

Step by step

Section titled “Step by step”

Week 1: Pilot setup

Section titled “Week 1: Pilot setup”

Select your pilot group (3-5 people):

  • Choose a mix: one power user, one sceptic, one person who matches your most common use case
  • Avoid all-enthusiasts — you need realistic feedback

Configure their accounts:

  • Assign seat types: Standard ($25/mo) for most, Premium ($125/mo) for anyone who’ll use Claude Code
  • Install Claude Desktop on their machines
  • Enable relevant skills and connectors

Set up shared context:

  • Create organisation-wide CLAUDE.md instructions with company terminology, brand guidelines, and standard processes
  • Install the Productivity plugin for each pilot user
  • Run the Workplace Memory setup with each person

Give them a specific task, not an open invitation:

  • “Use Claude for your weekly reporting this week”
  • “Review this month’s contracts using the Legal plugin”
  • “Prep for your next 3 sales calls using the Sales plugin”

Week 2: Gather feedback and adjust

Section titled “Week 2: Gather feedback and adjust”

Check in with each pilot user:

  • What’s working? What’s frustrating?
  • Are they hitting usage limits?
  • Which features are they actually using vs. ignoring?
  • What training do they need?

Common Week 2 findings:

  • Someone needs a Premium seat upgrade (hitting limits)
  • Someone isn’t using it because they don’t know where to start
  • The shared CLAUDE.md needs updates based on real usage
  • One plugin is perfect; another isn’t relevant

Adjust before expanding:

  • Update seat assignments based on actual usage
  • Refine the CLAUDE.md with lessons learned
  • Create a short “getting started” guide based on pilot feedback

Week 3: Expand to the full team

Section titled “Week 3: Expand to the full team”

Onboard in groups, not all at once:

  • Group by function (all sales first, then marketing, then finance)
  • Each group gets a 30-minute walkthrough based on Your First 30 Minutes
  • Assign a pilot user as the “Claude champion” for each group

Provision plugins by function:

  • Sales team → Sales + Productivity plugins
  • Finance → Finance + Productivity plugins
  • Marketing → Marketing + Productivity plugins
  • Everyone → Productivity plugin (baseline)

Set usage guidelines:

  • Default model: Sonnet (use Opus only for complex tasks)
  • Use Chat for everyday tasks, Cowork for file/plugin work
  • Share a model selection guide (see Cost Management)

Week 4: Measure and optimise

Section titled “Week 4: Measure and optimise”

Track adoption:

  • How many team members are using Claude daily? Weekly?
  • Which features are getting the most use?
  • Where are the gaps — who isn’t using it, and why?

Optimise seats:

  • Move light users to Standard if they’re on Premium
  • Upgrade heavy users who are hitting limits
  • Remove unused seats (if anyone isn’t using it, find out why before cutting)

Create team-specific skills:

  • Based on what’s working, create custom skills for your team’s specific processes
  • Provision these org-wide via admin controls

How operators actually use it

Section titled “How operators actually use it”
Section titled “Related”

Something wrong or outdated? Let us know →

Get weekly workflows — subscribe to the newsletter.