We Pay for Claude Seats and Only a Quarter of the Team Uses Them. How Do We Fix Adoption?
A recovery plan for a stalled Claude rollout: read the usage analytics you already have, sort people into three groups, give each a fix, and right-size seats instead of paying for empty ones.
You fix low Claude adoption by treating it as three separate problems, not one: people who never really started, people who tried it and stalled, and the few who use it daily. Read the usage analytics your admin console already has, sort your team into those groups, give each group a different fix, and only then decide whether to cut or move seats. Another all-hands demo or a "remember to use Claude" email rarely moves the number.
This post is for the company that already rolled Claude out and is now staring at a quarter of the seats doing the work. If you're starting fresh, my 30-day plan for a non-technical team is the better place to begin.
Why a quarter is the usual number
On team calls I hear the same shape over and over. Leadership bought seats, IT turned them on, someone sent an announcement, and a few enthusiasts took off. Everyone else opened Claude once, typed a vague question, got a vague answer, and quietly went back to how they worked before.
That's not laziness and it's not a sign the tool is wrong for your company. A blank chat box asks people to invent a use case on the spot, while they're busy doing their actual job. The people who succeeded were the ones who already had a use case in mind. So the fix is to hand everyone else one.
Step 1: get the real numbers before you change anything
Owners and Primary Owners on the Team plan, and Owners, Primary Owners and Admins on Enterprise, can open Analytics from the menu under their initials in the lower-left corner. According to Anthropic's usage analytics guide, the tabs that matter for this job are:
- Summary: weekly active members, which is your headline number.
- Who's using Claude?: active members against assigned seats, broken down by groups and members.
- How are they using Claude?: adoption level, product stickiness, and which skills and connectors people actually use.
- Claude Chat and Cowork: the percentage of users with at least one chat or one Cowork session, plus top members by chats and by project usage.
Write down three numbers today: weekly active members, the percentage of users with one or more chats, and the percentage with one or more Cowork sessions. That's your baseline. If you're on Enterprise and want this in your own dashboard, the Primary Owner can turn on the Analytics API under Organization settings and create a key with the read:analytics scope.
Step 2: sort the team into three groups
Using the members view, put every person into one bucket:
- Daily users. Your top members by chats and projects. Usually a small group.
- Tried and stalled. They have some chats, but nothing recent, and little or no Cowork use.
- Never started. An assigned seat and almost no activity.
You don't need precision. A rough sort on a spreadsheet in twenty minutes is enough, because each group needs a completely different intervention.
Step 3: turn daily users into the source of everyone else's first task
Your daily users have already solved the hardest part: they found work Claude does well in your company. Ask each of them one question: "What's one thing you now do in Claude every week?" You'll get answers like a weekly status draft, a first pass at a customer reply, or a summary of a long thread.
Then make those answers reusable:
- Put the useful context into a shared project for that team, so the next person doesn't start from zero. Context from one chat doesn't carry into the next unless it's in the project's knowledge.
- Turn the prompts that work every time into skills. On Team and Enterprise plans, organization Owners can provision skills for all users, so they appear for everyone. This requires code execution to be enabled, so check that setting first.
Two or three skills built from real work beat a library of twenty that nobody asked for.
Step 4: give the stalled group one task, not a tour
The tried-and-stalled group already knows how to open Claude. What they lack is a reason to come back. Meet with them in small groups, by team, and have each person name one task they did last week that they'll do again this week. Then do that task together, live, in the shared project, with the skill your daily users just provided.
This is the step where the Cowork jump usually happens. Someone stops pasting a spreadsheet into chat and asks Claude to read the file, find what changed and draft the update. Once a person sees their own task done that way, they come back without being reminded.
Step 5: find out why the never-started group never started
This group is where I'd be careful not to assume. In my experience the reasons are usually one of these:
- They don't know what they're allowed to put in. Write your policy in one or two sentences ("customer names are fine, financial account numbers are not") and put it at the top of every shared project.
- The tools they live in aren't connected. If their work is in a system your policy hasn't connected yet, Claude feels like a separate island. Decide which connectors are allowed and say so.
- Their job genuinely has little use for it right now. That's a legitimate answer, and it leads to the next step.
Ask them directly, one line each. You'll learn more from ten honest replies than from another month of dashboards.
Step 6: right-size the seats instead of paying for empty ones
Once you know who needs what, adjust the seats. The details from Anthropic's Team plan seat guide are worth knowing before you touch anything:
- Team plans mix Standard and Premium seats. Premium adds higher usage limits. You can change a person's seat type from the Tier dropdown under Organization settings > Members, if your plan has an unassigned seat of that type.
- Removing a member frees their seat for someone else but does not lower your bill. To pay less you have to reduce the total seat allocation, which an Owner or Primary Owner does under Organization settings > Organization and access > Manage.
- A seat reduction takes effect at your next renewal, with no prorated refund when you submit it.
So the sensible order is: move heavy users who hit limits onto Premium, give stalled users a real chance with steps 3 and 4, and plan any reduction for the renewal date rather than reacting mid-term.
Step 7: check again in 30 days
Come back to the same three numbers a month later. If weekly active members went up, keep going: add one more shared skill per team and one scheduled task that produces a draft people review each week. If it didn't, look at which group didn't move. It's almost always that some people still don't have a task that's really theirs.
A short checklist
- Baseline today: weekly active members, percentage with a chat, percentage with a Cowork session.
- Sort everyone into daily, stalled and never-started.
- Collect one weekly task from each daily user, then turn the best into shared projects and skills.
- Small-group sessions for the stalled group, built on their own tasks.
- One honest question to the never-started group, plus a written policy line and a connector decision.
- Seat changes planned around renewal, not reactions.
- Re-check in 30 days.
If a new model is part of why you're revisiting the rollout, my notes on Fable 5.2 for teams cover which seats get it. And if meetings are where your team's work lives, read what admins should set before Claude joins calls.
Sources: View usage analytics for Team and Enterprise plans, Purchase and manage seats on Team plans, What are skills, Schedule recurring tasks in Claude Cowork.
If you'd rather have someone run the recovery sessions with your team, built around the work your people actually do, that's exactly what our private team training is for.
Related posts
Claude Can Join Your Team's Video Calls Now. What Should Admins Set Before It Does?
Claude Meetings is in beta on Team and Enterprise. What it does on a Google Meet call, which settings are on by default, and the five admin decisions to make before auto-join spreads.
How Do I Get a Non-Technical Team Actually Using Claude in the First 30 Days?
A week-by-week plan for getting a non-technical team using Claude chat and Cowork in 30 days: admin settings, one shared project, owner-provisioned skills, scheduled tasks and the analytics to check.
Claude for Enterprise: How Engineering Teams Are Using Claude in Production
The problem with ad-hoc Claude adoption at work - and what the teams who are getting it right actually do. Shared CLAUDE.md, team-wide commands, MCP servers, and why training is the gap nobody's filling.