Plan choice, SSO, a central skill library and honest success measurement \u2013 so a tool becomes a real way of working. This is how I roll out Claude Desktop in a team, without sprawl.<\/p>\n\n\n\n
My promise to you:<\/strong> after six weeks your team knows what Claude Desktop is good for \u2013 and what it is not. In writing, verifiable, without hype.<\/p>\n\n\n\n Starting point A \u2013 sprawl without ground rules.<\/strong> Individual staff use Pro accounts privately, company data ends up in the app uncontrolled. We consolidate onto one plan and write binding rules.<\/p>\n\n\n\n Starting point B \u2013 pilot in place, rollout missing.<\/strong> Three to five people are enthusiastic, but the team does not know how to proceed. We build the skill library, onboarding and adoption measurement.<\/p>\n\n\n\n Starting point C \u2013 greenfield with compliance requirements.<\/strong> The company wants to start but has concrete GDPR or audit requirements. We begin with the Enterprise plan, BYOK and written data flows.<\/p>\n\n\n\n In phases, not with a battering ram. Each week ends with a concrete result.<\/p>\n\n\n\n Too many MCP servers at once.<\/strong> If the pilot group gets eight servers at once, Claude often picks the wrong one. Three to five servers are enough to start.<\/p>\n\n\n\n Training without concrete tasks.<\/strong> Generic introductions fizzle out. A session where each person solves a real task sticks.<\/p>\n\n\n\n Measuring adoption by token consumption.<\/strong> Tokens are an input signal, not a result. Measure processing time per task, not activity in the app.<\/p>\n\n\n\n Power users without an owner role.<\/strong> If the first enthusiasts get no official role, the knowledge drains away. Appoint a person with clear responsibility.<\/p>\n\n\n\n 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.<\/p>\n\n\n\n For a team of 10 to 30 people I plan four to six weeks. Of that, two weeks are preparation \u2013 ground rules, skill library, pilot group \u2013 and two to four weeks of active onboarding with support.<\/p>\n\n\n\n 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.<\/p>\n\n\n\n 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.<\/p>\n\n\n\n Yes, on the Enterprise plan. Both identity providers are supported. Setup usually takes a morning and saves staff from maintaining their own passwords.<\/p>\n\n\n\n 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 \u2013 guide value: between 4,000 and 12,000 EUR net.<\/p>\n\n\n\nWhere teams start in practice<\/h2>\n\n\n\n
What a serious rollout looks like<\/h2>\n\n\n\n
\n
Four anti-patterns from real rollouts<\/h2>\n\n\n\n
How you will know it is working<\/h2>\n\n\n\n
\n
Frequently asked questions<\/h2>\n\n\n\n
Do we need the Team or the Enterprise plan?<\/h3>\n\n\n
How long does a rollout typically take?<\/h3>\n\n\n
Do we have to train all staff?<\/h3>\n\n\n
How do we measure success?<\/h3>\n\n\n
Can we use SSO with Microsoft Entra or Google Workspace?<\/h3>\n\n\n
What does the rollout cost per employee?<\/h3>\n\n\n