Someone on your team upgrades to the most expensive plan on day two because a screenshot showed a red “usage limit” banner. Someone else stays on Free for six months, hits the wall every afternoon, and decides the whole category is a toy. Both people are reacting to pricing theater instead of a boring question: what do you actually open, how often, and with what kind of work?
This is Part 2 of Learn Claude from scratch. Part 1 placed company, model, and product in separate boxes. Now we walk Free, Pro, and Max the way you would compare phone plans: what you get, where limits bite, and when spending more is rational versus panic. Prices and feature bundles change. Treat every dollar figure here as as of writing and re-check claude.com pricing before you pay.
What you’ll learn
- What Free, Pro, Max 5x, and Max 20x are for (and who they fit)
- How usage limits roughly work (about every five hours, plus weekly caps on paid)
- Which headline Pro features matter for normal work versus specialist workflows
- Why the API Console is a separate wallet from your chat subscription
- When Team or Enterprise is the real answer instead of five personal Max seats
- A calm chooser so you pick a plan without FOMO
If you still mix up “Claude the chat product” with “Claude the model name,” skim Part 1 first. For general AI literacy, keep our LLM and generative AI explainer handy. Workflow habits beyond one vendor live in the Practical AI series.
The plan ladder in plain English
Individual Claude plans (consumer side) look like this as of writing. Always confirm on the live pricing page; tax and regional details vary.
- Free: $0. Real product, real limits. Fine for light exploration and occasional drafts.
- Pro: about $20 per month if billed monthly, or about $200 per year when billed annually up front (Anthropic’s page has shown that annual path as roughly $17 per month equivalent). More usage than Free, plus the paid feature bundle (details below).
- Max 5x: about $100 per month. Everything in Pro, with roughly 5× Pro usage per rolling session window, higher output limits, and priority-style access during busy periods (wording on the marketing page).
- Max 20x: about $200 per month. Same idea with roughly 20× Pro usage per session window.
Those multipliers are relative capacity, not a promise of “N messages exactly.” Long chats, big files, heavier models, code tools, and research-style features consume the pool faster than short questions. Anthropic’s own help docs stress that there is no fixed public message count because tasks differ.
How usage limits actually feel
Limits are the part people misread as “Claude got dumber.” Usually the model is fine and the meter is empty.
The rolling five-hour window
On Claude’s consumer plans, a major usage bucket resets on a rolling schedule on the order of every five hours. When you hit the cap, you wait for capacity to return, upgrade, or (on paid plans, where offered) add usage credits that bill more like API rates. Exact numbers are not a simple public “50 messages” card because a three-line email rewrite and a two-hour coding session are not the same cost to run.
Weekly limits on paid plans
Paid plans also use weekly limits so a single user cannot monopolize capacity. You can be fine in a morning sprint and still feel a weekly ceiling if you run heavy tools all week. Check Settings → Usage in the product when you care about the live bar rather than folklore.
One pool across surfaces
Web, desktop, mobile, and Claude Code (when included) generally draw from the same plan pool. Running Code in a terminal does not magically create a second free meter next to your browser chat. That surprise causes a lot of Max upgrades that could have been “stop dual-wielding two huge sessions.”
What Pro claims relative to Free
Anthropic’s pricing FAQ has described Pro as providing on the order of at least 5× more usage per five-hour session than Free, with Max multiplying Pro again (5× or 20×). Use those ratios as orientation, not a spreadsheet identity. Features and models also change what “one unit of work” means.
If you want the primary source language, read Anthropic’s usage limit article: usage limit best practices.
Free: what you actually get
Free is not a demo video. You can chat on web, iOS, Android, and desktop (availability depending on current download options), write and edit, generate code, search the web when the feature is enabled, and use a useful slice of everyday assistant behavior. Memory across conversations, file creation, code execution, connectors, and other extras appear on the marketing comparison table for Free in some periods. The durable truth is simpler: Free is capacity-constrained, and the ceiling shows up when you try to make Claude your all-day coworker.
Free fits you if:
- You draft the occasional email, outline, or explanation.
- You are evaluating whether the product style fits your brain before paying.
- You already have another paid assistant and want Claude as a second opinion only.
- Your employer has not approved paid consumer AI spend yet, and you stick to non-sensitive practice tasks.
Free will frustrate you if:
- You hit limits mid-project several days a week.
- You need the paid-only product surfaces (Claude Code and friends) as a daily driver.
- You rely on higher model access that Free does not include in the current matrix.
Frustration is data. If Free blocks real work, upgrade for capacity. If Free is fine and you upgrade because a podcast host said Max is “mandatory,” that is FOMO.
Pro: the default paid seat for most individuals
Pro is where Anthropic expects “everyday productivity” buyers to land. As of writing, the headline bundle includes everything in Free, plus more usage, and a set of named inclusions that matter if you read them as job tools rather than logo stickers.
More usage
This is the feature most people feel first. Longer sessions before the five-hour window complains. Room for iterative drafting: rewrite, then rewrite again, then ask for a skeptical pass. If your pain on Free was “I was in flow and the banner killed it,” Pro is aimed at you.
Claude Code
Claude Code is Anthropic’s coding-oriented product path (terminal and related workflows). It is included on paid plans as of the current pricing FAQ. Heavy Code use burns the same plan pool as chat. Developers who live in a repo all day often outgrow Pro and look at Max, or they split work with API credits. Casual “help me fix this query” users may never need Max.
Claude Cowork
Cowork is a separate product surface for agent-style computer work (exact scope evolves). Inclusion on Pro means you can try it without a Max tax. Whether it becomes your daily driver is a later series topic. For plan choice, ask only: will I open this weekly?
Claude Design and Claude Science
These are specialized products in the Claude lineup (design-oriented and science-oriented workflows). Pro marketing lists them as included. If your job is not design systems or scientific workflows, do not buy Pro only for the names. If those are your job, confirm current capabilities on the product pages before you plan a process around them.
Research, Projects, more models
Projects help you keep chats and documents organized for ongoing work (a client, a course, a migration). Unlimited projects on Pro (per current marketing) matters if you were drowning in a flat chat list. Research-style features help with multi-step information gathering when available on your plan. Access to more Claude models means you are less stuck on the lightest free default when a harder task needs a heavier engine (names like Sonnet, Opus, Fable generations as offered).
Claude for Microsoft 365
Pro lists a Microsoft 365 path. That matters in companies standardized on Outlook, Word, and Teams. “Matters” is not the same as “ignore security review.” Connectors and workplace integrations should follow your employer’s rules. Part 7 of this series goes lighter on work integrations; here the plan takeaway is simply that Pro is the consumer rung that advertises that door.
Pro is a sensible default if you use Claude several times a week for real deliverables, want Code or Projects, and hit Free limits often enough to notice. Pro is optional if you open Claude twice a month for fun outlines.
Max 5x and Max 20x: when more capacity is the product
Max is not a different personality. It is mostly more room and some priority / early-access framing on top of Pro.
- Max 5x (~$100/mo): about five times Pro’s usage per five-hour session window, higher output limits, priority access when traffic is high, earlier access language for advanced features.
- Max 20x (~$200/mo): same idea at about twenty times Pro’s session usage. This is power-user territory: long coding days, constant agent-style runs, or roles where waiting on a limit banner costs more than the subscription.
Buy Max when you can point to a pattern: “I hit Pro limits on most workdays while doing productive work I already know how to verify.” Do not buy Max because a stranger on the internet said 20x is the only serious tier. Plenty of excellent work happens on Pro. Plenty of mediocre work happens on Max with unverified SQL and confident wrong numbers.
If you are a developer comparing Max to pure API spend, run the math for your token volume. API pricing is public on the platform docs; consumer Max is a flat-ish subscription with shared limits. Neither is universally cheaper.
A comparison table you can actually use
Values are orientation as of writing. Confirm on claude.com/pricing.
| Plan | Ballpark price | Usage orientation | Best fit |
|---|---|---|---|
| Free | $0 | Light daily; easy to hit walls | Trying Claude, light drafts |
| Pro | ~$20/mo or ~$200/yr | Much more than Free; still finite | Regular work, Code, Projects |
| Max 5x | ~$100/mo | ~5× Pro per ~5h window | Daily heavy use, frequent Pro caps |
| Max 20x | ~$200/mo | ~20× Pro per ~5h window | All-day power workflows |
The API Console is a different product wallet
Two Anthropic-related logins confuse people for months.
- claude.ai subscription (Free / Pro / Max): human chat and included products, metered by plan limits (and optional usage credits on paid).
- Claude Platform / Console (API): keys for applications, automation, and builders. You pay per token (and related tool fees) for models such as Haiku, Sonnet, Opus, Fable generations. Pricing tables live on the platform docs and the API section of the pricing page.
You can hold both. Many developers do: Pro or Max for interactive Code and chat, Console keys for apps. Paying for Pro does not automatically fund unlimited API traffic. An API budget does not automatically unlock every consumer chat perk.
If your job is “I talk to Claude in a window,” you can ignore Console until a later series part. If your job is “I ship a feature that calls a model,” start with platform docs and finance’s cloud process, not only a personal Max card.
Team and Enterprise: when the org should buy
Personal plans are for individuals. As soon as several people need shared admin, SSO, central billing, or clearer training defaults, look at organization plans.
As of writing, Anthropic’s pricing page describes:
- Team: for groups (marketing has cited bands such as 2 to 150 people). Standard and Premium seats with different usage. Central billing, SSO, admin controls for connectors, Claude Code and Cowork inclusions, and default “no model training on your content” style enterprise messaging. Standard seat pricing has been shown around $25/seat/month monthly or $20/seat/month annual-equivalent; Premium much higher (on the order of $100 to $125/seat/month depending on annual vs monthly). Verify live numbers.
- Enterprise: larger scale, seat price plus usage at API rates in the self-serve framing, with deeper admin, SCIM, audit logs, retention controls, network controls, and compliance-oriented options (including HIPAA-ready offerings and a Claude Security beta where applicable). Sales-assisted paths exist for complex contracts.
Smell test: if five employees each buy Max on personal cards and paste customer data into personal accounts, you do not have a productivity win. You have a shadow IT pile. Team or Enterprise plus policy training is the adult move even if the sticker price looks higher than five Pro seats.
Plan chooser: pick without FOMO
Walk these questions in order. Stop at the first plan that fits.
- Is this for work with company data? If yes, ask IT or your manager which Claude path is approved. Do not invent a personal Max workaround for regulated data.
- How many days per week do you hit Free limits while doing useful work? If rarely, stay Free. If most weeks, consider Pro.
- Do you need Claude Code, Projects organization, Research, or Microsoft 365 integration as a regular tool? That points to Pro (or org plans), not Free heroics.
- On Pro, do you still hit limits on most full workdays? Track it for two weeks. If yes, Max 5x is the usual next step. If you are a full-day agentic or coding user and 5x still bricks you, Max 20x enters the chat.
- Are you building software that calls models in production? Budget Console/API (and cloud partner options) separately. Do not expect a chat plan to replace engineering cost controls.
- Are multiple people involved? Price Team/Enterprise against the chaos of personal cards. Include admin time in the comparison.
Notice what is missing: “Which model is winning benchmarks this week?” Benchmarks are interesting. They rarely justify a $200 personal subscription if your actual job is rewriting status updates twice a week.
Cost scenarios (toy math, not invoices)
These are teaching scenarios with round numbers. Your taxes, currency, and promotional pricing differ.
Scenario A: curious analyst
Three sessions a week, short summaries, no Code. Free is enough. If a quarterly deep-dive week feels cramped, a single month of Pro can be a temporary boost; canceling paths exist in billing settings (always follow the live cancel instructions).
Scenario B: individual IC who writes and codes lightly
Daily chat, weekly Code, Projects for two active workstreams. Pro at ~$20/mo is the default. Annual ~$200 if you already know you will keep it a year and the discount still exists when you subscribe.
Scenario C: full-time coding with agents
Claude Code open most of the day, large repos, frequent higher-tier models. Max 5x or 20x may be rational. Compare against API-heavy workflows and company-provided seats. Keep verifying code; a higher plan does not reduce the need to check AI-written SQL or review diffs.
Scenario D: ten-person team, mixed roles
Ten personal Pros is $200/mo before anyone buys Max. Add shadow data risk. Team standard seats may land near a similar monthly number with SSO and admin, depending on discounts and seat type mix. Run the real quote. The point is organizational design, not only arithmetic.
Common plan mistakes
- Upgrading before learning prompts. A vague one-liner wastes Max as efficiently as it wastes Free. Practice iteration on Free for a week with non-sensitive tasks.
- Ignoring the shared pool. Chat plus Code plus mobile “quick questions” is one meter. Stagger heavy jobs if you are near a limit.
- Using personal Pro for secret work data. Plan tier does not equal compliance. Policy does.
- Assuming annual is always better. Annual makes sense when you are sure. If you are experimenting, monthly reduces regret.
- Mixing API bills with chat bills in your head. Separate budgets, separate owners when possible.
- Chasing model names as a substitute for process. Heavier models help hard tasks. They also burn limits faster. Match engine to job.
- Treating the assistant as a source of record because you pay more. Payment buys capacity and features, not truth. Liability stays human.
Practice: a two-week plan experiment
You do not need a spreadsheet temple. You need honest notes.
- Stay on your current plan for ten workdays. Each day you use Claude, jot: minutes used, main task type (write, summarize, code, research), and whether you hit a limit banner.
- Mark sensitive vs non-sensitive tasks. If sensitive work appeared on a personal account, flag it for policy cleanup regardless of plan.
- Count limit events. Zero to one mild limit in two weeks: stay or light Pro. Several mid-task interrupts while doing real work: Pro or Max depending on severity.
- List features you opened. If you never opened Code, Cowork, Design, or Science, do not let those logos drive a Max purchase.
- Decide in one sentence. Example: “Pro monthly for three months because Free blocked two client-facing drafts per week.” Revisit after the quarter.
Optional: before any upgrade, re-read Part 1’s boundaries. Paying more does not make invented metrics safe for a board deck.
Age, terms, and other fine print worth knowing
Consumer Claude is for users 18+ under current Anthropic consumer terms (confirm the live legal page). Refunds are limited and depend on region and storefront (web vs Apple vs Google). Downgrades usually apply at period end; upgrades often apply immediately with proration-style credits. None of that replaces reading the billing UI when you click.
Feature matrices on marketing pages shuffle. A capability that is Free today might move. A model name on a blog post might differ from the picker in your account. When in doubt, the account you are logged into is the source of truth for what you can click, and the legal/pricing pages are the source of truth for what Anthropic claims to sell.
How this connects to the rest of the series
Part 3 walks first sessions on web and mobile so the plan you chose has a place to live. Later parts cover Projects, everyday jobs (writing, summarizing, planning), privacy habits, work integrations, and when Claude is the wrong tool. Specialized product deep dives (Code, Cowork, Design, Science) get their own tracks so this Free vs Pro vs Max post stays about money and capacity, not a 40-page manual.
If you write SQL with any assistant, keep the verification loop from how to check AI-written SQL. Plan tier never replaces that loop.
Recap checklist
- Free is real but capacity-tight. Pro (~$20/mo or ~$200/yr) is the usual individual paid seat. Max 5x (~$100) and Max 20x (~$200) buy more usage on top of Pro.
- Usage resets on a rolling window about every five hours; paid plans also have weekly limits. Surfaces share one pool.
- Pro’s headline extras include more usage, Claude Code, Cowork, Design, Science, Research, Projects, more models, and a Microsoft 365 path (confirm live).
- API Console billing is separate from chat subscriptions.
- Teams should prefer org plans and policy over a pile of personal Max cards for work data.
- Choose with two weeks of limit notes, not with FOMO. Re-check claude.com/pricing before you pay.
- Paying more never makes Claude a source of record. You still own the numbers.
Sources
- Claude plans and pricing (Free, Pro, Max, Team, Enterprise, API overview): https://claude.com/pricing
- What is the Pro plan: https://support.claude.com/en/articles/8325606-what-is-the-pro-plan
- What is the Max plan: https://support.claude.com/en/articles/11049741-what-is-the-max-plan
- Usage limit best practices (five-hour sessions, weekly limits, shared pool): https://support.claude.com/en/articles/9797557-usage-limit-best-practices
- Manage usage credits for paid Claude plans: https://support.claude.com/en/articles/12429409-manage-usage-credits-for-paid-claude-plans
- Claude Platform API pricing docs: https://platform.claude.com/docs/en/about-claude/pricing
- Claude Code product page: https://claude.com/product/claude-code
- Claude Cowork product page: https://claude.com/product/cowork
- Consumer terms of service: https://www.anthropic.com/legal/consumer-terms
- AMS: What are LLMs, ChatGPT, generative AI, and more: https://analyticsmadesimple.com/analytics/what-are-llms-chatgpt-generative-ai-and-more/
- AMS Practical AI series: https://analyticsmadesimple.com/series/practical-ai/
- AMS: How to check AI-written SQL: https://analyticsmadesimple.com/tutorials/how-to-check-ai-written-sql/
