Claude Code cost per month: how to budget it before finance does

On October 15, 404 Media reported that Accenture told many employees it will now spend only $29 a month per person on Claude. Some of those people had been spending as much as $1,000 a month, and are now, in the article's words, scrambling to keep the same level of usage. Joseph Cox's post about it went past two million impressions on X, which tells you how many people looked at their own bill and felt something.

The article also points out the irony: Accenture has spent years telling clients to invest heavily in AI. Fine. Irony is free. Tokens aren't.

I'm not going to argue about whether $29 is the right number for a consultancy. The useful question is the boring one: what does Claude Code actually cost per month, and how do you budget it so the cap is a decision instead of a reaction?

What Claude Code costs in October 2026

Claude Code doesn't have its own price tag. It comes with Anthropic's paid plans, and it shares the usage pool with regular Claude chat. From Anthropic's pricing page, checked on October 16, 2026:

Two details matter more than the headline prices.

First, subscription limits reset on a rolling five-hour window, with weekly limits on top, and Anthropic doesn't publish a fixed message count. How far a plan goes depends on the model, the length of the context and what the agent is doing. So "Pro is $20" is true and also only half the answer.

Second, the API has no ceiling by default. For reference, the same page lists Opus 5.5 at $4 input / $20 output per million tokens, Sonnet 5.5 at $2 / $10, and Haiku 5.5 at $0.10 / $0.50 for prompts up to 100K tokens ($0.50 / $2.50 above that). Claude Code's fast mode for Opus 5.5 is listed at $8 / $40. Those look like small numbers until an agent rereads your repo forty times in an afternoon.

That second point is probably how somebody gets to $1,000.

Why coding agents burn more than chat

A chat costs what you type plus what you read. An agent costs what it reads to decide what to do, over and over, and you don't see most of it.

I wrote about the same mechanics on the API side in Keeping Claude's token bill from ruining your month: LLMs are stateless, so every turn resends the whole conversation. A coding agent makes that worse in three ways:

• Context is big by default. Files, diffs, test output, tool definitions. The agent pulls them in because that's its job.
• Loops. Run the tests, read the failure, edit, run again. Each lap resends the growing context.
• Model choice is sticky. If the default is the most capable model, every trivial rename gets frontier pricing.

None of that is a bug. It's the product working as designed, which is exactly why it's easy to stop noticing the meter.

How to budget it: start from the work, not the price list

A per-seat number like $29 is a budget built from the price list. It's simple to administer and it will be wrong for almost everyone: too much for people who open Claude twice a week, far too little for the person whose whole job is now reviewing what an agent wrote.

A better order:

1. Measure two normal weeks. Not a demo week. Normal. On Team and Enterprise there's usage analytics; on the API every response tells you the tokens it used.
2. Group people by how they work, not by title. Occasional users, daily users, "the agent is my pair programmer" users. You'll usually find a long tail and a small heavy group.
3. Give each group the cheapest option that doesn't interrupt them. Occasional users on Pro. Heavy users on Max or a premium seat, because a fixed monthly price is easier to defend than an open-ended API bill. Automated pipelines on the API, with a hard limit.
4. Re-check monthly. Models and prices move. A budget you set once is a budget you'll get surprised by.

If you're solo, the same logic applies with smaller numbers: if you keep hitting the five-hour limit on Pro, that's the signal to try Max for a month and compare, not to quietly add API credits on top and forget about them.

How to measure it

You can't cap what you don't measure, and "the invoice" is not a measurement, it's a post-mortem.

For agents I build on the API, the cost comes straight off the response: input tokens, output tokens, cache reads and writes. Log those per call, tag them with the user or tenant and the task, and "who is expensive and why" stops being a guess and becomes a GROUP BY. That's the setup I described in the token bill post, and it works just as well for internal tools as for products.

The useful metric isn't cost per user. It's cost per finished task: per merged PR, per fixed bug, per qualified lead. $1,000 a month is expensive if it buys a lot of rerun test loops. It's cheap if it replaces a week of someone's time. Accenture's cap treats both cases the same, which is the part I'd question if I worked there.

How to cap it without killing the useful part

Caps work best in layers, each set where the money is actually spent:

• Plan limits. Subscriptions already cap you; the five-hour window is a budget whether you like it or not.
• Admin spend controls. Team and Enterprise plans list user and organization-level spend controls. Use them per group, not one flat number for everyone.
• API hard limits. For anything on Console keys, set a workspace limit. An automation with an uncapped key is how a typo becomes an invoice.
• In-code limits for your own agents. A daily budget check before each call and an iteration cap on tool loops. In my WhatsApp bot, an iteration cap of five on the tool loop is what stops a runaway loop from turning into a runaway bill. I wrote that up in the Claude token post as "a kill switch".

Building an agent and want the cost controls in from day one instead of after the first scary invoice?

The cheap wins before anyone caps anything

Most of the savings come from not paying for the same tokens twice:

• Prompt caching for the static part of the context. Cache reads are a small fraction of the input price on every model on Anthropic's list.
• Right model per task. Classification, renames and boilerplate don't need the top model. Route them to Haiku or Sonnet.
• Shorter context. Point the agent at the files that matter instead of letting it rediscover the repo every session.
• Batch what isn't urgent. Anthropic's Batch tier exists for exactly the work nobody's waiting on.

If you're estimating the full cost of an agent you're building, not just the coding tool you use, I broke the build and run costs down in AI agent development cost.

So, is $29 a month enough?

For someone who uses Claude occasionally to draft or explain things, probably yes. Pro alone is $20. For someone running Claude Code as a daily coding agent, no, and the 404 Media piece suggests the people affected already know that.

The lesson isn't "AI is too expensive" or "companies are cheap". It's that usage-based tools need a budget built from usage. Measure for two weeks, split people by how they actually work, cap in layers, and track cost per finished task. That's less dramatic than a memo, and it doesn't leave your best people scrambling for tokens on a Tuesday.

FAQ

How much does Claude Code cost per month?

As of October 2026, Claude Code has no standalone price. It's included in Anthropic's paid plans: Pro at $20/month ($17/month billed annually), Max from $100/month (5x Pro usage) up to the 20x tier, plus Team and Enterprise seats. Enterprise is listed at $20 per seat per month plus usage at API rates. You can also run Claude Code with a Console account and pay per token at API prices, with no monthly ceiling unless you set one.

Is a subscription or the API cheaper for Claude Code?

For one person coding most days, a subscription is usually the predictable option: a fixed price with usage limits that reset on a rolling five-hour window plus weekly caps. The API is cheaper for light or bursty use and is the only option where the ceiling is entirely yours to set, which also means nobody sets it for you. Measure a couple of weeks of real usage before deciding.

Why did Accenture cap Claude at $29 a month?

According to 404 Media (October 15, 2026), Accenture told many employees it would now spend only $29 a month per person on Claude, after some had been spending as much as $1,000 a month. The article frames it as part of a wider trend of companies curbing AI tool spend once usage outgrew budgets. It doesn't publish an internal rationale beyond that.

How do I stop an AI coding agent from blowing the budget?

Set the cap where the money is spent, not in a spreadsheet: per-user or per-org spend limits in the Team/Enterprise admin, a hard limit on the API workspace, and in your own agents a per-day budget check and an iteration cap on tool loops. Then log cost per task so you know which work is worth the tokens.

Originally published on joancomadran.dev. I'm Joan, an AI engineer in Barcelona — work with me.