You installed Claude Cowork, connected a folder, ran your first task, and something didn't work. Before you decide the tool isn't ready, it helps to know that nearly every problem new users report in their first month falls into one of ten buckets, and none of them takes more than a few minutes to fix. We set up Cowork for Australian businesses ranging from two-person bookkeeping practices to fifty-seat professional services firms, and the same ten issues surface almost every time.
Here they are, roughly in the order people hit them.
Access problems: when Claude can't see what you see
1. Claude says it can't find your files
Cowork only sees folders you have explicitly connected. It does not roam your hard drive. If Claude reports that a file doesn't exist while you're staring at it in Explorer, the folder it lives in probably isn't connected to the session. The fix is to click the folder selector and choose the directory where the work actually lives. Pick the project folder rather than your entire Documents library: a tighter scope means faster searches and less chance of Claude touching something it shouldn't.
2. The file exists but every read fails
This one catches OneDrive and Google Drive users constantly, which in practice means most Australian offices on Microsoft 365. Files-on-demand keeps a placeholder on your disk and the real content in the cloud, so a shell command sees a stub and errors out. Claude's own file tools trigger the download automatically, so the fix is often just letting Claude retry with a different tool. For folders you work in daily, right-click them in OneDrive and choose 'Always keep on this device'.
3. A connector keeps demanding authorisation
Connectors to Xero, Gmail, Notion or your CRM each carry their own OAuth grant. Until you approve one, every request that needs it will stall. Authorise connectors once through your settings, and note that on Team and Enterprise plans an admin may need to approve the scopes first. If a connector worked last week and fails today, the token has usually expired. Re-authorising takes under a minute.
Working-style problems: an agent is not a search box
4. Vague requests produce vague work
'Write something about our services' gets you generic filler. 'Draft a one-page summary of our conveyancing services for first home buyers in Brisbane, plain English, ready to attach to an email' gets you something usable. Cowork behaves like a capable new hire: it does what you ask, so ask precisely. Name the audience, the deliverable, the format and the length. Thirty seconds of extra typing routinely saves two rounds of revision.
5. You expected an instant answer to a twenty-minute job
A question gets answered in seconds. A task like 'reconcile these three spreadsheets and flag the mismatches' involves planning, running code, checking results and writing a report. Watch the task list Cowork shows while it works rather than assuming it has frozen. If a job does stall, say so. Asking for a progress summary usually reveals exactly where it's up to.
6. Everything lands in chat instead of files
New users often get a wall of text where they wanted a document. Say the word 'file' and name the format: 'save this as a Word document in the client folder' or 'give me the figures as a spreadsheet'. Cowork can produce Word, Excel, PowerPoint and PDF deliverables directly into your connected folder, which beats copy-pasting out of a chat window every time.
7. Claude remembers something that's no longer true
Cowork keeps memory between sessions, which is mostly a feature: it recalls your entity structure, your clients and your preferences without being told twice. But if your pricing changed or a project was cancelled, stale memory produces confidently wrong output. When you spot it, correct it directly and ask Claude to update its memory. One sentence fixes it permanently.
Guardrail and automation problems
8. Claude drafted the email but won't send it
That's deliberate. Out of the box, Cowork asks before sending messages, publishing content or submitting forms, and a sensible setup keeps it that way: draft freely, send only with approval. For Australian businesses handling client data under the Privacy Act, that checkpoint is worth keeping even after trust builds. Approve each send explicitly rather than hunting for a switch that turns the safeguard off.
9. A skill or plugin didn't trigger
Skills fire on matching phrases, and paraphrases sometimes sail straight past them. If you installed a month-end close skill and asked Claude to 'sort out the June numbers', it may have answered generically instead. Invoke skills by name when it matters, or use the slash command directly. If a skill you expect isn't listed at all, it may not be installed in the session you're working in.
10. A scheduled task ran, but you can't tell what it did
Automated runs are only as good as their reporting. Ask each scheduled task to write a short run log to a file in your project folder, then skim it twice a week. Silent automation fails silently; logged automation tells you the morning something breaks. This habit alone separates teams that trust their setup from teams that quietly stop using it.
The first-week checklist
If you'd rather prevent these problems than fix them, five habits cover most of it:
Connect the specific folder where the real work lives, not your whole drive.
Authorise the two connectors you'll use daily. For most Australian SMBs that's email and accounting.
Write prompts that name the audience, the deliverable and the file format.
Review every outbound draft for the first fortnight before approving a send.
Give every scheduled task a run log, and read it twice a week.
When it's worth getting help
Everything above is fixable on your own, and for a sole trader that's usually the sensible path. The maths changes with a team. Ten staff who each lose two hours a week to a misfiring setup are burning roughly $52,000 a year at average Australian professional wages, against a one-off fixed-fee setup that typically costs $3,500. If Cowork is becoming part of how your business runs rather than an experiment, a structured setup with tested connectors, filing rules and scheduled tasks pays for itself in the first month.
If you'd rather skip the trial and error, book a short call and we'll walk through your setup, what's misfiring and what to automate first.
