Claude Enterprise Pricing: Wetin You Go Really Pay

Claude Enterprise cost na how much?

Claude Enterprise pricing get two parts, but dem publish only one. As of August 2026, dem list the seat as $20 per user per month, and dem bill am yearly. Dem bill usage separately: every token wey your team spends across Claude surfaces, including Chat and Claude Code, dey charged at standard API (application programming interface) rates on top of the seat. No usage allowance dey included. Your seat line dey fixed by headcount. Nothing dey fix your usage line.

Na so the bill dey work. The next part go explain who qualify, wetin the seat add over the Team plan, and how dem calculate the amount wey dem quote you.

Wetin make Claude Enterprise get seat price but no list price

Enterprise seat dey buy permission make you use Claude under your company controls. E no come with any token. No published monthly total dey, because two seats fit differ by one hundred times: manager wey dey ask four questions every day and engineer wey dey run Claude Code across one large repository both cost one seat, but their token bills no resemble each other.

How you go pay depend on which path you use. Self-serve path dey take card or ACH bank transfer, and e dey work with credits wey you buy upfront, so usage dey reduce balance wey you go top up. Sales-assisted path dey send invoice monthly in arrears. Invoice payment terms dey show when contract big reach $50,000 or more as of August 2026. Dem still dey sell Enterprise through AWS Marketplace. If you don already get AWS agreement, ask your account team whether Marketplace spend dey count against your committed spend, because na your AWS contract get that answer, no be Anthropic's price list.

How many seats Claude Enterprise dey require?

Minimum dey two. Self-serve Enterprise dey start for 20 seats. Sales-assisted Enterprise dey start for 50 seats. Team dey run from 2 reach 150 seats, so company wey pass 150 people go move go Enterprise because Team don reach im limit, no be because of any single control.

[
  {
    "plan": "Pro",
    "usd_per_seat_month": 17,
    "min_seats": 1
  },
  {
    "plan": "Team standard",
    "usd_per_seat_month": 20,
    "min_seats": 2
  },
  {
    "plan": "Team premium",
    "usd_per_seat_month": 100,
    "min_seats": 2
  },
  {
    "plan": "Enterprise self-serve",
    "usd_per_seat_month": 20,
    "min_seats": 20
  },
  {
    "plan": "Enterprise sales-assisted",
    "usd_per_seat_month": 20,
    "min_seats": 50
  }
]

Read that chart with one thing for mind. One Team premium seat wey cost $100 every month get usage wey five times pass standard Team seat, and that usage dey included. One Enterprise seat wey cost $20 every month no include any usage. The smaller number na the one wey get open end.

Wetin Enterprise get wey Team no get

Start with wetin Team don already get, because na for here upgrade arguments dey usually go wrong. Team get SSO (single sign-on) with SAML, domain capture, JIT (just-in-time) provisioning, role-based permissioning, and spend caps for both user and organisation level. Single sign-on no be reason to move go Enterprise. E dey there already.

Enterprise add the controls wey security team dey ask for by name:

• SCIM (system for cross-domain identity management) provisioning, so when person comot, your identity provider go deprovision am instead of person doing am by hand.
• Audit logs, with OpenTelemetry monitoring. Anthropic list these ones as Enterprise only.
• Compliance API wey dey return usage data, activity logs, chat histories and file content, filtered by user and time range.
• Custom data retention controls.
• Network-level access control and IP allowlisting.
• Customer-managed encryption keys. You provision one key for your own cloud account, and Anthropic use that key protect your team's chats, projects and files.
• US-only inference, wey keep your company's inference inside United States.
• HIPAA-ready offering (Health Insurance Portability and Accountability Act), plus fine grained role-based access control.

One idea dey run through the whole list: evidence. Team let person use Claude under sensible defaults. Enterprise let you prove later wetin that person do. When auditor ask which files employee upload last quarter, Compliance API answer am, but Team no fit, because Team no expose audit log or endpoint wey fit query one.

Data retention and model training

Anthropic no dey use content for commercial plans train their models by default. This one apply to Team and Enterprise too, so “dem go train on our conversations” no be reason to upgrade. Wetin Enterprise add na control over how long dem keep content, plus ability to read am back programmatically.

Anthropic dey publish SOC 2, ISO 27001, GDPR (General Data Protection Regulation) and CCPA (California Consumer Privacy Act) compliance for the platform. Those ones na properties of the service, no be line items wey you go negotiate. Retention length, the HIPAA offering, customer-managed keys and the inference region na the parts wey go enter contract.

Context window no be the reason again

