Quick Answer
Claude Cowork is Anthropic's desktop agent. It reads files in folders you grant it access to, and it can connect directly to Xero. Point it at a Google Drive folder mirrored to your Mac, give it your Xero connector, and it writes a full weekly business report in around five minutes. Pro is £16 a month. Manual reporting costs you two to four hours a week. The maths is plain.
Table of Contents
- Why this stack works for trades
- What you will connect
- Prerequisites
- Step 1: Set up Claude Cowork
- Step 2: Mirror your Google Drive folder
- Step 3: Connect Xero to Claude
- Step 4: Build the weekly report template
- Step 5: Write the agent prompt
- Step 6: Schedule a recurring Monday morning run
- Cost analysis: manual vs automated
- Guardrails: what the agent should never touch
- What business owners are saying
- Recommended videos
- Frequently asked questions
- My verdict
Claude Cowork
Google Drive
XeroWhy this stack works for trades
I sat down on a Sunday for years putting together the same numbers. Cash position. Top five overdue invoices. Last week's revenue against the same week last year. A rough P&L. Then a few lines for the team on Monday morning so we all knew where we stood.
It is the same job every Sunday. The numbers move. The shape does not. That is exactly the kind of work an agent can do, and Claude Cowork is the first one that does it properly. It reads files on your machine. It writes files to your machine. It has a live Xero connector built by Xero and Anthropic together, so it can pull cash position, invoices, contacts, and P&L data straight into the report.
And because Google Drive syncs your files to a local folder, you can mirror the same report back to your Drive automatically. Your accountant sees it. Your operations manager sees it. Your van team gets the Monday morning headlines on their phones. Zero copy and paste.
If you already use Xero, the marginal cost of adding this is £16 a month for Claude Pro. The payback is one Sunday evening of your time. I do not know many trades business owners who would not take that trade.
What you will connect
The full stack is three things. Claude Cowork is the agent itself, the desktop app from Anthropic that has file system access and connectors. Google Drive for desktop is the bit most people miss. It mirrors a folder of your Drive to your Mac so Claude can read and write it like any local folder. And Xero is your accounting truth. The official connector lets Claude query your books in real time within the chat session.
You are not building a workflow in Make.com or n8n here. There is no JSON to maintain, no node graph to debug. The agent is the workflow. You describe the report you want, the agent does the work, you sign it off.
For context on how this fits into a broader automation stack, our guide on BigChange + Xero job costing automation covers what classical workflow tools still do best.
Prerequisites
Before you start, get these in order.
- A Mac. Cowork is macOS first at time of writing. Windows is on the roadmap.
- Claude Pro at £16 a month, or Team at £80 per seat per month if you have five plus seats. Pro is enough to start.
- Xero subscription on any current plan. The connector works for all UK Xero customers.
- Google Workspace or a personal Google account with Drive.
- Google Drive for desktop installed and signed in.
- An hour for the first setup. Five minutes a week after that.
One thing to confirm before going further. The Xero connector is a chat-side integration. It is not Cowork specific. You sign in to Xero from inside Claude.ai, and from then on Claude can query your books in any chat or Cowork task. That is important because it means your data goes through Anthropic's session-only handling, not through any third-party MCP server. Xero confirmed proprietary business data is not used to train Claude.
Step 1: Set up Claude Cowork
Open Claude.ai and switch on Cowork from the left rail. The first run will prompt you to grant access to a working folder. This is the folder Claude can read, create, and modify files inside. Anything outside it is invisible to the agent.
Make a fresh folder for the weekly report work. I called mine WeeklyReports. Drop it directly inside your Google Drive folder so it syncs automatically, and grant Cowork access to it. Cowork remembers the permission for next time.
If you have used Claude before for general chat, Cowork feels different. The agent breaks a task into sub-tasks, shows you each one as it runs, and writes finished files to disk. You can interrupt at any point. You can also ask it to explain its reasoning before it touches anything.
Set the working folder, confirm the permission, and quit Cowork. You will not need it again until step five.
Step 2: Mirror your Google Drive folder
Google Drive has two modes on desktop. Streaming and mirroring. They look identical in Finder but they behave very differently with Claude Cowork.
Streaming holds the file in the cloud and downloads it on demand. Mirroring keeps a full copy on your disk. Cowork can only reliably work with mirrored files. Streaming files often appear empty to the agent because the local copy is a placeholder.
You only need to mirror the folders Cowork will touch. Mirror your WeeklyReports folder. Mirror any data exports you might want the agent to read. Leave the rest on streaming so you do not eat up disk space.
One small detail. Cowork cannot edit native Google Docs files. It works with .docx, .txt, .md, .xlsx, .csv, .pdf, and code files. If you want the report written into a Google Doc, the agent will create a .docx, and Drive converts it to a Doc when you open it. That is fine for our purposes.
Step 3: Connect Xero to Claude
This is the integration Xero and Anthropic announced together in March 2026. Inside Claude.ai go to Settings, then Connected apps. Find Xero in the directory and click Connect.
You will be redirected to Xero to authorise the connection and pick the organisation you want Claude to see. If you have multiple Xero tenants, pick the trading entity. The connector will then have read access to your contacts, invoices, bills, P&L, balance sheet, and cash position.
The connector is read first. Claude can pull data but cannot post invoices or change ledgers. That is the right default. You do not want an agent posting journals on a Sunday night without supervision.
Test the connection by asking Claude a simple question. "What is my cash position today?" or "Show me the top five overdue invoices." The numbers should come back in seconds. If they do not, disconnect and reconnect, and double check you authorised the correct organisation.
For the wider picture on how Xero connects to trades software, see our breakdown of the Payaca, Xero, and Stripe payment pipeline for renewables installers.
Step 4: Build the weekly report template
The agent works best when you give it a template to fill. Do not ask Claude to invent the format from scratch every week. The structure should be yours, locked in, and the numbers should change.
Create a file in your WeeklyReports folder called template.md. Mine looks like this:
| Section | What goes in it |
|---|---|
| Headline numbers | Cash in bank, this week's revenue, this week's costs, net margin |
| Comparison | Same numbers vs last week, vs same week last year |
| Overdue invoices | Top five oldest outstanding, total £, days overdue |
| New jobs in | Quotes accepted this week, lead source if known |
| Cash forecast | Next four weeks, expected in, expected out |
| Owner notes | Blank box for me to add anything not in the numbers |
| Team digest | Three lines for the Monday morning toolbox talk |
Save the template. It now lives in Drive, so any change you make is versioned automatically. If you want to add a customer concentration section, or a labour utilisation line, edit the template once. The agent picks up the change next run.
For a deeper look at what a proper monthly pack should contain, our Claude Cowork monthly management accounts walkthrough goes further into commentary and variance analysis.
Step 5: Write the agent prompt
This is where most people get it wrong. They open Cowork and type "give me a weekly report". The agent does its best, the output is generic, and they decide the tool does not work.
The right prompt is specific, scoped, and grounded. It tells Claude exactly what to read, what to query, what to write, and where. Here is the one I use, anonymised.
Task: Write this week's business report for Elite Heating & Plumbing Ltd.
1. Read template.md from the working folder.
2. Use the Xero connector to pull, for the company organisation:
- Cash position as of today across all bank accounts.
- Revenue and direct costs for the last seven days and the same seven days one week ago and one year ago.
- The five oldest overdue invoices by days, with customer name, £ amount, days overdue, and invoice reference.
- Quotes accepted this week by total £ value.
- An estimate of net cash position for the next twenty eight days based on confirmed in and out.
3. Fill the template structure with these numbers. Write British English. No em dashes. No filler. Currency in £.
4. Add a three line team digest in plain language for a toolbox talk.
5. Save the report as report-{YYYY-MM-DD}.docx in the working folder, where the date is the Monday of the current week.
6. Do not modify template.md. Do not delete anything. Do not query Xero for anything else.
That prompt is around 200 words. It is reusable. You save it as a Project in Claude, or as a saved task in Cowork, and run it on demand. The first time it runs, watch it work. Cowork shows each sub-task in sequence. If the Xero pull fails, you will see it. If the file write fails, you will see it.
The output is a Word document in your working folder, which Drive syncs to the cloud, which means it is in your accountant's shared folder by the time you finish your coffee.
Step 6: Schedule a recurring Monday morning run
Cowork supports scheduled tasks. You can tell it to run the same prompt every Monday at 06:00. The agent fires, generates the report, and the document is in Drive before anyone is awake.
I prefer 06:30 on a Monday. By 07:00 I have a draft on my phone in the van, by 07:30 the team has the digest on WhatsApp, and the Monday morning toolbox talk starts with numbers, not vibes.
If your Mac is normally asleep at 06:30, set System Settings, Battery, Schedule, Wake every Monday at 06:25. The agent gets five minutes to warm up. It runs. It saves. The Mac goes back to sleep.
Cost analysis: manual vs automated
I will keep this short and honest.
| Method | Time per week | Annual time | Annual cost at £30 owner hourly value |
|---|---|---|---|
| Manual collation in Excel | 2 to 4 hours | 104 to 208 hours | £3,120 to £6,240 |
| Claude Cowork plus Xero plus Drive | 5 to 10 minutes | 4 to 9 hours | £120 to £270 |
| Net saving | 2 to 4 hours | ~ 100 to 200 hours | £2,850 to £5,970 |
Claude Pro is £192 a year. Xero is your existing line. Google Workspace, if you pay for it, is a separate line you already have. The net of the Pro subscription is at least £2,650 of recovered owner time. For a five plus head business owner that is a low estimate. For some it is closer to a full working week per year.
Guardrails: what the agent should never touch
An agent with file system access is powerful and a little dangerous. Three rules I run by, all of them learned from people who got bitten.
One. Cowork only ever sees a single folder. Never your home directory, never your Documents folder, never your full Drive. One folder, one task, one purpose. If you want it to do something different, give it a different folder.
Two. Never put irreplaceable files in a Cowork folder. The template.md, yes. The output reports, yes. Your only copy of the company tax returns, no. The Drive sync gives you version history, but the principle still stands.
Three. The Xero connector is read first. Keep it that way. Posting transactions through an agent is a discussion for another article and a different governance conversation.
For more on the broader compliance picture when AI touches financial data, our Fergus, Xero, and n8n CIS auto-categorisation guide covers the audit trail concerns.
What business owners are saying
Recommended videos
FULL Claude Cowork Tutorial For Beginners in 2026 (Zero to PRO)
Comprehensive beginner walkthrough of Claude Cowork from scratch.
How to Use Claude Cowork – Full Workflow Automation Guide 2026
Workflow setup walkthrough covering file access, scheduling, and prompts.
Setup the Xero MCP Server with Claude & Open AI Agents
Technical walkthrough of how Xero's MCP integration connects to Claude.
Accounting, Reimagined using Xero MCP
A look at how the Xero MCP server lets AI tools query books directly.
Connect Xero to Claude in 90 Seconds
Short demo of the official Xero connector authorisation flow.
How I Use Claude to Automate Tax and Bookkeeping
Practical, beginner-friendly walkthrough of AI bookkeeping prompts.
Frequently asked questions
Pro is enough for a weekly report. Max is for users running multiple long Cowork tasks every day. If you find yourself running ten Cowork tasks in a row and hitting the daily limit, then upgrade. Most trades business owners will not.
Cowork is macOS only at time of writing. Windows is on the public roadmap. If you are Windows only, the Xero connector still works inside Claude.ai for ad hoc queries. You just lose the scheduled file output side.
Xero and Anthropic confirmed financial data exchanged between the two platforms is used solely within the active session and proprietary business data is not used to train Claude. The data is in flight, not stored or trained on. Treat it the same way you treat any cloud accounting access.
The default connector is read first. You can grant write scopes through the official MCP server if you want the agent to create draft invoices or contacts, but I would not. The whole point of this stack is the agent collates, you sign off, and Xero remains the single source of truth.
The numbers in the report come from Xero, not from Claude's reasoning. The agent pulls and formats. If the Xero figure is wrong, that is a books problem, not an AI problem. Spot check the headline cash and revenue numbers for the first month, build trust, then trust the workflow.
An hour the first time. Twenty minutes installing and authorising. Twenty minutes writing the template. Twenty minutes refining the prompt. After that it is five minutes to review on a Monday morning.
The task will not fire. Either set a wake schedule in System Settings, Battery, Schedule, or run the task manually on a Monday morning. The manual run is one click.
Yes. Because the output lives in your Google Drive folder, you share that folder with your accountant once and they have ongoing access. The Monday morning report appears in their Drive too. No emailing, no version chaos.
My verdict
For £16 a month you get a Sunday evening back, your team gets numbers on a Monday morning, and your accountant gets a current pack in their Drive every week. The cost is trivial. The discipline is the harder part. Build the template once, write the prompt once, schedule the run once, and the workflow looks after itself. After three months of running it, the bigger question is not whether you can afford to add this. It is what you do with the time you get back.
