Claude Code Usage Limits: What Accenture's $29 Cap Tells Us

Accenture just told its own employees to stop treating Claude like an all-you-can-eat buffet. Starting October 1, 2026, the consulting giant centrally funds only $29 a month per employee for Claude usage. Anyone who burns through that has to go find a project budget willing to cover the rest. Some workers had been running up $500 to $1,000 a month. At least one person's access got cut off entirely (404 Media).

That's not a Claude problem specifically, it's a "what happens when 700,000 employees get metered API access and nobody puts a meter on it" problem. But it's also a useful wake-up call if you're paying for Claude Code out of your own pocket or watching your weekly limit evaporate by Wednesday. So let's talk about why these limits exist, what Accenture's cap actually tells us, and the specific things that stretch a Claude Code subscription further.

What did Accenture actually do?

Accenture capped central funding for Claude at $29 per employee per month, effective October 1, 2026, after some staff were racking up $500-$1,000 in monthly usage. The news broke via journalist Joseph Cox at 404 Media, who got the internal memo.

Here's the mechanic, and it's worth understanding because it's not a hard wall: Accenture's premium Claude accounts come with $250 in token usage a week baked in, but a lot of employees aren't on that premium tier. For everyone else, $29 is the default. Go over it and you need to find a specific project, tagged with a Work Breakdown Structure code, willing to absorb the overage. Basically: your team's budget eats the bill instead of IT's.

An Accenture spokesperson told 404 Media the company's policy is to "provide the right tool for the right work" and that it's still investing in AI. Translation: we're not cutting you off, we're just making you ask permission first.

I don't think this is Accenture getting cold feet on AI. I think it's a company realizing that "unlimited enterprise AI seat" was never actually unlimited, someone was always paying per token behind the scenes, and a few power users were quietly consuming 30-50x what a normal employee used. That math doesn't scale to 700,000 people. It wasn't going to last at any company this size.

Why does Claude Code even have weekly limits?

Claude Code limits usage through two overlapping windows: a rolling 5-hour session cap and a separate weekly cap, and hitting either one locks you out until it resets. Anthropic added the weekly layer back in mid-2025 specifically to stop a small number of accounts running Claude Code 24/7 in the background, including some people reselling login access, which was burning capacity that was supposed to be shared across everyone on the plan.

The plans break down like this:

Here's the part that annoyed a lot of people, myself included: Anthropic ran a temporary 50% weekly boost from May 13 to September 13, 2026. When it expired, the "permanent" replacement was a 25% bump over the original pre-May baseline, which is a real increase on paper but a 17% cut from what everyone had gotten used to all summer. If you felt like your weekly limit suddenly got stingier in mid-September, you weren't imagining it. You just got used to a promo rate and then the promo ended.

That's basically a smaller, individual-scale version of what Accenture just did at the org level. Give people a generous allowance, watch usage patterns adjust to fill it, then tighten it back up once the bill comes due.

How do I make my weekly Claude Code limit last longer?

Run /usage at the start of every session so you know where you stand before you're mid-task and suddenly locked out. Beyond that, the biggest wins come from context hygiene, not clever prompting:

1. Clear between unrelated tasks. /clear wipes the session instead of carrying forward thousands of irrelevant tokens from your last task. A single Claude Code turn can fire 8-12 tool calls and burn 50,000-150,000 tokens, way more than a plain chat message, so stale context compounds fast.
2. Compact proactively, not reactively. Run /compact around 40-60% context usage instead of waiting for Claude Code to force it on you at the edge. You can add a note to steer what the summary keeps.
3. Point Claude at exact files. Don't let it go searching a whole repo when you already know the file and line number. Vague prompts mean more exploratory tool calls, and every tool call costs tokens on top of the actual work.
4. Trim CLAUDE.md and disable MCPs you're not using. Every MCP server's tool definitions get loaded into context on every turn whether you use them that session or not. If you're not actively using a dozen integrations, that's dead weight.
5. Stop asking for full redos. If one section of a long output is wrong, ask Claude to fix that section, not regenerate the whole thing. This sounds obvious written down, but it's the single most common way people waste a 5-hour window.
6. Don't multi-Claude unless you need to. Running five parallel instances on five tasks is a real workflow for some people, but it also means five sessions drawing from the same weekly pool. Anthropic has said only about 5% of users do this, and they're disproportionately the ones hitting walls.

None of this is exotic. It's the same lesson Accenture just learned at a much bigger scale: usage limits aren't arbitrary, they track the cost of what you're actually doing with the tool. A sloppy workflow burns the same budget as a careful one, just faster.

Is the Claude Code weekly limit worth paying more to avoid?

If you're hitting the weekly wall most weeks on Pro, moving to Max 5x at $100 buys real headroom (140-280 Sonnet hours vs. 40-80), and it's a better fix than fighting the context-management battle every single session. If you're hitting it occasionally, the habits above will probably get you there without the upgrade. The r/ClaudeCode thread a reader of ours pointed to tells the same story from the other direction: people who went from constantly hitting the weekly cap to barely touching it, not by upgrading, but by clearing context aggressively and being specific about what they asked for (r/ClaudeCode).

My honest take: pay for the plan that matches how you actually work, but fix your habits first. A $200/month Max plan won't save you if you're letting a bloated CLAUDE.md and ten unused MCP servers eat your context on every single turn. That's the same mistake Accenture's power users made, just at a bigger dollar amount.

If you want more background on what's actually shipping from Anthropic right now, we covered the Claude Opus 5 launch and broke down Opus 5 pricing in separate posts. If you're deciding between models for a specific workload, our Opus 5 vs Fable 5 comparison covers the tradeoffs.

FAQ

Frequently Asked Questions