Choosing the plan, SSO, a central skill library and an honest measure of success, that is what turns a tool into a real way of working. Here is how I roll out Claude Desktop in a team without letting it sprawl.
My promise to you: after six weeks your team knows what Claude Desktop is good for, and what it is not. In writing, verifiable, without the hype.
Where teams actually start
Starting point A, sprawl without ground rules. Individual staff use personal Pro accounts, and company data ends up in the app uncontrolled. We consolidate onto one plan and write binding rules.
Starting point B, the pilot works, the rollout is missing. Three to five people are enthusiastic, but the team does not know what comes next. We build the skill library, the onboarding and the adoption measurement.
Starting point C, greenfield with compliance requirements. The company wants to get started but has concrete GDPR or audit obligations. We begin with the Enterprise plan, BYOK and written data flows.
What a serious rollout looks like
In phases, not by force. Every week ends with a concrete result.
- Week 01, discovery and choosing the plan. Map the use cases, interview three to five power users, decide between Team and Enterprise. Result: a written plan with a budget and success criteria.
- Week 02, setup and ground rules. Buy the plan, set up SSO, configure workspace rules, sign off the usage policy. Result: the technical frame is in place and responsibilities are named.
- Week 03, skill library with the pilot group. With three to five people, build three use cases as skills and test them in daily work. Result: a first version of the skills, with feedback already folded in.
- Week 04, training for everyone. A two-hour introduction per team. Demo, a short exercise, a quiz on the ground rules. Result: everyone knows when Claude Desktop applies and when it does not.
- Week 05, supported use. Office hours or a channel for questions. We watch usage and collect friction points. Result: skills get sharpened, obstacles get documented.
- Week 06, adoption review and handover. An assessment of usage, time saved and quality. Result: a written final report and a clear plan for the next 90 days.
Four anti-patterns from real rollouts
Too many MCP servers at once. If the pilot group gets eight servers at the same time, Claude often picks the wrong one. Three to five servers are plenty to start with.
Training without concrete tasks. Generic introductions evaporate. A session in which every person solves a real task sticks.
Measuring adoption by token usage. Tokens are an input signal, not a result. Measure the time it takes to complete a task, not activity in the app.
Power users without an owner role. If the early enthusiasts get no official role, the knowledge drains away. Name one person with clear responsibility.
How you know it is working
- 80 percent weekly active use. Four in five staff open Claude Desktop at least once a week for a real task.
- Three skills carrying the load. The top three skills together cover more than half of all use cases.
- 25 percent less handling time. Defined routine tasks are finished a quarter faster on average, with no loss of quality.
This post is part of the series Setting up Claude Desktop.
Frequently asked questions
Do we need the Team or the Enterprise plan?
The Team plan is enough as soon as you need central management, shared billing and a DPA. The Enterprise plan adds SSO, longer retention settings and EU options via Bedrock. Rule of thumb: from 25 people, or with strict compliance requirements, Enterprise is worth it.
How long does a rollout typically take?
For a team of 10 to 30 people I plan four to six weeks. Of that, two weeks are preparation – ground rules, skill library, pilot group – and two to four weeks of active onboarding with support.
Do we have to train all staff?
No. A two-hour introduction for everyone and a deeper session for the power users is enough in most cases. More important than front-of-room training is a curated skill library with concrete tasks.
How often should we refresh training?
Ideally about every 12 months. Claude and the AI landscape evolve very fast – new features, new skills and adjusted ground rules make one-off training go stale quickly. A short annual refresh keeps the team current.
How do we measure success?
Not by tokens or requests, but by time saved per use case. Before the rollout we define three to five concrete tasks and measure how processing time and quality change.
Can we use SSO with Microsoft Entra or Google Workspace?
Yes, on the Enterprise plan. Both identity providers are supported. Setup usually takes a morning and saves staff from maintaining their own passwords.
What does the rollout cost per employee?
On the plan side, Team and Enterprise run between 25 and 60 EUR per person per month. The rollout consulting is project-based and depends on team size and complexity – guide value: between 4,000 and 12,000 EUR net.