Claude Cowork is the desktop version of Claude that works inside your actual files: it reads the folders you give it, drafts documents, prepares reports, and runs scheduled jobs while you get on with billable work. For an Australian small or mid-sized business, the difference between a setup that sticks and one that gets abandoned by week three is rarely the software. It comes down to three decisions made on day one: which folder it works in, which plugins it carries, and which guardrails it operates under.
This guide walks through those decisions in order. None of it requires a developer. All of it requires somebody in the business to own the answers.
Before you grant access to anything
The most common setup mistake is opening the app first and thinking later. Three decisions come before any access is granted.
Pick the right plan. An individual plan suits a sole operator; once two or more people share workflows, a Team plan is the right call. Budget roughly $30 to $45 AUD per user per month, and remember GST applies on top of advertised USD pricing.
Decide the working folder. Never grant access to your whole drive. Create one dedicated workspace folder containing only what Cowork needs for the workflows you have agreed.
Agree the first three workflows before opening the app. A tool without a job becomes a toy. Pick three recurring, document-heavy tasks: a weekly client report, invoice follow-up drafting, meeting-pack preparation.
A folder structure that works
Cowork is only as organised as the folder you point it at. A structure that works for most Australian SMBs takes ten minutes to create:
An inbox folder for things that need action, an active folder for current work, and a reference folder for templates, price lists and standing documents.
Client-confidential material stays out of scope until your governance rules are written down. Add it deliberately, folder by folder, not by default.
One project per recurring workflow, each with its own instructions file and only the documents that workflow needs.
A clean scope does two jobs. It keeps output quality high, because the assistant is not guessing which of four price lists is current. And it keeps risk low, because the blast radius of any mistake is one folder, not the whole business.
Plugins, skills and connectors
Plugins bundle ready-made skills and connectors for a business function. Start narrow and expand on evidence.
Install the packs that match your function first: the small business pack covers finance and ops work, the sales pack covers pipeline and outreach.
Connect email and calendar early, with scoped permissions. These two cover the most common workflows: drafting replies, preparing meeting packs, chasing follow-ups.
Hold off on CRM and accounting connectors until the team trusts the review loop. A bad draft email is recoverable; a bad write to your accounting file is a cleanup job.
Custom skills come later, once a workflow has repeated often enough to deserve one. Write down the steps you keep retyping; that document is the skill.
The guardrails that matter
Guardrails are what make the difference between delegation and risk. Four rules cover most of it.
Draft, never send. Anything client-facing gets prepared by Cowork and approved by a human. This single rule removes most of the downside while keeping nearly all of the time savings.
Scheduled tasks need visible failure behaviour. A missed Monday-morning report should be noticed by 9am, not discovered in a month. Build the check into someone's routine.
Mind the Privacy Act. If client personal information sits in scoped folders, your existing obligations follow it. Decide which categories of data may enter the workspace before the first file is copied in.
Write the rules on one page. An unwritten policy is not a policy, and a 40-page one will not be read. One page, shared with the team, reviewed quarterly.
Common first-week mistakes
Granting access to a messy drive and blaming the tool for the mess. Clean the folder first; the assistant amplifies whatever structure it finds.
Automating a workflow nobody has mapped. If you cannot write the steps down for a new hire, Cowork cannot follow them either.
Skipping the review habit, then losing trust at the first error. Review everything in week one, spot-check by week four. Trust is built on evidence, not optimism.
What a sensible first fortnight looks like
Run one workflow with one champion for four weeks, and measure. The numbers do not need to be heroic to be compelling. An operations coordinator in Sydney or Brisbane costs a business around $75,000 a year. If Cowork absorbs five hours a week of document assembly and follow-up drafting per person, that is roughly $9,000 a year of capacity returned for each seat, against licensing of a few hundred dollars. A ten-person Australian firm running three well-chosen workflows is typically looking at $50,000 or more in recovered capacity in the first year.
If you would rather have it stood up properly the first time, our Cowork implementation service sets up the folders, plugins and guardrails in two weeks, and our Claude training gets the team past the prompt-fumbling stage quickly. Not sure your business is ready? Take the readiness assessment or book a short call and we will tell you honestly, including if you can self-serve.
