Claude Team Pricing in the UK, Canada and Australia: What Seats Cost

Claude Team costs $20 per standard seat per month billed annually, or $25 billed monthly; premium seats are $100 or $125. Tax is not included. Anthropic says those are its US prices and that currency, price and tax handling vary by region, so a UK, Canadian or Australian buyer sees the local amount and any tax at checkout.

The standard seat is only one line in the bill. Team has a two-seat minimum, premium seats cost more, and the annual rate means paying the year up front. A local invoice can differ from a currency conversion you perform yourself, even before your finance team decides how to record tax.

The published Team figures and the missing local quote

Anthropic's public pricing page gives a clean benchmark: a standard Team seat is $20 a month when billed annually, or $25 on a monthly subscription. A premium seat is $100 a month on annual billing or $125 monthly. Team supports two to 150 seats and allows a mixture of standard and premium. The pricing page states that prices shown don't include applicable tax. Anthropic's Team plan help article goes further: the figures are for US customers, and pricing, currency and tax handling vary by region. It sends buyers to the upgrade page at claude.ai/upgrade to see the current price for their location, and Anthropic publishes no separate sterling, Canadian-dollar or Australian-dollar table.

There is no responsible way to turn that table into a fixed sterling, Canadian-dollar or Australian-dollar list price from the public page alone. The exchange rate on the day you search is not necessarily the rate on Anthropic's invoice, and a card provider may apply its own conversion. For a purchase decision, capture the actual checkout quote for each billing interval while signed in as the intended organisation owner. Do not publish a converted figure in a budget as though Anthropic had promised it.

A practical quote record needs the date, seat mix, billing interval, currency, amount before tax, displayed tax, total due now and next renewal date. Save the checkout screen or draft invoice, then make the purchase against that record. If your business needs a particular tax invoice, ask the billing team or qualified adviser which entity details must be entered before paying. The price table is useful for comparison; the checkout is the payable offer.

The Complete Excel Course with AI Integration

From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.

By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner

Buy now

Build a ten-seat budget that survives the first invoice

For an illustrative architecture practice with ten people, suppose eight colleagues need standard seats and two people working on large document sets need premium seats. The annual-billing benchmark is eight times $20 plus two times $100, or $360 per month equivalent. Anthropic charges the annual subscription up front, so the benchmark cash commitment is $4,320 for twelve months before tax. On monthly billing the same mix is eight times $25 plus two times $125, or $450 each month before tax. Across a full twelve months that would be $5,400, assuming the seat mix and listed rate stayed the same.

The difference is $1,080 over twelve months in this illustration, but that is not a prediction of savings. Annual billing reduces the published unit price while moving more cash to day one and making unused seats harder to unwind. Monthly billing gives the practice a shorter commitment for a trial. The useful comparison is not simply $360 against $450; it is $4,320 now against a series of monthly payments, the local invoice, and a realistic plan for whether all ten people will use their seats.

Run a second scenario before paying. If the practice begins with two standard seats, the published annual benchmark is $480 paid up front; monthly billing is $50 each month, or $600 over twelve unchanged months. This is the smallest Team purchase, and it is often a better test than placing ten people on day one. A sole practitioner still needs two Team seats; an individual plan may be more suitable if central administration and sharing are unnecessary. The Team value decision is separate from this location-specific invoice check.

Then test a mixed expansion: six standard and one premium would be $220 per month equivalent on annual billing, or $2,640 up front before tax. On monthly billing it would be $275 per month. A single premium seat changes the total markedly, so name the role and expected workload behind it. Buying premium for everyone because a few users hit limits is an expensive shortcut. Premium provides five times the usage of standard according to Anthropic, but it does not guarantee a fixed count of prompts or pages.

What annual billing, seat changes and tax do to cash flow

Annual means the twelve-month seat price is billed once at the start; it is not a promise that you can pay $20 each month. On a monthly plan, the $25 standard-seat benchmark is charged each billing cycle. When a member is added or a seat upgraded partway through a period, Anthropic says it charges a prorated amount immediately. Removing a member does not produce an immediate refund or credit; the seat becomes available for reassignment. The same principle matters if a colleague leaves the practice two weeks after an annual renewal.

Imagine an illustrative marketing agency with four standard annual seats. The published benchmark is $960 at renewal, before tax. One person leaves after two months. The administrator removes their access, but the subscription still has four purchased seats that can be reassigned. The owner should not assume a ten-month refund. If a replacement starts in month four, give that person the vacated seat before adding another. This simple register prevents paying for five seats while only four people work in Claude. If nobody replaces the leaver, an owner has to reduce the plan's total seat allocation to lower the bill; Anthropic says a reduction takes effect at the next renewal (the annual renewal date on annual plans) with no prorated refund when the change is submitted.

