Claude Team plan in Australia: what it costs in AUD, how to set it up and what to roll out first

What Claude costs for an Australian business

For a team of ten on annual billing, that's about A$340 a month, or A$4,080 for the year. On monthly billing the same ten people cost A$430 a month. You can mix seat types, so most teams buy standard seats for everyone and add a premium seat or two for the people who spend all day in long documents or writing code.

Prices change, and Anthropic says pricing, currency and tax can vary by region. Check the plan page inside your own account before you buy.

Pro or Team: when to make the switch

Pro is a personal plan. It's good for one person working on their own, and plenty of owners start there. The trouble starts when five people each have their own Pro account on their own credit card. Nobody can see who has access, saved work sits in personal chat histories, and each person decides for themselves whether their chats can be used to help train Claude.

Team fixes those problems. You get central billing and one admin view of everyone's seats. Anthropic doesn't train its models on your Team content by default. You can switch on single sign-on and control which connectors people can use. Team also includes Claude Code, Claude Design and Claude Science, plus enterprise search across your organisation.

Our rule of thumb: once two or more people are using Claude for client work, move them onto Team. The cost difference is small, and the admin and privacy controls are worth more than the money.

Setting it up properly in the first week

Most of the value comes from the setup, and most teams skip it. This is the order we work through with clients.

Pick an owner. One person owns the account, adds and removes seats and approves new connectors. In a smaller business that's usually the founder or the operations manager.

Invite people with work email addresses. If you use Microsoft 365 or Google Workspace sign-in, turn on single sign-on so people log in the same way they do for everything else. When someone leaves, removing their work account removes their access.

Connect the tools you already use, slowly. Claude can connect to Microsoft 365 (Outlook, SharePoint, OneDrive and Teams) and to Google Workspace (Gmail, Drive and Calendar). The Microsoft connector needs a one-time approval from your Microsoft administrator, and it only sees what each person can already see. We usually connect one source first, check it behaves, then add the next.

Write down what's safe to put in. A one-page policy does the job: which tools are approved, what client information can go in, and who checks work before it goes out. Our free AI use policy template is a starting point you can edit in twenty minutes.

Build Projects for repeat jobs. A Project holds the instructions, examples and reference documents for one job, so the whole team gets the same quality without writing a long prompt each time. Good first Projects are the jobs people do every week, like drafting a standard client email or summarising a meeting into your own format.

What to roll out first

Start with each team's own work. In our experience, generic training on "what AI can do" fades within a fortnight. Training built on a team's real emails and documents sticks, because the first win solves a problem they already had.

For each team, pick two or three jobs they repeat every week and that take longer than they should. Run a short session where everyone works on those jobs with Claude, using their own examples, and checks what it gives them before anything goes out. Then pick one or two keen people per team as champions, so the rest of the team has someone nearby to ask.

One client, a commercial property firm of around 70 people, is a good example. They run on Microsoft 365 and had planned a paid Copilot rollout. Before buying, they chose Claude Team instead. A few people were already using AI in patches and most of the team weren't sure where to start. We ran a session for everyone, then hands-on workshops for the property management and sales teams using their own emails and leases. Within the first month, staff showed or told us about 18 different ways they were using it, from drafting arrears emails to checking documents against a lease.

Mistakes we see often

• Leaving everyone on personal accounts. It feels cheaper until someone leaves with a year of client work in their chat history.
• Connecting everything on day one. Turn on one connector, check what Claude can see, then add more.
• Training once and stopping. A single workshop gets people started. Champions and a check-in a month later keep them going.
• Measuring logins. Usage quotas and tracking who logs in make people defensive. Ask them to show you what's working instead, and share the best uses across the team.

Common questions