Open Claude Cowork for the first time and old habits kick in fast: type a short question, read the answer, type the next short question. That's search behaviour, carried over from twenty years of typing into a box and expecting one clean result back. It works, technically. Cowork will happily answer a one-line question. But treating it that way means most Australian business owners are using a fraction of what the tool can actually do, because Cowork can read your files, hold a multi-step plan, check its own work and ask a clarifying question before it starts, the way a competent new hire would.
The cost of that habit isn't dramatic, it's just invisible. Every time you ask five small questions instead of handing over one properly scoped job, you're doing the assembly work yourself: combining the answers, checking they're consistent, deciding what happens next. That's exactly the layer of work you were trying to get off your plate.
The tell: you're prompting it like a search engine
There's a simple test. If every message you send Claude Cowork is a standalone question with no reference to what came before, and you're the one stitching the answers together into a finished task, you're running it like a lookup tool. If instead you hand over a job with a goal, some context and a few constraints, and Cowork comes back with a finished draft or a completed action, you're delegating. The difference in output is not subtle.
You'll notice it in your own message history. Scroll back through a week of Cowork conversations and look for how often you say "now do this next" versus how often the whole multi-step job was in the first message. If nearly every reply from you is a new instruction reacting to what Cowork just did, you're steering it turn by turn instead of setting it up to run.
Search-style: "What's my highest overdue invoice?" Delegation-style: "Chase every invoice more than 14 days overdue, match the tone to how each client usually responds, and hold anything above $10,000 for me to approve before it sends."
Search-style: "Summarise this contract." Delegation-style: "Read this vendor contract, flag anything that's non-standard for an Australian small business, including auto-renewal, indemnity and IP ownership clauses, and put the three riskiest ones at the top."
Search-style: "Write a LinkedIn post about our new pricing." Delegation-style: "Draft three LinkedIn post options announcing the pricing change, keep them under 150 words each, match the tone of our last five posts, and leave them as drafts, don't publish."
Search-style: "What's our cash position?" Delegation-style: "Pull cash position and the top five overdue receivables from Xero, compare to the same week last month, and flag anything that would affect payroll in the next fortnight."
What a proper brief actually includes
A brief that gets a manager-quality result from Cowork usually has four parts, and skipping any one of them is why the output feels generic.
The outcome, not the task. Not "draft an email" but "get this client to agree to the new payment terms without souring the relationship."
The context it needs and where to find it: which folder, which inbox, which prior conversation, which numbers actually matter.
The constraints: budget, tone, deadline, and what NOT to touch, including sending anything, publishing anything, or handling customer data in a way that would concern the Privacy Act.
The format and the checkpoint: what the finished thing should look like, and where you want to review before anything goes out the door.
Correct the plan, not every sentence
Delegation doesn't mean walking away and hoping for the best. The manager mindset shows up in how you check in too: at the plan level, not the sentence level. When Cowork proposes a plan or drafts something off-target, correct the underlying assumption, for instance "don't include clients who are already on a payment plan," rather than rewriting each line it produces. One correction at that level reshapes everything downstream. Line-editing only ever fixes the one line you touched.
A worked example: chasing invoices for a Sydney bookkeeping client
One of our Cowork setup clients, a 12-person bookkeeping firm in Sydney's CBD, used to have a staff member spend roughly three hours a week manually checking Xero for overdue invoices and writing chase emails one at a time. At $45 an hour loaded cost, that's close to $6,750 a year spent on a task that's almost entirely mechanical, and it was always the first thing to slip when the team got busy with actual client work.
The fix wasn't a smarter one-line prompt. It was a standing brief: check overdue receivables every Monday morning, draft, never send, a chase email per client using the tone that's worked for that client historically, flag anyone over $10,000 or 60 days overdue for a phone call instead of an email, and drop the whole batch into a folder by 9am for a two-minute human review before anything goes out. Same tool, same task, roughly four times the throughput, because the job was framed as a brief with rules rather than a question with one answer.
Within the first month the firm's principal reported the invoice-chasing line item had effectively disappeared from her Monday morning, replaced by a five-minute skim of drafts before her assistant sent them.
Guardrails that keep delegation safe, not risky
The reason this works without turning into a liability is that the brief does the fencing for you. Draft, never send. Flag anything above a dollar threshold. Never touch account settings, payment details, or anyone's access permissions. Once guardrails like these are written into the standing instructions, delegating bigger chunks of work stops being a leap of faith and starts being routine, the same way you'd trust a new office manager with the diary and the inbox before you'd hand them the company credit card.
It also means the guardrails only need to be written once. A good standing brief for invoice chasing, lead follow-up, or weekly reporting keeps working every week without you re-explaining the constraints each time, which is the actual point of delegating in the first place.
If your team is still treating Claude Cowork like a search box, the fastest fix isn't a prompting course, it's writing three or four standing briefs for the tasks that eat the most admin time each week. We set this up for Australian small businesses as part of our Cowork setup service, or if you'd rather talk through what to delegate first, book a short call.
