Claude Cowork Pricing: What You Actually Pay per Task

All prices and limits come from Anthropic's pricing page and Help Center articles, checked October 27, 2026. Anthropic can change prices and plans at any time, so confirm on the pricing page before you buy.

Claude Cowork pricing by plan

Cowork is included on Pro, Max, Team and Enterprise. The Free plan doesn't include it (source: Anthropic Help Center). Here's how the plans compare:

Sources: Claude pricing, What is the Max plan?, What is the Team plan?. US prices, before tax.

A few details the table doesn't show:

• Max plans include priority access at high-traffic times, plus $100 (Max 5x) or $200 (Max 20x) in monthly API credits for the Claude Platform.
• Team plans run from 2 to 150 seats and include up to $500 a month in API credits.
• Team usage limits apply per member. They aren't pooled across the team, so a heavy user can't borrow from a light one.
• The monthly API credits on Max and Team don't apply to Claude, Claude Code or Cowork usage. They're for building on the Claude Platform, not for stretching your Cowork limits (source: Manage usage credits).

That last point trips up a lot of buyers. If you're choosing Max 20x because "it comes with $200 of credits," those credits won't buy you more Cowork time.

Which Claude plan fits your team

The right plan depends less on sticker price and more on how many Cowork tasks each person runs in a day.

Pro ($20/mo, or $17/mo annual)

Pro is the cheapest way into Cowork. It fits a solo operator or founder who runs a handful of tasks a day alongside regular chat. Since October 6, 2026, new Cowork tasks on Pro and Max run in the cloud, and scheduled tasks run even when no device is online. If you're testing Cowork before rolling it out, start here. For ideas on what to run first, see our list of Claude Cowork use cases.

Max 5x ($100/mo) and Max 20x ($200/mo)

Max is for individuals who live in Cowork. You get 5x or 20x Pro's usage per 5-hour session, plus priority access. If you keep hitting Pro limits before lunch, Max 5x is the next step. Max 20x makes sense when Cowork does a large share of someone's daily work, such as long research or ops tasks run back to back. Max is billed monthly only.

Claude for Teams: Standard ($25 or $20/member/mo)

Team Standard gives each member 1.25x Pro's per-session usage, plus central billing, SSO, admin controls for connectors and organization-wide plugin and skills deployment. The per-seat price is close to Pro, so for a team of light-to-moderate Cowork users it's usually the default. A five-person team pays $100 a month on annual billing, or $125 on monthly billing.

Claude for Teams: Premium ($125 or $100/member/mo)

Premium raises each member to 6.25x Pro's per-session usage. Because limits aren't pooled, you can mix seat types: put your heaviest Cowork users on Premium and everyone else on Standard instead of paying Premium across the board.

Enterprise ($20/seat/mo plus usage)

Enterprise separates the seat fee from consumption. You pay $20 per seat per month, then usage at standard API rates, on an annual contract. That model rewards teams that track and control token use closely, because every task shows up on the bill. Anthropic's Enterprise consumption guide covers spend caps by group and user.

How Claude Cowork usage limits work

Anthropic doesn't publish a fixed number of messages or tasks per plan. Every paid plan runs on two limits (source: How do usage and length limits work?):

• A session limit that resets every five hours
• A weekly limit

How fast you reach either one depends on the length and complexity of your work, the model you use, which features and tools are on, and the effort level you set.

Chat, Cowork and Claude Code all draw from the same pool. If you spend the morning in Claude Code, you'll have less left for Cowork that afternoon.

Anthropic is direct about Cowork's appetite. Its Enterprise consumption guide rates Cowork as "higher intensity" than chat: agentic workflows, multi-step task execution and Skills "generate significant intermediate token usage that may not be visible to end users," and a single Cowork task "can consume many more tokens than chat." If you sized your plan around chat habits, expect to hit limits sooner once Cowork becomes part of daily work.

New to how Cowork runs tasks? Our guide on how to use Claude Cowork walks through the setup.

Do Claude Cowork plugins and connectors cost extra?

No. Claude Cowork plugins are included with Cowork, and on Team and Enterprise they're controlled by the same admin toggle as Cowork itself, with no separate plugin setting or charge (source: Use Claude Cowork on Team and Enterprise plans). Claude connectors are available on every plan, Free included, per the pricing page. You won't see a line item for either.

They do cost you usage. A plugin bundles skills, connectors and sub-agents into one package (Use plugins in Claude), and Anthropic notes that tools and connectors are token-intensive. Every connector you leave on can add context Claude has to process, and every tool call adds tokens. On a usage-billed Enterprise plan, that shows up on the invoice. On Pro, Max or Team, it shows up as hitting your session limit earlier.

If you're weighing plugins against Skills, our explainer on agent skills covers how they differ.

Claude Cowork pricing per task: a worked estimate