A different illustrative case is a recruitment agency adding a premium user halfway through a monthly cycle. The published increment from standard to premium is $100 per full month on monthly billing. The immediate charge is calculated for the remaining days, so it will be lower than a full month's increment, while the next complete month carries the full premium rate. Record both amounts. A manager who compares the smaller first charge against a normal monthly budget will otherwise underestimate the recurring cost.

Anthropic's own billing article works the same arithmetic in dollars, and it is worth copying the method into a local-currency sheet. On a monthly plan, ten standard seats cost $250 on 1 January. Upgrading five of them to premium on 15 January, with 16 days left in a 31-day month, costs $100 × 5 × 16 ÷ 31, or $258.06, charged that day. On an annual plan, ten standard seats cost $2,400 up front; upgrading five to premium with 275 days left in the subscription year costs $80 × 5 × 12 × 275 ÷ 365, or $3,616.44. Both examples exclude tax. Swap in the local seat prices from your own checkout and the same formula predicts a mid-term charge before anyone clicks upgrade.

Anthropic says displayed prices exclude applicable tax, and both of its worked billing examples end with the note that taxes are not included. That matters in all three markets in the title: an owner should not treat the pricing-card figure or a dollar example as the gross invoice. The exact treatment depends on the account and billing details. Enter the organisation's correct legal and billing information, inspect the tax line on the final quote, and reconcile the actual invoice after payment. A bookkeeper can advise how the amount is recorded; the tutorial cannot determine the tax treatment for a particular business.

Three billing settings are cheaper to get right before the first charge than after it. First, when the billing address is eligible, the Team signup shows an optional field for the business's tax ID; Anthropic says later changes to billing details apply only to future billing cycles, and completed invoices cannot be updated retroactively. Second, if the invoice should carry the company name rather than the cardholder's, an owner ticks "Use a different name on invoices" when adding the payment method and fills in the "Bill to" field. Third, an organisation that is exempt from tax cannot sign up as exempt; Anthropic's billing team reviews the exemption document after subscription and issues a credit note for tax already charged. Each of these is a support exchange if it is missed, so put all three on the checkout checklist.

Anthropic's Team billing FAQ lists credit, debit and prepaid cards as the accepted payment methods and says other forms, including bank transfers, are not accepted. If that card is charged in a currency other than the one the account is held in, add a separate line in the internal budget for possible card conversion costs. Do not label that line an Anthropic fee. It is a payment-method contingency until the card issuer's terms and the first statement confirm it. A useful comparison sheet therefore has three figures: Anthropic's quoted subtotal, tax on the quote, and any bank-side cost visible on the statement. Keeping them separate makes later renewal comparisons meaningful.

The pooled API credit is not a cheaper seat

Anthropic's Team page now says a Team organisation can receive up to $500 a month in pooled Claude API credits. Its API-credit help article sets the rate at $20 per standard seat and $100 per premium seat, pooled into one monthly balance capped at $500; Anthropic's example is three standard plus two premium seats receiving $260, and adding a third premium seat lifts the next cycle to $360. This is a separate Platform allowance for API use. It covers the Claude API, Managed Agents and the Agent SDK run with an API key, but not interactive Claude Code sessions or extra usage after someone hits a seat limit. It is not a reduction of the Team invoice, an automatic reimbursement, or an unlimited allowance for chat in the Claude app.

Suppose the illustrative architecture practice above never uses the Claude API. The eight-standard, two-premium seat bill does not fall because the API credit goes unused. Conversely, a team using an application built on the API should review the credit balance and Platform billing separately. On the published rule, its eight standard and two premium seats would earn $160 plus $200, or $360 a month in credits. One owner has to link a Claude Console organisation and claim the pool, and Anthropic says the offer appears only after seven days on an eligible plan, so confirm the actual figure in the Console balance before counting on it. The wider seat-tier comparison can help if that application use is the main reason for moving beyond individual subscriptions.

Here is a concrete bookkeeping example. A four-person law firm sets aside $100 per month for a document workflow on the API and buys four standard Team seats on annual billing. The seats cost $80 a month equivalent, and on the published rule they also bring $80 a month of API credit. The matching figures are a coincidence of the rates, not a refund. Record the credit against API usage in the Platform ledger, where it covers $80 of the $100 budget, and keep the seat charge in the subscription ledger. Combining the two into a made-up "net seat price" conceals the fact that app access and API calls have different limits, renewal rules and owners.

Choose the smallest useful seat mix

List the work first, then choose seats. For each prospective user, write one recurring task, the source material and the person who checks the answer. A colleague who drafts two short emails a week may not need the same seat as someone who works through long specifications daily. Do not buy premium because a job title sounds senior. Anthropic describes premium as more usage, not different approval authority or a separate data-control tier.

Use a filled-in roster, not a vague "ten licences" request. In an illustrative recruitment agency, the roster might read: owner, standard, reviews weekly pipeline summary; two consultants, standard, draft interview notes with human checks; operations lead, premium, processes long candidate packs; finance lead, no seat in the first month, receives the approved summary only. That is four paid seats initially, with one deliberately deferred. The fourth line is as important as the other three because it prevents accidental licence growth before a workflow exists.