Older write-ups talk say expanded 500K token context window na the Enterprise headline. Check that claim against the current help center before you buy based on am. As of August 2026, Anthropic document 1M token context window for Opus 5 and Sonnet 5 on all paid plans, and 500K for Opus 4.8 and Sonnet 4.6 on all paid plans. Context length dey follow the model wey you pick, so if you want bigger window, pick newer model. Choosing between dem na another question, and which Claude model to use for which job cover am.

Wetin dey decide your quote

Four inputs dey change the number.

• Seat count. Dem no dey sell Enterprise at all for fewer than 20 seats. From 20 to 49, you dey use the self-serve path with fixed terms. For 50 and above, salesperson go join, and na there custom terms fit become possible.
• Term. Enterprise get one seat type, priced per user per month and billed annually. The annual commitment na the normal deal structure, no be discount wey you need ask for.
• Expected usage. Usage dey bill at API rates with no allowance, so na here your risk dey. Estimate am from one real month of Team or API usage, no be from headcount, because headcount no tell you anything about tokens.
• The extras. HIPAA readiness, customer-managed encryption keys, US-only inference and custom retention length na separate requests. Raise dem for the first call, because dem fit change the agreement wey you go sign.

Before that call, collect one real number: the tokens your people use last month. Where Claude Code tokens really dey go and how Claude usage limits dey work both explain how to read that figure. Quote wey you no fit check na quote wey you no fit challenge.

One person, small team, or organization

• One person. Pro or Max. Enterprise no dey available for you, and na the seat minimum cause am. Start from how to choose between the Claude plans.
• 2 to 150 people, with no audit obligation. Team. You already get single sign-on, domain capture, role-based permissions and spend caps, with usage included for the seat. The Claude Team plan for small business explain the seat calculation.
• More than 150 people, or with an audit obligation. Enterprise. The trigger na either the Team seat cap or one named control from the Enterprise-only list, usually SCIM or audit logs.
• Machine workloads wey no human dey behind them. The API. A nightly batch job no need seat, and giving am one go waste the fee.

When Enterprise better pass putting API for corporate account

Enterprise usage dey follow standard API rates. So if team move from corporate API account go Enterprise, e no change wetin token cost. E add fixed fee for each human user, and that fee dey buy identity and audit controls wey raw API key no get.

API-only setup dey give metered usage without seat minimum and without monthly floor. E also no give interface for people wey no dey write code, no identity management through una directory, and no audit trail for each person, because API key no be person. Every key wey una issue na credential wey person must rotate, and nobody must explain why dem need am.

Break-even na how many humans need supervised access. Multiply seat count by monthly seat fee, then compare am with building the same controls by una own: proxy in front of API, una own key rotation, una own logging, and una own attribution for each user. If na under 20 people, comparison no go happen, because seat minimum don rule Enterprise out. If na few hundred people, seat fee usually smaller than the engineering work wey e replace. First, do the same calculation for each person with the break-even between Claude API and subscription, because the answer pattern na the same and the numbers easier to check.

FAQ

Claude Enterprise plan dey cost how much for each user?

The seat price wey dem publish na $20 for each user every month, with yearly billing, as of August 2026. That amount cover the seat only. Every token wey your team use dey bill separately with standard API rates; no allowance dey inside. So the total na seat price multiplied by number of users, plus the real usage. Dem no publish one total price because usage per seat dey vary too much to quote am ahead of time.

Wetin be the minimum number of seats for Claude Enterprise?

Na twenty seats if you buy am by yourself with card or ACH transfer. Na fifty seats if you buy through salesperson. Enterprise no dey available below twenty seats, so na Team you go use for that level. Team itself get limit of 150 seats. So any company wey pass that number go move to Enterprise, whether e need the extra controls or not.

Claude Enterprise include usage, or dem dey bill am separately?

Dem dey bill am separately. Enterprise dey charge every token with standard API rates on top of the seat fee, and no allowance dey bundled inside. Pro, Max and Team work the other way: usage dey come with the seat, and rate limits dey control am instead of invoice. Self-serve Enterprise dey take usage from credits wey you buy upfront, while sales-assisted Enterprise dey send invoice every month for usage from the previous month.

I need Enterprise before I fit get SSO for Claude?

No. Team already include single sign-on with SAML, domain capture and just-in-time provisioning. Wetin Team no get na SCIM provisioning and audit logs. Na these two things usually dey make people move to Enterprise, together with Compliance API wey fit read the records back. If the requirement na say employees must sign in with their work identity, Team meet am.

Company data dey used to train Claude for Enterprise plan?

No. Dem no dey use content for commercial plans to train Anthropic's models by default, and this apply to Team as e apply to Enterprise. Enterprise add custom data retention controls, Compliance API for exporting activity and content by user and time range, customer-managed encryption keys and US-only inference option.