Method 1: Plan price divided by tasks finished

This is the simplest way to think about per-task cost on a flat plan.

Per-task cost = monthly plan price ÷ Cowork tasks you finish that month

Hypothetical examples:

• Pro at $20/mo, 60 tasks finished in a month: $20 ÷ 60 = about $0.33 per task
• Pro on annual billing at $17/mo, same 60 tasks: about $0.28 per task
• Team Standard at $20/member/mo (annual), one member finishing 60 tasks: about $0.33 per task
• Max 5x at $100/mo, 300 tasks finished: about $0.33 per task

This tells you whether a plan pays for itself. Its weakness is that it ignores how close you came to your limits. If you finished 60 tasks but stalled at the session limit every afternoon, your real cost includes the time you spent waiting.

Method 2: Usage-credit math at API rates

When you run past your plan's limits on usage credits, or when you're on Enterprise, you pay standard API rates. Current rates per million tokens, from the pricing page:

Per-task cost = (input tokens ÷ 1,000,000 × input rate) + (output tokens ÷ 1,000,000 × output rate)

Hypothetical task: 400,000 input tokens and 40,000 output tokens. Input is the big number in this example because agentic work rereads files, tool results and earlier steps as it goes.

• On Sonnet 5.5: (0.4 × $2) + (0.04 × $10) = $0.80 + $0.40 = $1.20
• On Opus 5.5: (0.4 × $4) + (0.04 × $20) = $1.60 + $0.80 = $2.40
• On Haiku 5.5: (0.4 × $0.50) + (0.04 × $2.50) = $0.20 + $0.10 = $0.30

Notice where the money goes. In this example, input tokens make up most of the bill on every model. That's why the cost-cutting steps below focus on how much context each task loads. (Prompt caching can lower input costs on the API; the pricing page lists cached-read rates separately.)

How to log your own numbers

Estimates only get you so far. To find your actual cost, open Settings > Usage in Claude and track a normal week:

• How many Cowork tasks you finish
• When you hit the 5-hour session limit, and how often
• How close you get to the weekly limit
• Whether you dipped into usage credits, and how much you spent

After a week, run Method 1 against your real task count. If you're on Enterprise or using usage credits, compare your spend with Method 2 to find which tasks are the expensive ones.

What happens when you hit your limit

When you reach a limit, you can wait for it to reset, move to a higher plan or, on paid plans, turn on usage credits and keep working at standard API rates. On Pro and Max you set a monthly spend cap and optional auto-reload, so the bill can't run away from you. On Team, the organization enables usage credits for its members (What is the Team plan?).

This changes the plan math. A Pro user who occasionally overflows into usage credits may pay less overall than one who upgraded to Max 5x and never used half of it. Track it for a month before you upgrade.

Again, the monthly API credits included with Max and Team can't be used here. Usage credits for Cowork are a separate, pay-as-you-go balance billed on top of your subscription.

How to make each Cowork task cost less

Every tip here comes back to one thing: fewer tokens per task. On flat plans that means more tasks before you hit a limit. On Enterprise or usage credits, it means a smaller bill. The first five come from Anthropic's own usage guidance.

Turn off connectors you don't need for the task

Anthropic suggests turning off apps you've connected when a task doesn't need them. If a task only touches your docs, switch off the CRM, calendar and messaging connectors before you start.

Lower the effort level for routine work

Effort level is one of the factors Anthropic lists as driving usage. Save high effort for tasks where reasoning quality matters, and run formatting, cleanup and simple lookups at lower effort.

Start new conversations instead of extending old ones

Long threads carry their history into every new step, and conversations that trigger automatic context management use more of your limit. When you switch to a new task, start fresh.

Use Claude Projects for shared context

Claude Projects keep reference material in one place instead of pasted into each conversation, and they use retrieval, so only the relevant parts load into context. Keep project instructions short and remove files you no longer use.

Match the model to the task

Model choice changes cost directly. In the hypothetical above, the same task cost twice as much on Opus 5.5 as on Sonnet 5.5. Reach for the larger model when the task needs it, not by default.

Brief Claude once instead of every task

Here's the cost most teams don't see. Every time someone starts a Cowork task by pasting in the brand guidelines, the review checklist, the tone rules and an example of good work, that's input tokens. Multiply it by every task, every teammate, every day, and re-explaining context adds up.

The fix is to store that know-how once and let Claude pull only what a task needs. That's what Callstand does: it keeps your team's briefs, standards and review checklists in one place and serves them to Claude or ChatGPT through MCP and an API. Instead of each person pasting the same context, Claude reads the relevant part when it needs it. You get output that follows your standards, and each task starts lighter. See the brief-once workflow for the setup, or how Callstand works.

Still deciding between agents? Our Cowork vs Codex comparison covers how the two differ in practice.

Claude Cowork pricing FAQ