Blog

Claude Cowork Demo Script: What We Show Australian SMBs First

July 2026 · 6 min read · AI Strategy

A laptop screen with a play button producing a finished document, drawn in notebook style
← Back to all posts

Most software demos lose the room in the first ninety seconds. The business owner is watching for one thing: does this touch work I actually do, or is it another dashboard I will never open again? When we demo Claude Cowork to a Sydney accounting firm or a Brisbane trades business, we throw out the polished feature tour and run a script built around their real Monday-morning admin. This is that script, close to word for word, with the reasoning behind each choice.

Cowork is the desktop side of Claude, the assistant built by Anthropic, that can read the files on someone's computer, run tasks in a private sandbox, and hand back finished documents. That sentence means nothing to a business owner until they watch it do their filing. So we do not describe it. We point it at the kind of folder they already have and let them watch.

The first five minutes carry the whole meeting

A busy owner gives a new tool about five minutes of real attention before deciding whether the rest of the call is worth it. We spend those minutes on proof, not promises. Nothing in the opening is hypothetical, and nothing depends on a connector we have not already set up. The goal is a single undeniable moment where the owner leans in and says: do that again, but with my numbers.

To get there we prepare almost nothing in advance. A staged demo with tidy sample data is the fastest way to lose an experienced Australian buyer, because they have sat through dozens of vendor pitches and can smell a rehearsed happy path. Real mess is more convincing than any slide.

The script, step by step

Open with a folder they recognise

We ask the prospect to pick a folder they find mildly painful. A quarter of receipts. A pile of quote PDFs. Sixty client photos with useless file names. We point Claude at it and ask a plain-English question: what is in here, and what is missing? In about twenty seconds it reads the folder and answers in their words, not ours. That is usually the first time the room goes quiet.

Run one real task from start to finish

Then we do one complete job, not five half-jobs. A favourite for accounting and bookkeeping firms: take a folder of supplier invoices and produce a clean spreadsheet with vendor, date, amount, and GST, flagging anything that does not add up. For a trades business we turn six site photos and a voice note into a formatted quote. The task finishes on screen, as a file they can open, in the time it takes to explain what it did.

Four things we make sure the owner actually sees during that task:

  • The input is their own messy data, not a tidy sample we prepared earlier.

  • The output is a real file, an Excel sheet or a Word quote or a PDF, saved to a folder, not a chat message they have to copy out by hand.

  • Claude shows its working and asks before anything destructive, so nothing gets deleted, sent, or overwritten without a clear yes.

  • The whole job runs on their own machine, so sensitive client data never has to leave the building.

Put a number on the minute we just saved

Owners do not buy speed. They buy hours back. So we close the task by doing the maths out loud. If reconciling one supplier statement takes a bookkeeper twenty-five minutes, and the firm does forty a month, that is roughly seventeen hours a month gone. At a loaded rate of $65 an hour, that is about $1,100 a month, or a little over $13,000 a year, on one task alone. We write that figure on the whiteboard and let it sit there while we talk.

The number matters more than the magic. A demo that produces awe but no arithmetic gets a warm reaction and no purchase order. A demo that ends with a believable annual saving gets a second meeting.

What we deliberately leave out

A good demo is defined by what it refuses to show. We do not open with agents, MCP servers, or the API. We do not promise Claude will run the whole business. And we never claim it is error-free. Naming the limits early buys more trust than any feature: Claude gets things wrong sometimes, it works best on well-scoped tasks, and a person still needs to check the output before it goes to a client.

We keep compliance concrete rather than vague, too. If the firm handles personal information under the Privacy Act, or works with a financial services client worried about its ASIC obligations, we show exactly where the data sits and who can see it. For most Australian SMBs the honest answer is reassuring: the files stay local, and anything that reaches the internet can be switched off.

Turning a demo into a decision

The last five minutes matter as much as the first. We do not ask what did you think. We ask which task on your desk this week should we point this at. That question moves the conversation from entertainment to a pilot. If they can name the task, we scope a fixed-price setup on the spot. If they cannot, the tool is not the problem, and we would both rather learn that now than after an invoice.

The pattern underneath all of this is plain: show real work on real data, put a dollar figure on it, and be honest about the edges. That is the demo that earns a second meeting with an Australian small business. If you would like to see the Claude Cowork setup run against your own files, you can book a short session with our team and we will build the script around your Monday admin.

Ready to move from AI pilot to production?

We help mid-market Australian businesses deploy AI automations that actually reach production and deliver measurable ROI.