[object Object]

Tier Structure

As of April 2026, Anthropic’s commercial Claude offerings ladder up:

  • Free: limited daily messages on the public model, no SLA, no admin.
  • Pro ($20/month): individual use, ~5x free message limits, Projects, file uploads, access to Claude Code at consumer rates.
  • Max ($100 or $200/month tiers): power users, larger context utilization, higher rate limits, priority access during congestion.
  • Team ($30/user/month, 5+ seats): shared Projects, central billing, team admin, audit basics. Designed for small functions.
  • Enterprise (negotiated): SSO/SAML, SCIM provisioning, audit log export, advanced admin, role-based access, BAAs for HIPAA-regulated workloads, zero data retention guarantee, regional data residency options, dedicated capacity, named account management.

Cross-cutting: the API is sold separately, billed per token, with optional volume commits and the Anthropic Console for organization governance. Claude in AWS Bedrock, Vertex AI, and Microsoft Foundry are distinct procurement paths with their respective cloud’s commercial terms.

CRM Use Cases by Tier

  • Individual reps experimenting with summarization or draft assistance: Pro or Max.
  • Small teams (sales ops, marketing) prototyping content workflows: Team.
  • Production agents embedded in Salesforce, HubSpot, ServiceNow, Dynamics: Enterprise + API (or hyperscaler equivalent).
  • HIPAA-regulated CRM use (healthcare, payer, life sciences): Enterprise with BAA, or Bedrock with HIPAA-eligible configuration.
  • EU-data deployments requiring residency: Enterprise with EU region election, or Vertex/Bedrock EU regions.

Most serious CRM integrations combine tiers — interactive Team or Enterprise subscriptions for human users plus API for automated workflows. Procurement, finance, and security all see different artifacts.

API vs Subscription

Subscription tiers are designed for interactive use through Claude.ai (chat, Projects, Computer Use, Claude Code). API is designed for embedded application use (your code calls the model). Many enterprises maintain both — same model, different delivery mechanism, different cost structure, different governance.

API-specific capabilities not exposed in subscription tier:

  • Prompt caching (70–90% discount on cached prefix tokens; critical for high-volume CRM agents).
  • Tool use / function calling for agentic workflows.
  • Fine-grained streaming control.
  • Per-request system prompt override.
  • Programmatic batch access.
  • Direct integration with MCP servers.

CRM platform integrations (Salesforce Agentforce, HubSpot Breeze, ServiceNow Now Assist) generally consume Anthropic via API or via hyperscaler resale, not via subscription.

Cost Modeling

Subscription is per-user per-month, predictable. API is per-token, variable.

Worked example: a 50-rep sales team using AI for email drafting (10 drafts/day, ~3K input + 500 output tokens each):

  • Team subscription: 50 × $30 = $1,500/month.
  • API on Sonnet 4.5: 50 × 10 × 22 days × ($3 × 3K/M + $15 × 0.5K/M) = $182/month.

API wins big for predictable automation. Subscription wins for browse-mode interactive work where token usage is variable and includes file uploads, web search, and other tool-call costs.

Cost Considerations

Hidden costs to model:

  • Egress and integration infrastructure (API gateway, secrets management, observability).
  • Caching infrastructure for prompt caching to actually pay off.
  • BAA, ZDR (zero data retention), and EU-residency typically require Enterprise or hyperscaler — not available on Pro/Team.
  • Volume commits (100M+ tokens/month) unlock 15–30% discounts.

Common Failure Modes

  • Buying Team when usage is automation-heavy — overpaying versus API.
  • Buying API when usage is interactive — losing the Claude.ai surface that delivers the productivity.
  • Skipping Enterprise on regulated workloads and discovering the BAA gap during compliance review.
  • Single account, no SSO — provisioning chaos at 50+ users.

What to Do This Week

For any team running on Team or Pro at scale (>20 users) or any production CRM workload still on consumer subscription, model the API equivalent. Switch the path that pays for itself.

[object Object]
Share