Claude Plans
Also: Claude pricing, Claude Team, Claude Enterprise, Claude Pro, Claude Max
Claude's plans as of November 2026. For individuals: Free; Pro ($20 a month) with higher limits, connectors and Claude Code; Max and Ultra for much higher usage. For companies: Team, for 2 to 150 people, with Standard seats ($25 a month, or $20 billed annually) and Premium seats ($125, or $100 annually) that include about five times the usage; and Enterprise, which charges $20 a seat plus usage at API rates (20-seat minimum) and adds SCIM, audit logs, the Compliance API, custom retention and a HIPAA-ready setup. Neither Team nor Enterprise trains models on your data. Check claude.com/pricing before buying, because prices change several times a year.
In practice
You're using Claude for personal productivity and hitting the message limit constantly. You upgrade to Claude Pro. Your company wants to give the whole team access with shared Projects and admin controls — that's Claude Team. A developer building an app on Claude uses the API, which is usage-based and not a subscription plan.
Related concepts
Where Claude Plans shows up
13 articlesClaude's plans as of November 2026, in plain terms: what each costs, who it is for, and the simple rules for picking one for yourself or your company.
A one-page AI policy beats a long one nobody reads. Sort tasks into three zones, cover five things, and update it every few months. Updated for November 2026: connectors, computer use, personal accounts and the text watermark.
The problem with AI ROI isn't that it's hard to measure — it's that teams measure the wrong things. Here's what to track instead, and how to present it in a way leadership will actually act on.
Getting Claude configured is the easy part. Getting people to actually change how they work is harder. Here is what that looks like when done well.
The security and privacy facts a Claude Team or Enterprise admin needs, as of November 2026: training and retention by plan, SSO and SCIM, what stays off-limits, the new security controls, and a four-step setup.
Rolling out to 10 teams at once is a recipe for chaos. Here is the sequencing strategy that works — who to start with, how to expand, and what to do when a team is struggling.
A complete, one-page AI usage policy template for company-wide Claude deployments — with three variants: general company, professional services, and healthcare-adjacent. Fill in the bracketed fields and you have a policy ready for legal review.
Most admin guides cover getting Claude set up. This one covers what happens after: the recurring work, the common incidents, the governance tasks, and what a realistic monthly admin time commitment looks like for a 100-600 person company.
You are delivering faster and charging the same. That is a positioning problem, not a delivery problem. Here's how to reprice your AI consulting work before your clients notice you've gotten better.
IT isn't the enemy of your Claude rollout — they're the ally you haven't briefed yet. Here's exactly what IT needs to see before they can say yes, and how to give it to them without triggering a six-month procurement cycle.
Your manager doesn't need an AI pitch — they need a staffing and efficiency argument with AI as the mechanism. Here's how to write it so leadership can say yes.
The November 2026 lineup: Fable 5.2, Opus 5.5, Sonnet 5.5 and Haiku 5.5. How to pick, why Sonnet 5.5 is the right default for most work, and why tuning effort usually beats switching models.
The first two weeks for whoever owns a Claude rollout, as of November 2026: learn how each team works before you configure anything, set the few controls that matter on day one, and know what a good first month looks like.