Anyone looking up what Claude Code costs finds the list in a minute at claude.com/pricing. The problem for someone building a real team budget isn't finding the numbers: the plan's monthly fee is only one line of the actual bill. Weekly consumption, the time spent checking what the agent produced, and the cost of reconstructing months later why a change was made a certain way all sit outside any pricing table.
What do Claude Code plans cost today?
Claude Code doesn't have its own price: it's included in every paid Claude plan, and what a team pays depends on the plan it picks, not a separate line item for the tool. Updated as of September 25, 2026, primary source claude.com/pricing: the Free plan is free but doesn't include Claude Code. Pro costs $20 a month, or $17 a month billed annually, and includes Claude Code with a usage limit shared across the rest of the plan. Max goes up to $100 a month for 5x Pro's usage inside the five-hour window, or $200 a month for 20x, billed monthly only, with no annual discount. Team starts at $20-25 a month per standard seat and $100-125 per premium seat, with a two-seat minimum. Enterprise starts at $20 per seat a month, billed annually, plus consumption charged at API rates.
Why doesn't the real bill match the plan's price?
The monthly fee buys a usage ceiling, not unlimited use, and that ceiling has been moving. Claude Code shares the same limit as the rest of the Claude plan, with a cap that refills every five hours and a separate weekly cap. Starting in May 2026, Anthropic temporarily raised weekly limits by 50% across Pro, Max, Team, and seat-based Enterprise; that promotion ended on September 13, 2026, and as of September 14 the permanent limit settled back to 25% above the pre-promotion level, not 50%: a team that planned its usage over the summer is now working under a lower ceiling than it had in August, even if that ceiling is still higher than where it started (source: official announcement from Anthropic's ClaudeDevs account on X, September 13, 2026, consistent with independent coverage that same week). Upgrading from Max 5x to Max 20x doesn't linearly double the weekly room either, because the per-session multiplier and the weekly cap don't scale the same way: a budget that assumes a 1:1 ratio between plan price and real usage starts out wrong.
What's the cost that isn't on the price list?
METR's 2025 randomized controlled trial found that experienced developers using AI tools on real tasks were 19% slower, despite having predicted beforehand that they'd be 24% faster. Almost all of that gap is verification time: reading a diff cold, checking it against a criterion written before the session started, and deciding whether to accept it. That time shows up on no pricing plan, but it's real, recurring, and grows with the number of sessions a team runs each month. There's a second, less visible cost on top of it: when someone asks months later why a change was made a certain way, the answer today is almost always "ask whoever ran the session," not a record anyone can check.
Is it worth it anyway, against the cost of not using it?
The Stack Overflow Developer Survey 2025 found that 69% of developers using coding agents report higher individual productivity, against only 17% who report better team collaboration. The first number says the cost of not using Claude Code, for a software house competing on delivery time, is real: a team that skips it starts out slower. The second number says the subscription alone doesn't solve the team problem: buying Claude Code seats doesn't automatically buy the team's trust in what those seats produced. The honest comparison isn't "use it or don't," it's "what it costs to use it well, with a verification process around it," against the cost of using it badly, without one. Framed that way, the seat price stops being the deciding factor either way: a team that skips Claude Code to avoid the bill still pays the productivity gap, and a team that adopts it without building a review habit around it still pays the trust gap. Neither cost shows up on an invoice.
How to set the budget without guessing
| Team situation | Plan to start from | What to budget beyond the seat |
|---|---|---|
| One developer, occasional use | Pro | Review time, even at low volume |
| One or two developers, frequent long sessions | Max 5x or 20x | Watch the weekly cap, not just the five-hour one |
| Team delivering across multiple clients | Team, standard or premium seat | Central administration, review by project, not by person |
| Regulated sectors, clients that audit | Enterprise | A verifiable delivery record, not just access controls |
The right seat gets picked by looking at session volume and who has to answer for the result, not just the lowest number at the bottom of the pricing page. The missing piece, in every row of that table, is the same one: what a team can show when someone asks to account for a delivery, regardless of which agent wrote that code that particular week. Detent, the end-to-end delivery system (detent-ai.com), holds intent, authorized context, execution, and human signature together across every delivery, from request to release: that's the cost Claude Code's price list doesn't include, and an honest budget has to account for anyway.