Claude Team costs $20 per seat per month on annual billing ($25 monthly), with a two-seat minimum, and every seat includes Claude Code. A room in muti is a different shape: one developer's Claude Code, running on their own machine under their own subscription, that the people they trust can send work to, with the developer approving anything risky and a record of who asked for what. For a small team where one or two people actually build and everyone else needs results, the second shape is usually the cheaper Claude Team alternative, and it is often the more honest one.
This is not a guide to sharing a login. It is a guide to counting who needs a seat.
A marketing lead asks the developer's Claude Code agent for a chart from a CSV; the request runs on the developer's laptop, finishes in 38 seconds, and shows its cost next to its id.
What Claude Team actually buys you
Claude Team in 2026 is a good product for teams where most people work in Claude every day. A standard seat gives 1.25 times the Pro usage, a Premium seat ($100 to $125) gives 6.25 times plus Cowork and the largest models inside plan limits, and the workspace adds centralized billing, admin controls and the contractual no-training guarantee. The minimum dropped to two seats this year, so even a two-person shop can buy it.
The catch is arithmetic. A five-person startup with one engineer pays for five standard seats, $100 to $125 a month, so that four people who ask for a chart or a data pull twice a week each have their own Claude. Their seats sit idle most of the month, and the engineer, the one person who would use a Premium seat all day, is on the same standard tier as everyone else.
Who on your team needs a seat
Sort people by what they do with the model, not by title.
- Producers open Claude Code many times a day: engineers, the data person, sometimes a designer who ships components. They need their own seat, and often the biggest one.
- Askers want an output: a chart, a cleaned CSV, a summary of last week's interviews, a landing page copied to a new locale. They do not want a terminal, a repository or a permission prompt. They want to describe the job and get the file back.
- Approvers are the producers wearing a second hat: the person whose machine and repositories the work touches, who should see what runs and be able to say no.
Claude Team prices all three the same. A room prices them differently: producers keep their seats, askers get a way to ask, approvers get the buttons.
How the room replaces the extra seats
The developer connects their machine to muti with one command and creates an agent from the Claude Code already installed there. They invite the team into a room, or give the agent a Slack bot with its own name so people can DM it or mention it in a channel. From then on:
- An asker describes the job in plain language, attaching the CSV or the screenshot if there is one.
- The request runs on the developer's machine, inside the directory the agent is pinned to, under the developer's own Claude subscription.
- Everyone in the room watches the same timeline: which files were read, which commands ran, what came out. The result and any files come back into the room, or into the Slack thread.
- Anything risky pauses for the developer. Pushes, deletes, credential access and spending always ask; routine things can be allowed once or, after the first time, allowed always for that agent.
- Every request has an id, a requester, an approver and a cost.
The asker never installs anything and never holds a Claude login. The developer never hands over their laptop or their password. What moved is the work, not the account.
The rooms index shows who is asking whom: three group rooms with four to six members each, one direct room, request counts per room, and one request in flight.
The cost, side by side
A five-person team: one engineer, a marketer, an ops lead, a founder and a designer who occasionally builds.
The saving is not dramatic in dollars for five people; it is dramatic in what you stop paying for. The four idle seats go away, and the engineer can move to the seat they actually need. At fifteen people with three producers, the gap is $200 to $300 a month, every month.
What this is not
Be precise about the line, because the line is where teams get banned.
A room is not account sharing. Nobody but the developer holds the subscription, signs in, or runs the client. The developer's Claude Code runs on the developer's machine and does the developer's work, some of which other people asked for. That is the same relationship as a colleague asking you to run a query for them, made visible and governed. Anthropic's consumer terms prohibit sharing credentials, reselling access and plugging subscription tokens into third-party tools; muti does none of those. It drives the official Claude Code binary on your machine and never touches your credentials.
It is also not for everyone. If four of your five people are producers, buy Team; the no-training guarantee and admin controls are worth it and the seats will be used. If you are a regulated company that needs contractual data terms for every user, buy Team or Enterprise. If askers turn into heavy users, give them seats. A room is the right tool for the very common team where the model is one person's daily instrument and everyone else's occasional errand.
Frequently asked questions
Does the developer's usage limit get eaten by the team? Yes, that is the point of routing through one plan, and it is why cost per request is shown next to every request. When the team's asks start to crowd out the developer's own work, that is the signal to buy a second seat, not a fifth.
Can askers see the developer's other work? No. Rooms are the boundary. A person in the marketing room sees the marketing room. The agent's other rooms, and everything else on the machine, are invisible to them. See zero sharing by default.
What if the developer is asleep? Requests queue in the agent's inbox and run when the machine is back; approvals wait up to 24 hours. Routine work the developer has allowed always runs without them. See the agent inbox.
Does this work with Codex or Cursor instead of Claude Code? Yes. The room does not care which runtime sits behind the agent. See Codex for non-technical teammates.
Count the producers. Buy them seats. Give everyone else a room.
Published