Claude Pro is listed at 18 euros a month, or 180 euros paid yearly. Claude Max comes in two tiers, around 85 and around 170 euros a month. These prices were checked with the vendor on 24 August 2026. The real question is not the amount. It is whether your usage problem comes from the plan or from your habits.
In the vast majority of cases, it comes from habits. Tandem has been configuring Claude for small and mid-sized companies for several months. The teams that hit their limit do not work more than the others. They simply let their context run away.

How much does a Claude subscription cost in August 2026?
Anthropic offers five levels. The free plan opens the chat, web search, memory and connectors. Pro adds broader usage and, above all, the four surfaces of the product, including Claude Code, Cowork and Claude Design. That is the first tier genuinely useful in a professional setting.
On the vendor's French pricing page, checked on 24 August 2026, Pro is listed at 18 euros a month, or 180 euros paid upfront for twelve months. Annual commitment therefore works out at 15 euros a month. Team starts at 21.04 euros per seat per month on annual billing, with a premium seat at 105.23 euros.
The two Max tiers stay quoted in dollars on that same page, at 100 and 200 dollars a month. At the 23 August 2026 rate, that puts Max 5x around 85 euros and Max 20x around 170 euros. Enterprise is billed per user, with consumption added at API rates.
| Plan | Price per month | Included usage | Who it fits |
|---|---|---|---|
| Free | 0 euros | The base, chat and connectors | Trying the tool out |
| Pro | 18 euros, or 15 yearly | The reference, rated x1 | Normal daily usage |
| Max 5x | around 85 euros | 5 times the Pro plan | Long sessions every day |
| Max 20x | around 170 euros | 20 times the Pro plan | Claude Code running non-stop |
| Team | 21.04 euros per seat | Broader than Pro | A team, central billing |
What Max really buys you compared with Pro
Max is not a smarter model. It is the same Claude with a bigger reserve. Anthropic's documentation describes two tiers, five times and twenty times the Pro plan's usage per session. Added to that are higher output limits, priority access during busy hours and early access to new features.
Metering happens at two levels. A session limit resets every five hours. A weekly limit applies on top, across all models, resetting at a fixed time assigned to your account. That second ceiling is the one that surprises heavy users.
These weekly ceilings are not new. TechCrunch documented them as early as July 2025, when they were announced. Anthropic was targeting accounts running Claude Code non-stop, and estimated fewer than 5 percent of subscribers were affected. The orders of magnitude published then spoke of 40 to 80 weekly hours on Pro, against 240 to 480 hours on the top Max tier.
The models named in that announcement have changed since, as the Claude 5 family replaced the previous one. The order of magnitude still says something useful. A Pro plan comfortably covers a normal working day. It does not cover an agent running without interruption.
Since 2026, a third mechanism exists. Usage credits let you keep going once the included reserve is exhausted, billed at standard API rates. That is often cheaper than moving to Max for a one-off spike, because you only pay for the actual overage.
Why you hit the limit, and why it is not your plan
The context window works like Claude's working memory. It holds your conversation, your files, the tools called and the model's own instructions. With every new message, Claude rereads all of it from the start. The cost of an identical question therefore rises as the conversation goes on.
I put numbers on this effect in a carousel published on LinkedIn in May 2026, which drew about 220 reactions. The first message of a session weighs roughly 500 tokens. The thirtieth weighs close to 15,500 for a comparable request, some thirty times more.

What Tandem observes on its long sessions confirms the mechanism. About half the budget goes to rereading history. A little over a tenth goes to the connectors and MCP servers left switched on, even unused. A few more percent go to the connected apps, calendar or mail for instance.

The habits that cut your usage before you pay more
About a dozen moves are enough to get back under the limit. Four weigh far more than the rest, and none of them requires technical skill.
- Start clean before saturation. Ask for a condensed summary of the conversation, open a new chat, paste that summary as the first message. I switch sessions at around 60 percent of context filled.
- Edit rather than correct. When Claude heads the wrong way, the reflex is to type no, try something else. The failed attempt then stays in the context and pollutes every later answer. Go back to the original message, edit it, run it again.
- Switch off dormant connectors. Every connector and every skill left enabled is read on every message, even when useless. Enable on demand, disable once the task is done.
- Pick the model to fit the task. A fast model handles a summary or a sort perfectly well. Save the most powerful model for complex reasoning, and leave extended thinking off by default.

The general principle fits in one sentence. What you keep out of the context costs you nothing. I developed this frugality logic in our article on what changed about prompting in 2026, and the full configuration mechanics in the ten-step guide to mastering Claude.
Should you commit annually to save money?
Annual commitment saves 36 euros on Pro, 180 instead of 216. The saving is real but modest. It is paid for in flexibility, and that is the actual trade-off.
I settled this question in a video about artificial intelligence subscriptions, before Max even existed. My recommendation has not changed. The market moves too fast to lock twelve months into one ecosystem. A year earlier I had in fact cancelled my Claude subscription, then came back to it when Cowork and Claude Code arrived. That is exactly the kind of switch an annual commitment prevents.
Monthly billing keeps another advantage. Moving from Pro to Max applies immediately, with the difference prorated. So you can step up for a heavy month, then step back down. Paying for Max all year for three weeks of crunch is the worst possible calculation.
Which plan for which profile in a company
For one person using Claude every day on writing, document analysis and office deliverables, Pro is more than enough. That describes most of the employees Tandem equips.
Max 5x makes sense when you run long sessions daily, typically more than two or three hours of sustained use. Max 20x only makes sense for continuous agentic usage, with Claude Code or Cowork working in the background for a good part of the day.
For a team, the calculation changes. Team brings central billing, admin controls and single sign-on, at 21.04 euros per seat per month. From five people up, that weighs less than managing five individual subscriptions. We detail this framing in our guide to Claude training for teams.
That explains most of the licences sitting idle. A Max subscription used as a chatbot costs ten times too much. A well-configured Pro subscription returns ten times its value. If you are still weighing ecosystems before picking a plan, our comparison of Claude against ChatGPT for business and the article on the reasons to switch to Claude address that upstream question.
Claude Pro or Claude Max, what to take away on price
Take Pro, monthly, and stay there. That is the recommendation in almost every situation Tandem encounters. Eighteen euros open the four surfaces of the product, and that is where the value sits, not in the size of the reserve.
If you saturate, start with the four habits above. They cost nothing and settle most cases. If you still saturate after applying them for two weeks, then and only then does Max become an honest calculation. And take it monthly, so you can step back down.
One last marker. A paid plan left unused costs more than a well-exploited higher tier. The teams that genuinely get value from Claude are not the ones paying the most. They are the ones who took the time to configure it, which I detailed for non-technical profiles in our practical guide to Claude Code.



