Which Claude Plan for Claude Code? Pro vs Max, Explained by Usage

You need a paid Claude plan to use Claude Code, and the entry point is Pro. Pro includes Claude Code and is enough for most people learning it or working on small projects. The Max plan exists for one reason: more usage. It comes in two levels that give you 5x or 20x the usage of Pro in each rolling 5-hour session. The Free plan does not include Claude Code, so it is not an option here.

The decision is not about unlocking features. Claude Code itself is the same tool on Pro and Max. What changes is how long you can keep working before you hit a limit. So the plan question is really a usage question, and the honest way to answer it is to start low and move up only when your own usage forces it. Check current prices on [Claude's own pricing page](https://claude.com/pricing) before you decide, since plans and prices change.

Here is the ranked answer, cheapest first. Pick the lowest one that does not leave you blocked mid-task.

There are also team and enterprise plans for organizations that need shared administration, seat management, and governance controls. For an individual builder or a solo agency operator, the real choice sits between Pro and the two Max levels.

Claude Code usage is metered in rolling 5-hour sessions, with a weekly cap layered on top. The 5-hour window is short-term throttling; the weekly cap is the ceiling for the whole week. Both Pro and Max share the same usage pool across Claude and Claude Code, so a heavy chat session and a heavy build session draw from the same budget.

When you reach a 5-hour limit, you wait for that window to reset and then keep working. When you reach the weekly cap, you are done until the next week - unless you are on the 20x Max level, which lets you opt into extra usage billed per token at standard API rates so you are not fully stopped. The exact number of prompts you get per window is not a fixed figure Anthropic publishes as a single number; it varies with how large and complex each request is, so treat any specific prompt count you see quoted elsewhere as a rough estimate, not a guarantee.

Upgrade when you are regularly blocked while you still have work to do. Not when you hit a limit once in a busy week - that is normal and cheap to wait out. The trigger is hitting the wall during the workday, often enough that waiting for the reset is costing you real momentum. That is the moment a bigger plan pays for itself in recovered time.

The mistake goes both ways. Some people over-buy on day one, pay for the 20x level, and use a fraction of it. Others cling to Pro while losing an hour a day to blocked sessions. The self-check we teach members is simple: for one week, note every time Claude Code stops you mid-task. Zero or one? Stay put. Several times a day? Move up a level. Let your actual usage make the call, not a guess about your future usage.

If you build for clients, treat the plan as a cost of goods, not a personal subscription. A single Max level that keeps you unblocked through a delivery week is cheap against the value of shipping on time. The usage a client project pulls - especially anything running in the background - used to hide inside a personal plan; now it is metered, so it belongs in how you price the work.