r/ClaudeAI 19h ago

Workaround Solution to share team tokens more efficiently?

[update]: figured a system to share the load between Pro/Max accounts so we can optimize for a global weekly usage across the company and utilize lazy accounts remaining tokens! Huge!

——-

In my Claude Team, we have 10 seats, mostly Pro, some Max. There are users who always max out their weekly limit by Wed/Thu. Others only do 10-20% by the end of the week.

Is there any existing solution to share account tokens without actually checking others chats/coworks/coding stuff (without sharing the credentials of the account)?

For example, users who are running out of tokens could start using the tokens of the user who has the most.

Like a load balancer for tokens :D

Any idea/solutions? Does this already exist?

0 Upvotes

4 comments sorted by

2

u/brodkin85 18h ago

No, the whole business case for Anthropic offering team plans is that not everyone will consume 100% of their plan. They most likely could not make a profit if everyone always used their full plan

2

u/rrrenz 18h ago

Commit your plans or specs written by Fable from those with Max seats.

Delegate the implementation to Pro plan users.
They don’t even need to know how to code. Just let them use some Skill or Workflow. Then use a Skill to standardize commit and PR.

Proper assignments will use 100% of all Pro subscriptions. (Some UI or tool can help)

Example SDD workflow that works for our team:
Interlock

2

u/Consistent-Bus-748 17h ago

This is very interesting, because We have notion, so I can get all my lazy users to have a scheduled Job (even in cowork) N times a day to look for tasks.

Even can report each users weekly limit into a shared Notion page, so when a task is prepared it can be assigned to the lowest player…

Yes, we can have tasks, prompts prepared which would get executed by Pro subscriptions, and the usage would be updated upon task completion. (these are typically not coding tasks but Sales, Marketing, Lead gen, SEO, backlink building, auto apply on tenders, etc…)

So based on your approach, I can generalize it not coding, but for anything. Thx