Set a trial decision in advance. After four weeks, ask each seat holder to show two real outputs, the source documents used and what they corrected. Track whether a limit stopped important work and how often. If only the operations lead reaches a limit, test premium for that seat alone. If everyone spends time correcting basic source errors, the issue may be document quality or permissions, not the subscription tier. For an owner looking at alternative business subscriptions, the AI subscription price comparison provides a wider budget frame.

One failure pattern is shared logins. Anthropic's seat rules say each Team seat is assigned to one named individual and only that person may use it, and that reassignment is meant for joiners, leavers and role changes, not for rotating one seat among several active users. Two staff on the same account may make the minimum look cheaper, but it breaks those terms and muddles permissions, auditability and ownership of conversations. Buy named seats for people who actually use the tool, remove departing people promptly, and reassign their paid seat where appropriate. Another is turning on extra usage credits without a spending decision. Treat any optional usage top-up as a separate, approved budget, not an incidental feature of Team.

A checkout checklist for the three markets

Open the upgrade flow as the intended organisation owner, select the exact standard and premium mix, then compare monthly and annual choices. Write down the invoice currency and whether the displayed subtotal is a local amount or a dollar amount. Check the company name and billing address, because the tax result depends on the account details. Capture the tax line and total due. Repeat with the other billing interval if the interface permits, and give the finance approver both quotes on the same day.

1. Confirm that the Team account is the one the team will use, not an employee's personal subscription.
2. Count named users and keep at least two seats in the quote; separate standard from premium.
3. Record the exact currency, subtotal, tax and total shown at checkout.
4. Record whether the annual choice charges the whole year now and the renewal date.
5. Check whether a card conversion cost could appear separately on the bank statement.
6. Ask whether any colleague already pays for Pro, Max or Ultra personally: upgrading that account to Team in place cancels the individual plan with a prorated refund, unless they tick "Keep your personal account separate" during team creation.
7. Save the invoice after purchase and compare it with the captured quote.

A filled-in illustrative approval note could say: "Four standard Team seats; annual public benchmark $960 before tax; local checkout subtotal and tax to be attached; owner approves only if the payable total is within the subscription budget; finance records the renewal date." The note does not invent a local price. It tells the buyer which missing number must be copied from a real quote. For a Canadian or Australian entity paying through a shared corporate card, also check which legal entity owns that card and the subscription before selecting the billing address.

Do not use a screenshot from another customer's account as a local tariff. Location, currency, promotions and tax details may differ, and an old screenshot is particularly risky for a product that changes plans. The practical answer for the UK, Canada and Australia is therefore a published dollar benchmark plus a required local checkout check. That is more useful than a precise-looking exchange conversion that will fail on the first invoice.

For a budget that must be approved before a checkout account is ready, show a provisional range rather than an invented local total. Take the two published billing benchmarks for the exact seat mix, mark both as pre-tax published dollar reference figures, and leave separate empty cells for local subtotal, tax and card charges. Set a maximum payable amount in the organisation's own accounting currency and require the buyer to come back for approval if the live quote exceeds it. This creates a decision that can be made today without pretending to know tomorrow's invoice. It also prevents a common approval error: comparing an annual cash payment with a monthly operating budget without multiplying by twelve.

Review the first month and the renewal

Give one person responsibility for the seat register. Once a month, compare paid seats with active named users and ask whether each has a specific workflow. Review premium seats first, because their published annual-equivalent price is five times standard. Check the API credit panel only if the business actually uses the API. Compare the invoice subtotal, tax and card statement so the true cash cost is visible in one place.

At least a month before renewal, make a fresh estimate using the current seat mix and current vendor page. A ten-seat team that changes to seven standard and one premium should not carry the old ten-seat forecast forward. If two seats are unused, reassign them or plan the seat reduction at the permitted point. Keep the original quote and the current price page side by side; neither alone describes the next invoice.

Finally, review access, not just cost. A connector can make Claude useful by reading workplace material, but it should inherit the access the user is meant to have. When trialling connected workflows, document which accounts can see which information and who approves outward actions. The business app connection guide is a useful next check before wider rollout. A correct local quote pays for seats; a controlled rollout makes those seats worth paying for.

Further reads

• ChatGPT Business vs Claude Team: Seat Costs for a Small Consultancy — Compare a second team subscription with the same seat count.
• How to Set Up Claude Projects as a Shared Team Assistant — Plan what the paid workspace will hold.
• ChatGPT or Copilot for a Microsoft 365 Business? — Compare another workplace assistant budget.
• How Much Does a Custom AI Assistant Cost a Small Business? — Distinguish seats from a custom build.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Claude pricing page; Claude support articles What is the Team plan?, How is my Team plan bill calculated?, Team plan billing FAQs, Purchase and manage seats on Team plans, Monthly API credits for Max, Ultra and Team plans, and Add or update your Team plan's tax ID (all checked 5 November 2026).