satori.
    Back to blog

    Buying Claude Licences in Australia: A Guide | satori.

    |9 min read
    Joachim Sahlin, CEO & AI Advisor

    Joachim Sahlin

    CEO & AI Advisor

    Book a meeting
    Buying Claude licences in Australia: an account, an invoice and a set of keys on a desk

    It nearly always starts the same way. One person picks up Claude Pro, gets hooked, and within a month five colleagues want the same thing. Then finance asks the awkward question: how do we actually buy Claude licences in Australia, in a way that works with invoices, GST and an IT lead who wants some visibility?

    It's a surprisingly messy question. Anthropic has several plans, the prices are all in US dollars, and there's no local "click here to buy" path for an Australian business.

    This guide is about the buying process itself. Not mainly what it costs, we've done that in the full Claude price list for Australia, but how you get from "we want Claude" to "everyone's up and running, and someone owns the seats". Step by step.

    What does it mean to buy a Claude licence?

    A Claude licence is simply a paid seat on one of Anthropic's plans. Either a personal subscription (Pro), a seat in a shared organisation (Team or Enterprise), or access to the models through the API in the Claude Console.

    Buying licences for a business means four things in practice: choosing the right plan, creating an organisation, adding the number of seats you need, and setting up billing. Not complicated on the surface.

    But the plan you pick drives almost everything else, so if you're still weighing that up, our guide to Claude for business covers which plan suits which shape of company. Here we're assuming the plan question is settled and focusing on how the purchase actually runs.

    What are the buying routes for Claude?

    There are four ways in. Most Australian businesses land in one of them.

    Claude Pro

    A personal subscription at US$20 per month, or US$17 per month billed annually1. You pay by card, per person. Perfect for letting a couple of key people test properly before you commit a whole team. No admin console, no shared invoice, no visibility.

    Claude Team

    The standard business route. US$20 per user per month billed annually, or US$25 month to month, with a minimum of two seats and a maximum of 1501. This is the first level with centralised billing, an admin console, SSO and role-based permissions. It's what you want the moment more than a couple of people are using Claude seriously. There's also a Premium seat at US$100 per user per month annually (US$125 monthly) that includes Claude Code and considerably more usage2. Most teams don't need it; the ones that do already know. We've broken the seat economics down in the Claude Teams pricing guide.

    Worth knowing before anyone over-promises internally: Team seats come with a 200k context window, which is generous but not unlimited. If someone is expecting to drop an entire document library into a single conversation, set expectations early.

    Claude Enterprise

    For larger organisations and regulated industries. Sales-assisted and quote-based, starting from around US$20 per seat plus usage, adding what Team doesn't have: SCIM provisioning, audit logs, custom data retention and a proper SLA2. This is also where a procurement team gets the contract terms it wants to negotiate.

    Claude API through the Console

    Not seats at all, but pay-as-you-go usage across the model family: Fable 5, Opus 4.8, Sonnet 5 and Haiku 4.5. The right route if you're building your own integrations or products on top of Claude. The wrong route if you just want your team chatting and drafting together.

    How do you buy Claude licences in Australia, step by step?

    Say you've landed on Claude Team, which most do. Here's what the purchase actually looks like, from account to live.

    1. Create or verify the organisation. Set up a work account on claude.ai and start a Team organisation. Decide who owns it and who administers it. Verify your domain so the right people land in the right workspace instead of spinning up rogue personal accounts.
    2. Choose the plan and seat count. Team starts at two seats. Start lean rather than generous, because you can add seats later far more easily than you can get money back for empty ones.
    3. Add your people. Invite manually or by CSV. On Enterprise you can wire up SSO and SCIM so accounts are created and removed automatically as people join and leave.
    4. Enter billing details. Card or invoicing. This is where the Australian reality starts to bite, and we'll get to that in a second.
    5. Set roles and permissions. In the admin console you decide who's an admin, who can invite others, and which connectors are allowed. Do this before people arrive, not after.
    6. Go live. Invite the team, build a couple of shared Projects with your own context in them, and check everyone can actually sign in.

    And here's the part worth internalising: the purchase is step one of ten. Getting people to genuinely use Claude is its own project, and we've written the whole 30-day plan for after you buy.

    Billing, currency and the GST question

    This is the part nobody discusses until the first invoice lands.

    Anthropic is an American company and bills in US dollars, globally1. So the cost of your Claude licences moves with the exchange rate every period. A budget that looked tidy in January reads differently in June. At roughly 1.5 to the US dollar, a US$20 seat is about A$30, but "about" is doing real work in that sentence.

    Then there's tax. GST on imported digital services has to be handled correctly in your BAS, which is routine for an accountant who has seen it before and an annoyance for one who hasn't3. Add vendor registration, the annual-versus-monthly decision (annual is cheaper but locks you in), and the question of whose card is on file, and a simple licence purchase quietly becomes a small procurement exercise.

    None of this is impossible to run yourself. It's just the reason a lot of Australian businesses decide they'd rather not.

    Who actually manages the seats?

    Here's the question that separates a good rollout from a messy one, and it has nothing to do with price.

    Someone has to own the licences. That means adding seats when a new hire starts, removing them the week someone leaves (not three months later), keeping SSO working, watching whether the people paying for Premium seats are actually using them, answering "why can't I log in" on a Tuesday morning, and reviewing the configuration against the Privacy Act when your biggest client sends through a security questionnaire.

    In a company with a real IT function, that's a small addition to an existing workload. In a company of thirty people without one, it lands on whoever was in the room when Claude was first mentioned. And that person has another job.

    This is the honest case for managed licensing: not that the licences are cheaper (they aren't, they're the same licences), but that the ongoing administration has an owner who isn't improvising.

    Is it better to buy Claude direct or through a managed partner?

    So, direct or managed? It depends on how much you want to do yourselves.

    Buy direct from Anthropic if you have an IT function that's happy to set up SSO, run user management and carry support internally, and you're comfortable with a USD invoice and support from a different time zone.

    Buy through satori-claude if you'd rather have one invoice in Australian dollars, a contact who answers the same day, and the Privacy Act configuration handled from the start. You pay for the Claude licences plus A$15 per user per month for the management, after a one-time A$850 setup. Licences run at A$42 per user per month for Standard or A$195 for Premium. Same Claude, same platform, someone else doing the paperwork.

    For a fifteen-person team on Standard, that's A$630 in licences plus A$225 in management, so around A$855 a month, plus the setup. Fixed, in AUD, on one invoice.

    Two things we'll say plainly. We're an independent Australian consultancy, not an accredited Anthropic partner, and we'd rather tell you that than let you assume otherwise. And if you want help getting the team genuinely using the thing, that's satori-launch at A$990 per user, one-time, from eight users; broader AI strategy is what an AI consultant is for.

    It isn't either-or. It's a question of where you'd rather spend your time.

    The bottom line

    Buying Claude licences for an Australian business is really four steps: choose the plan, create the organisation, add the seats, set up billing. Team suits most, Pro suits the smallest, Enterprise when compliance or scale demands it.

    The tricky bit is rarely the purchase. It's the USD invoice, the GST treatment, deciding who owns the seats, and the art of getting people to actually use what you bought.

    Want someone to take the whole thing off your hands? Book a chat and we'll run the numbers with you. No slides, just an honest conversation about what you'd actually be signing up for.

    Sources

    Read more

    Footnotes

    1. Anthropic (2026). Plans & Pricing. https://claude.com/pricing ↩ ↩2 ↩3

    2. Anthropic (2026). Claude Team and Enterprise plans. https://support.claude.com/en/collections/9387370-claude-for-work-team-and-enterprise-plans ↩ ↩2

    3. Australian Taxation Office (2026). GST on imported services and digital products. https://www.ato.gov.au/businesses-and-organisations/gst-excise-and-indirect-taxes/gst/in-detail/rules-for-specific-transactions/gst-on-imported-services-and-digital-products ↩

    Back to all articles
    Cookies

    We use cookies to improve your experience.

    Policy