Team Rollout

Last verified: 14 April 2026 | Applies to: Team, Enterprise

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.

Prerequisites

• A Team or Enterprise plan (see Choosing a Plan)
• Admin access to configure seats and permissions
• A pilot group of 3-5 early adopters identified

Step by step

graph LR
    W1["Week 1: Pilot setup"] --> W2["Week 2: Feedback and adjust"]
    W2 --> W3["Week 3: Expand to team"]
    W3 --> W4["Week 4: Measure and optimise"]
    W1 --- D1["Early adopters, specific tasks"]
    W2 --- D2["Check in, refine CLAUDE.md"]
    W3 --- D3["Onboard by function"]
    W4 --- D4["Track adoption, optimise seats"]

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 ($150/mo) for power users who need higher usage volume. Both include Claude Code and the same features. The difference is usage allowance.
• 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

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

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

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

Scenario: Priya, Head of Ops

Priya ran the Claude rollout at her 25-person ecommerce company, starting with a five-person pilot group. Two loved it immediately and began using it daily for reporting and email drafting. One was sceptical but converted after trying the sales call prep workflow for a client meeting. One did not engage at all — Priya paired them with a power user for a guided session, and they were productive within a day. The fifth person genuinely did not need Claude for their role (warehouse operations with minimal desk time). Four out of five adopting is a strong hit rate, and Priya used the pilot feedback to refine the CLAUDE.md instructions and plugin selection before rolling out to the full team in Week 3.

What to watch out for

• Don’t skip the pilot. Deploying to 50 people on day one guarantees support tickets and wasted seats. A 2-week pilot with 5 people catches problems cheaply.
• Give people a specific task. “Here’s Claude, have fun” leads to abandonment. “Use Claude for your weekly report this week” leads to adoption.
• Standard seats are fine for most. Don’t default everyone to Premium. Start Standard, upgrade as needed.
• Compliance matters. If you’re in a regulated industry, read Audit & Compliance first. Cowork sessions are not captured in enterprise audit logs.
• Budget for learning. Expect productivity to dip slightly in Week 1 as people learn. It recovers by Week 2-3 and exceeds baseline by Week 4.

Related

• Admin Setup: technical configuration for team deployment
• Cost Management: seat optimisation and usage strategies
• Your First 30 Minutes: the onboarding walkthrough for each team member
• Workplace Memory: the first thing each person should set up

---

Something wrong or outdated? Let us know →

Get weekly workflows. Subscribe to the newsletter.