Claude for Small Business in Australia: What It Is and How to Set It Up Properly

Claude for Small Business is a plugin from Anthropic that sits inside Claude Cowork. It connects Claude to tools you already use, like Xero, HubSpot, Google Workspace and Microsoft 365, and gives you ready-made workflows for jobs such as chasing overdue invoices and month-end prep. It works in Australia on any paid Claude plan, and it drafts the work for you to approve before anything is sent, posted or paid.

The plugin is easy to install. Setting it up properly is the part most businesses skip: which tools to connect first, what Claude is allowed to do in each one, and how you keep client and staff details out of places they shouldn't be.

The short version: start on the Team plan if more than one person will use it. Connect your email and Xero first, and leave both read-only. Give Claude one folder to work in, not your whole drive. Write down what it's allowed to help decide before 10 December 2026, when the new Privacy Act transparency rules start.

What Claude for Small Business is

Anthropic launched Claude for Small Business on 13 May 2026. Its launch post calls it "a package of connectors and ready-to-run workflows that put Claude inside the tools small businesses depend on."

At launch it had 15 workflows, 15 skills and seven partner connectors: QuickBooks, PayPal, HubSpot, Canva, Docusign, Google Workspace and Microsoft 365. A September 2026 update added 27 more integrations, including Xero, Shopify, Square, Stripe and Zapier. The plugin's own page now lists 43 ready-to-run workflows and 37 partner connectors.

Cowork is the part of the Claude desktop app that does longer jobs for you, working in the folders and tools you choose. To install the plugin, you open Cowork, click Customize, click the plus next to Plugins, find Small Business and click Install. A setup skill then asks about your business, helps you connect your tools and saves that context so every other workflow knows it.

Australia is on Anthropic's list of supported countries. Anthropic's September update says the plugin is on "every paid Claude plan", and it recommends the Team plan for businesses with more than one person. I won't quote prices here because they change. Check Anthropic's pricing page for current plans.

Sources: Anthropic, Introducing Claude for Small Business, Claude blog, September 2026 update, Small Business plugin page, Claude Academy install guide, Claude Cowork and Where can I access Claude.

What it connects to, for an Australian business

Most of the launch coverage was written for the US, where QuickBooks is the default. Here, most small businesses run on Xero or MYOB, with Microsoft 365 or Google Workspace for email and files. This is what each of those connections can do right now, from the vendors' own pages.

One rule runs through all of these. Claude inherits each person's permissions from the connected tool. Anthropic's connectors article says that if someone can't open a file or record in the source system, Claude can't reach it either.

If you want Xero and your CRM properly linked, that's a different job from asking Claude questions about Xero. Our guide to the HubSpot Xero integration covers that side.

Sources: Xero, Claude connector (AU), MYOB connector listing, MYOB press release, 17 August 2026, Claude Help, Microsoft 365 connector and Claude Help, using connectors.

Claude vs ChatGPT for a small business

"Claude vs ChatGPT" is rising in Google Trends Australia, and it's the first question most owners ask me. For everyday writing, summarising and answering questions, both are good. The useful differences for a small business are what each one plugs into and how you control it. This table sticks to things the vendors say on their own pages.

My honest take: pick the one that connects best to the tools you already use, then set it up with the same care. Most of the risk is in the setup, whichever app you choose. If you're in a sensitive industry, our post on whether ChatGPT is safe for NDIS participant data walks through the same questions for ChatGPT.

Sources: Xero blog, Claude for Small Business and ChatGPT, OpenAI Help, connected apps in ChatGPT, OpenAI Help, admin controls for apps and Anthropic Privacy Center, model training and Anthropic's launch post (Team and Enterprise training default).

How to set it up properly

This is the order I'd follow for a small team. It's slower than switching everything on at once, but you'll know what each connection can see and do.

1. Pick the plan for how you'll use it. If staff will use it, or client details will go in, start on Team. Anthropic says it doesn't train on Team and Enterprise data by default, and Team gives the owner admin controls. A solo owner on Pro or Max should check the Model Improvement setting in privacy settings.
2. Keep the owner account with the owner. On Team, an Owner has to enable each connector before anyone can use it. Members can request connectors by default, and only Owners can change that setting. Don't hand the owner login to whoever happens to be keen on AI.
3. Connect one tool at a time. Start with the one that takes the most of your time, usually email or Xero. Get comfortable with it before adding the next.
4. Leave connections read-only to start. The Microsoft 365 connector is read-only until an Entra admin approves write access and an Owner turns on write tools. Xero and MYOB are read-only anyway. Let Claude read and draft, and let people do the sending.
5. Set tool permissions. On Team, Owners can set each action to "Always allow", "Needs approval" or "Blocked", and staff can't override it. I'd set anything that sends, deletes or pays to "Needs approval". Anthropic's Team setting that allows "Always allow" for connector tools is off by default. Leave it off.
6. Give Cowork one folder. Cowork only sees folders you connect. Make a folder for Claude with your templates, price list and policies. Don't point it at the whole drive, and keep HR files and client records out of it.
7. Check what people can see before they connect. If your file sharing is loose, tidy it before anyone connects Microsoft 365 or Google Drive, because Claude sees what they see.
8. Run the setup skill properly. The setup skill asks about your business and saves that context for the other workflows. Give it real answers. Vague answers give you generic drafts.

If you'd rather not work through permissions and Entra admin consent yourself, book a free call and I'll show you what I'd connect first for your setup.

