feat: Team plan needs a Max 20x equivalent tier for power users
Open 💬 18 comments Opened Apr 13, 2026 by marcoantoniofassa
Problem
The Team plan currently offers two seat types:
- Standard (1.25x Pro usage)
- Premium (6.25x Pro usage)
For power users (CTOs, tech leads, senior devs) who rely heavily on Claude Code CLI for agentic coding workflows, 6.25x is not enough. We currently use Max 20x individually, which means we can't move to Team without a significant downgrade in usage capacity.
Current workaround (bad)
- Keep individual Max 20x accounts for power users
- Create a separate Team org for the rest of the team
- Result: two completely separate accounts, no SSO unification, no shared projects between power users and the team
Proposed solution
Add a Premium 20x (or "Ultra") seat type to the Team plan, equivalent to the individual Max 20x usage tier. This would allow organizations to:
- Keep all members under one org with centralized billing and SSO
- Assign different usage tiers based on role (Standard for marketing/product, Premium for devs, Ultra/20x for tech leads)
- Avoid the split-brain problem of individual + team accounts
Why this matters
Organizations adopting Claude Code for their engineering teams have power users who push the limits daily. Forcing them to choose between team collaboration features (SSO, shared projects, admin controls) and adequate usage capacity is a blocker for enterprise adoption.
Context
- Team size: 5-15 people
- Power users: 2-3 (CTO + tech leads using Claude Code CLI all day)
- Regular users: 5-10 (devs, product, marketing)
- Current setup: individual Max 20x accounts, evaluating Team plan
18 Comments
+1 — two blockers preventing our migration from Max to Team
We're in exactly the same situation described here. Our team has power users on Max 20x who can't move to Team without a significant usage downgrade. Two blockers:
1. No 20x tier on Team
Team's Premium seat (6.25x) is less than a third of Max 20x. For engineers running agentic Claude Code workflows all day, this isn't a minor inconvenience — it's a hard blocker. We'd need to keep individual Max accounts for power users and a separate Team org for the rest, which defeats the purpose of a Team plan entirely.
2. Conversation history portability
Before switching, there's no clear answer on what happens to existing claude.ai conversation history when a Max account is moved into a Team org. If migrating requires creating a new account, months of context, project history and chat memory are lost with no migration path. This risk alone is enough to keep us on individual accounts indefinitely.
What we need:
Without both of these, Team is not a viable option for organizations where some members are power users of Claude Code.
+1 also, this needs to be addressed as soon as possible.
+1 please guys add this! Charge more than the max plan, we dont mind. Put a 23x usage and we will be happy to pay for it on the team plan. =)
Same problem here. I’m a founder and also the main dev on my team.
I use Claude Code pretty heavily throughout the day, morning sessions, afternoon, and late nights around 8pm.
Right now I’m on Max 5x individually and it works fine, but if I move to Team I lose the peak-hour throttling elimination and get stuck at 6.25x. That’s a downgrade for me.
The thing is I need both things at the same time: power user performance for myself and centralized billing, SSO and shared projects for the team.
The only workaround right now is keeping two separate accounts, which completely kills the management experience.
A 20x seat option in Team would fix this. Just needs to exist.
Agree, this is a major blocker to the team plan. Need this ASAP.
Yes, I am also wanting to have this and can leverage Claude better then.
Was looking for the same. I hope they will add it soon.
Agreed!
+1
Agreed
Agree. why don't do it that way?
Strong +1.
This is one of those features that changes how people use Claude Code every day, not just occasionally. It removes friction from common workflows, enables cleaner automation, and eliminates the need for brittle workarounds.
I believe this would have a disproportionately positive impact relative to the implementation effort. If there is room to prioritize community-requested features, I'd put this near the top.
I also agree that this would be a great feature to have for the select power users who need more usage. It's an administrative irritant to have part of the team on Claude Teams and part of the team running individual subscriptions specifically for 20x.
same problem here
+1
+1!!!
I'm a CTO for a 20 person org. We must be on a Team plan, but we have a few power users that need significantly more than the Premium limit offers.
I agree, I really need 20x on team plan
Following up on this request since there seems to be significant demand from teams using Claude Code heavily.
Could someone from Anthropic comment on whether this is:
The lack of a Team-equivalent to Max 20x is currently preventing us from consolidating individual and Team accounts, so even a high-level status update would be very helpful for planning purposes.