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

Posted on Oct 16 • Originally published at joancomadran.dev

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?

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.

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:

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.

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.

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.

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.

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

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

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

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.

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.

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.

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.

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.

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.