Sources: Claude Help, using connectors and Claude Help, Cowork on Team and Enterprise plans.

Keeping client and staff data safe, and the Privacy Act

First, check whether the Privacy Act covers you. The OAIC says most small businesses under its annual turnover threshold aren't covered. Some are covered whatever their turnover, including health service providers, businesses that trade in personal information and contractors on a Commonwealth contract. If you're not sure, the OAIC's small business page lists them all.

If you are covered, there's a new rule to know. From 10 December 2026, your privacy policy has to explain when a computer program makes a decision, or does something substantially and directly related to making one, that could significantly affect a person's rights or interests, using their personal information. You have to describe the kinds of personal information used and the kinds of decisions involved.

Two parts of the OAIC's September 2026 fact sheet matter for Claude users. It lists generative AI, including chatbots, as a computer program. It also says a decision can be in scope "even where a computer program output does not replace the entire decision-making process or is subject to human review." So "a person always checks it" doesn't take you out of scope on its own. Using Claude to shortlist job applicants or decide who gets credit terms deserves a hard look. Drafting a newsletter doesn't.

The OAIC's advice if you're unsure is to take a cautious approach and include the information. We've put together an automated decision-making privacy policy checklist that works through it step by step.

Practical habits that help, whatever your size:

• Use codes or initials for clients in prompts where you can, not full names and addresses.
• Keep health details, tax file numbers and bank details out of chats and out of Claude's folder.
• Treat every output as a draft. A person reads it before it reaches a client.
• Write a short note for staff on what Claude is for, what it never decides, and who to ask.

Sources: OAIC, new resources on transparency for AI and automated decision-making and the OAIC APP 1.7 to 1.9 fact sheet (PDF). This is general information, not legal advice.

Worked example: a realistic first week setup

Say a five-person plumbing business on Brisbane's northside. There's the owner, an office manager and three plumbers. They use Xero for invoicing, Microsoft 365 for email and files, and a job management app that has no Claude connector.

1. Monday. The owner signs up for Claude on the Team plan, installs the desktop app and adds only the office manager. The owner installs the Small Business plugin in Cowork and runs the setup skill together with the office manager, answering questions about services, service area and how they like to word things.
2. Tuesday. Their Microsoft 365 admin approves the connector in Entra. The office manager connects her own account, read-only. She asks Claude to sort recent supplier and customer emails by what needs a reply. Before she does, the owner checks which OneDrive folders she can open, and moves the staff contracts folder somewhere only he can see.
3. Wednesday. The owner connects Xero and picks their organisation. They try the overdue invoice workflow. Claude reads who owes what from Xero and drafts polite reminder emails. The office manager edits two, deletes one for a customer who's already called, and sends the rest herself.
4. Thursday. The owner makes a folder called "Claude" with the price list, standard quote wording and email templates, and connects only that folder in Cowork. He leaves the Microsoft 365 write tools switched off, so Claude can't send email at all.
5. Friday. They write a half-page note: Claude drafts emails and summaries, a person sends everything, Claude never decides who gets credit or who gets hired, and no customer addresses go into chats. Because the job app has no connector, they leave it alone for now and copy job notes across when they need to.

Nothing in that list is clever. The work is in the order: one person first, read-only first, one folder, and a written rule about what Claude doesn't decide.

What Claude for Small Business can't do yet

• It can't change your books. The Xero and MYOB connectors are read-only, so Claude can't raise invoices, reconcile or post transactions there. You still do that in Xero or MYOB.
• MYOB isn't for everyone yet. The connector is in beta and MYOB is rolling it out in phases.
• It doesn't know your industry software. If a tool isn't on the connector list, you're looking at Zapier, having Claude build a connector, or a custom connection.
• It isn't your accountant. Xero says the answers aren't tax, compliance or financial advice.
• Local history stays on each computer. Anthropic says Cowork history for local sessions is stored on users' computers, and admins can't centrally manage or delete it yet. Think about that before staff use it on a shared or personal laptop.

For a wider view of where AI fits in a small business, and where it doesn't, see how to use AI in a small business in Australia. If you're weighing up something that runs on its own, our guide to AI agents for small business covers that.

When it makes sense to get someone to set it up

If you're a solo operator with Xero and Gmail, you can probably do this yourself with the steps above. It's worth getting help when one of these is true:

• Staff will use it, and you need permissions, folders and admin settings right from the start.
• You handle sensitive information, like health, NDIS, legal or financial details.
• Your main system has no connector, and you want Claude to work with it.
• You're covered by the Privacy Act and need to know whether your use is in scope for the December changes.

This is close to what we've done before. We set up Claude assistants for an NDIS provider as part of a Microsoft 365 compliance build. They used participant codes and never names, and every output was a draft for a person to check. You can read about the wider build in our NDIS compliance automation case study.

I also run Workvolve day to day on my own setup built on Claude Code. It gives me a morning briefing from my calendar, inbox and meeting notes, keeps a memory of every client and decision, and drafts everything. Nothing sends until I say so. The same approval-first habit is what I'd set up for you.

Our custom AI agents service covers Claude setups like this, from choosing connectors and permissions to custom connections for software that isn't on the list. It's built in your own accounts, so you own it.

Want Claude set up properly for your business? Tell us which tools you run on. We'll show you what we'd connect first, and what we'd leave switched off. Book a free call.