AI for Tradies: What Actually Works (and What's a Waste)

Every time I search "AI for tradies" I get the same thing. A landing page with a stock photo of a bloke in hi-vis looking thoughtfully at a tablet, a pricing table starting at $149 a month, and absolutely no explanation of what the thing actually does. It's a prompt in a trench coat.

So this is the other article. The one that tells you what to set up, in what order, and what it'll cost you (spoiler: about twenty US dollars a month plus an afternoon of your time). I'm assuming you can already open Claude or ChatGPT and type a question into it. I'm not going to explain what a chatbot is. What I am going to explain is how to wire one into your actual email, your actual calendar, and your actual pricing, so it stops being a party trick and starts being useful.

One thing I'm deliberately leaving out: AI answering your phone. It's probably the single biggest win available to a trade business, because a missed call is a lost job and voicemail has been losing you jobs for years. But it's also a genuinely deep topic (number porting, voice quality, transcripts, privacy, what happens when it mishears an address) and cramming it in here would do it a disservice. It's getting its own article. Come back for that one.

Quick note: why Claude, and what if you use something else

Almost everything below is written using Claude, because that's what I use every day and I'd rather show you something I actually run than something I've read about. It's made by Anthropic, it costs about twenty US dollars a month for the paid tier, and it's the one I'd hand to a tradie who wants results this week rather than a hobby.

But this is not a Claude advertisement, and you are not stuck.

ChatGPT (OpenAI) does the same job. So, increasingly, do Gemini (Google) and Grok (xAI). They all now have some version of the same three ingredients: a chat window, a way to connect your email and calendar, and an "agent" mode that can go off and do multi-step work while you get on with your day. The names differ, the menus are in different places, the monthly limits are carved up differently. The shape is the same.

So when I say "switch on Cowork and schedule a task", the ChatGPT equivalent is Work, which lives inside the Codex app. When I say "connect the Gmail connector", every one of these has connectors, they just call them different things and hide them in a different corner of the menu. If you're already paying for one of them, use that one. Switching tools to follow a blog post is a waste of a perfectly good subscription.

What matters far more than which brand you pick is the two things in the next couple of sections: the safety rule, and loading the thing with your actual business information. Get those right and the logo on the app is a detail.

The one rule that makes all of this safe

Before any of the fun stuff, this.

AI drafts. You send.

That's it. That's the rule. Never give an agent the power to send, pay, or delete on a real account without you looking at it first.

Here's why, and it's not hand-wringing. Security researchers call it the lethal trifecta: an agent that can (1) read your private data, (2) is exposed to untrusted content from the outside world, and (3) can send data back out. Your inbox has all three. Prompt injection sits at number one on the OWASP Top 10 for LLMs, and it is not a solved problem. It's not a bug waiting for a patch.

Concretely: someone emails you. Buried in the footer, in white text, is an instruction. Your helpful agent reads the inbox, reads the instruction, and cheerfully forwards your customer list to a stranger, or pays an invoice that doesn't exist. It thinks it's helping. It is, technically, following instructions.

This is the reason Anthropic's Gmail connector can only create drafts and cannot press send. People complain about that. It's not a limitation, it's the safety rail. I've written before about what happens when you hand an agent too much rope, and about building an approval gate so a human stays in the loop.

Four rules, stick them on the wall:

Nothing sends, pays, or deletes without a human clicking the button.
Use a dedicated account with the minimum permissions, not your admin login.
No number reaches a customer unchecked. Not one.
If a tool needs full write access to be useful, that's a reason to be suspicious, not a reason to grant it.

Right. Now the good bit.

Setting up the foundation

Two steps. Neither is hard, and the second one is the one everybody skips.

Connect Gmail, Calendar and Drive

In Claude, go to Settings, then Connectors, and toggle on Gmail, Google Calendar and Google Drive. Sign in with Google, approve the scopes, done. If you're on a Team plan, an Owner has to enable connectors first, and if you run Google Workspace your admin might need to mark Claude as a trusted app under Security, then API controls. Give it fifteen minutes to propagate before you assume it's broken. (I did not give it fifteen minutes. I assumed it was broken.)

Microsoft 365 works the same way if that's your world. Same principles apply throughout.

Three gotchas worth knowing before you start:

Gmail is draft-only. Claude reads and composes. You send. See above.
Calendar is full read and write. This one genuinely works end to end, which is why the calendar workflows below are the most satisfying.
Attachments are metadata only. Claude sees that a PDF exists, not what's in it. If the quote is in the attachment, you'll need to hand it over yourself.

And do this properly: create a dedicated account, something like ai@yourbiz.com.au, and connect that. Not the login that owns everything. It costs you nothing and it means the blast radius of a bad day is small.

Build the project brain

This is the highest-leverage hour you will spend, and almost nobody does it. So let me slow down here, because if you skip this section the rest of the article is a toy.

What a Project actually is. In Claude, a Project is a folder that holds three things: a set of standing instructions, a pile of documents it can read (the "project knowledge"), and all the chats you've had inside it. Every conversation you start inside that Project automatically sees the instructions and the documents. You don't re-explain your business every morning. It's already there.

ChatGPT has the same concept and calls them Projects too. Gemini has Gems. Same idea, different noun.

Why it matters more than the model. A generic chatbot does not know your call-out fee. Ask it to write a quote and it will invent a number that looks plausible, because inventing plausible things is precisely what these things do. It is not lying to you. It genuinely has no idea, and it has been trained to be helpful, so it produces something helpful-shaped. This is the single biggest reason people try AI for a week and conclude it's rubbish. They asked a stranger to quote a job.

Context is the whole ballgame. A mediocre model with your real prices beats a brilliant model guessing, every single time.

Step one: create the Project and write the instructions. The instructions are the standing brief. Not a prompt, more like the induction you'd give a new office junior. Mine for a trades business would read something like:

You work for [Business], a residential electrical contractor on Sydney's Upper North Shore. Everything you write goes to Australian customers, so use Australian spelling and dollars, and always show GST. You draft, you never send. Never invent a price: if a price isn't in the knowledge files, say "PRICE NEEDED" and stop. Quotes always include our standard exclusions and the 12 month warranty wording. Keep the tone plain and friendly, no corporate waffle. If a job is outside our service area, say so instead of quoting it.

Note what that's doing. It sets the geography, the currency, the tone, the hard rule about sending, and (this is the important one) it gives the model a way to fail loudly instead of guessing. "Say PRICE NEEDED and stop" is worth more than any clever phrasing.

Step two: upload the knowledge. Drag the documents in. Realistically:

Rate card: hourly rates, call-out fee, after-hours and weekend loading
Materials price list, exported from your supplier or your accounting software
Standard inclusions and exclusions
Terms and conditions, warranty wording, payment terms
Service area, listed as actual suburbs
Licence numbers and whatever compliance boilerplate you paste into everything
A description of how you actually run a job, start to finish
Two or three of your best past quotes, as examples of the format you want

That last one does a surprising amount of work. Showing beats telling. Give it three real quotes and it will match your style far better than any adjective you could have written into the instructions.

Step three: keep it current, and keep it clean. Two rules I'd tattoo on this:

Point at live files, not dead copies. Rather than uploading a pricing PDF that goes stale, keep the price list in a Google Sheet in the Drive folder the Project can read. Copper goes up, you update one cell, and every quote from that moment on is right. Uploaded files are snapshots. Connected files are current.

Less, but better. There's a real temptation to shovel in every document you own on the theory that more context is better. It isn't. A Project stuffed with six versions of the rate card, two of which are from 2023, will confidently use the wrong one. Every document you add is a document the model might believe. Prune it like you'd prune a toolbox: if you wouldn't hand it to a new employee on day one, it doesn't go in.

A word on memory. Claude also has a memory feature that carries details across conversations, and it's genuinely handy for the small stuff (it'll remember you're in Sydney, that you hate exclamation marks). But do not rely on memory for your prices. Memory is a nice-to-have that gets recalled loosely. Project knowledge is a document it reads. For anything where being wrong costs you money, use the document.

If you want to go deeper on writing the instructions themselves, I've got a whole piece on prompt structure.

Do this properly and everything below stops being a demo and starts being a system.

Scheduled tasks, or: getting it to do things while you're up a ladder

Everything so far assumes you're sitting there typing. The step up is telling it to run on its own.

That's what Cowork is for. It isn't a separate app or a separate tab, it's a button right there in the chat box. You flick it on, and the same conversation you were already having gains two abilities: it can work with files on your machine, and it can run on a schedule instead of only when you're sitting there.

Setting one up is genuinely just: turn on Cowork, describe the task in plain English the way you would to a person, check it does the thing correctly when you run it by hand, and then set it to repeat. Daily at 6am. Every Friday at 4pm. Whatever suits.

Two bits of advice that will save you a fortnight of annoyance:

Always run it manually first. Twice. Watch what it does. A scheduled task that quietly does the wrong thing every morning at six is worse than no task at all, because you'll trust it.

Watch your usage. Scheduled tasks and Cowork sessions eat a plan's allowance much faster than chatting does. A task that runs hourly because it felt clever at the time will find your limit for you.

ChatGPT has scheduled tasks too, and if you'd rather run this stuff on your own hardware without a subscription in the loop, that's what tools like n8n and Hermes are for. More on those later.

The four workflows worth building first

1. The morning briefing

This is the one to build first, because it's useful on day one and it can't hurt anybody.

What it does: at 6am it reads overnight email, sorts it, drafts replies to the easy ones, and tells you what actually needs you. By the time you're in the ute with a coffee, you've got a list instead of an inbox.

How to set it up: turn on Cowork in the chat box, make sure the Gmail and Calendar connectors are on, and create a task with a prompt along these lines:

Every weekday at 6am, read all email received since 5pm yesterday.

Sort it into four groups: (1) new job enquiries, (2) customers replying about a quote, (3) suppliers and admin, (4) junk I can ignore.

For every new enquiry, pull out: name, suburb, phone number, what they want done, and any date they mentioned. Flag anything that sounds like an emergency at the top.

Then check my calendar for today and tomorrow and tell me what I've already got on.

Draft replies in Gmail for anything routine (acknowledging an enquiry, confirming an appointment). Leave them in drafts. Do not send anything.

Finish with a short list: "needs Thomas", for anything you couldn't handle or weren't sure about.

Keep the whole thing under a page. I'm reading it on a phone.

Then set it to run weekdays at 6am and go to bed.

Where it breaks: it will get urgency wrong. It will confidently file a burst pipe under "admin" because the customer was polite about it. It's a briefing, not an autopilot. Read it, don't obey it.

2. Enquiry to quote to calendar

This is the one that made me sit up, because the calendar half genuinely works without a human in the middle.

What it does: an enquiry lands. Claude pulls out the name, address and job type, checks your actual calendar for actual free slots, drafts a quote using your actual pricing from the Project knowledge, and puts a tentative hold in the diary. You read it, fix the bit it got wrong, and hit send.

The free-slot check is the part that surprises people. Because Calendar is read and write, "can you do Thursday morning?" gets a real answer instead of a hallucinated one. It looks at the diary. It knows you're already in Hornsby at nine.

How to set it up. Do this one inside your Project (so it has the prices) rather than as a blind scheduled task, at least until you trust it. When an enquiry comes in, you type something as lazy as "handle the Henderson email" and it goes. The standing instruction that makes that work looks like this, and it lives in your Project instructions:

When I ask you to handle an enquiry:

1. Find the email and pull out: name, address, phone, what they want, and any dates or times they mentioned.

2. Check my Google Calendar for the next 10 working days. Find slots that fit the job length, respecting travel: don't offer me a 9am in Berowra if I'm booked in Chatswood at 8.

3. Draft the quote using ONLY the rates and materials in the project files. If something isn't priced there, write PRICE NEEDED in the line item and tell me. Do not estimate.

4. Create a tentative calendar event, title it "TENTATIVE: [name] [suburb]", and put the customer's phone and the job description in the notes.

5. Draft the reply email in Gmail: thank them, summarise the job so they know we understood it, give the quote, offer two of the calendar slots, include our standard exclusions and warranty. Leave it in drafts.

6. Tell me in chat what you did, what you weren't sure about, and anything you had to guess.

Step 6 is the one people leave out and it's the most valuable line in there. You want it confessing.

Where it breaks, and this is not optional reading. The quote sits in drafts. Always. If you want true automatic sending you need an automation layer like n8n underneath, and even then I'd put a gate on it.

Here's why. AI is very good at producing a quote that looks right. The layout is beautiful. The line items are professional. The wording is better than yours. And the measurement is wrong by a factor of two and it has no idea, because being wrong feels exactly the same to it as being right.

The AI takeoff tools that read plans and photos run about 2 to 4 percent variance from a manual takeoff on clean residential drawings, and 8 to 12 percent on messy commercial sets. Which sounds survivable, until you notice individual line items can be wildly out even when the total lands close, because the errors cancel each other out. Great for the average. Terrible for the one job you actually quoted.

Draft, check, send. Every time. If you only take one thing from this article, take that.

3. Invoices and the boring money stuff

Start with receipt capture, because it's the least glamorous and the most reliable. Dext, Hubdoc, or MYOB's built-in capture, whichever your accountant already uses. Photograph the receipt in the merchant car park, it extracts the supplier, the ABN, the GST and the total, and files it against the right account. This is the most boringly dependable AI in the entire stack. It also doubles as your compliance fix, because the ATO wants your records kept for five years and a shoebox of faded thermal paper is not a system, it's a hope.

Then use the AI that's already inside your accounting software. Xero's Just Ask Xero (JAX) will draft invoices, chase payments, and predict when a given customer is actually likely to pay you (which is a different question from when they said they would). QuickBooks has a similar squad of agents, including one that pre-checks your GST against your P&L before you lodge. You're already paying for these. Turn them on.

Then wire your books into Claude. Xero ships an official MCP server, which in plain English means Claude can query your accounting data directly. Once that's connected, a Friday afternoon scheduled task earns its keep:

Every Friday at 4pm, check Xero for:

1. Invoices more than 14 days overdue. For each one, tell me the customer, the amount, how many days late, and whether I've already chased them.

2. Any completed jobs from this week that I haven't invoiced yet. Cross-check against my calendar.

3. Draft a polite chase-up email for each overdue invoice. Firm but not rude, we want to keep these people. Leave them in drafts.

Give me the total outstanding at the top so I know how bad it is before I read the detail.

Point 2 is the sleeper. Most small operators aren't losing money to bad debts, they're losing it to jobs they simply forgot to invoice. Having something cross-reference "went there" against "billed for it" once a week is a genuinely profitable ten minutes.

The limit. Treat a BAS as a draft, never a lodgement. These tools are good at flagging discrepancies and terrible at understanding your specific situation. GST-free items, capital purchases, private use apportionment: a general-purpose model will be fluent and confident and wrong. Your bookkeeper's name goes on the form, not Claude's.

4. Site notes and photos, without typing anything

You asked for this one and it's my favourite, because it's the gap nobody fills.

The simple version: the Claude mobile app takes voice input. Sit in the ute after a job and ramble at it. "Right, Henderson job, Wahroonga, the switchboard is older than I am, needs a full replacement, I've quoted around fourteen hundred, they want it done before the twentieth, also the bloke has a dog that hates me." Ask for a structured job note. Get one back. Done before you've reversed out of the driveway.

The better version: a phone shortcut (iOS Shortcuts, or Tasker on Android) that dumps voice memos and site photos into a dated Google Drive folder. One tap. Then at the end of the day, Claude reads the folder via the Drive connector and turns the whole mess into job records, a materials list for the merchant run, and tomorrow's follow-ups.

One warning here, because I don't want you building this and getting cross with me. Claude's Drive connector reads Docs and Sheets well. Audio files, it does not. Do not drop an .m4a into Drive and expect Claude to listen to it. Transcribe first: use your phone's built-in dictation, or run Whisper locally (my Mac Mini M1 does this happily and nothing leaves the house, which is a nice bonus if the recording mentions a client's name). Text into Drive, then Claude.

And if you're already on ServiceM8, check what you've got before you build anything. Its dictation writes straight to the job card, and you're paying for it.

Claude Code is not just for code (and that's the interesting part)

The name is doing this tool a disservice.

Claude Code is a terminal application. You point it at a folder on your computer and it can read, write, move, rename and reorganise everything in there, run commands, and work through a long list of tasks without you babysitting each step. That is obviously useful for code. It is also, and almost nobody talks about this, extremely useful for files. Which is what a small business actually drowns in.

Things I've watched it do that have nothing to do with programming:

Take a folder of 400 job photos with names like IMG_4471.jpeg and rename and sort them into folders by date and job number.
Read a directory of eighty PDF invoices from suppliers, pull out the date, supplier, total and GST from each, and produce a single spreadsheet.
Take a decade of scattered documents and reorganise them into a filing structure that a human could actually navigate.
Turn a folder of messy site notes into a properly formatted report, with headings, in Word.
Compare this year's price list to last year's and tell me exactly what moved and by how much.

That's the pitch: it's a very fast, very literal assistant that can touch every file on your machine. If your admin problem is fundamentally "there are too many files and they're a mess", this is the tool, and it's the one that'll surprise you.

Now the honest part, because there's a catch and it's a real one.

This is meaningfully harder than everything else in this article. It lives in a terminal, which means a black window and typed commands. There's no undo button. When it renames four hundred files it has renamed four hundred files, and if it misunderstood you, it misunderstood you four hundred times, quickly and efficiently.

So if you go here:

Work on a copy. Always. Copy the folder, let it loose on the copy, check the result, then swap. This is not paranoia, it's just what you do.
Use version control or at least a backup before any bulk operation. Time Machine counts.
Do not turn off the permission prompts. There's a flag that skips all the "can I do this?" confirmations, and it is enormously tempting, and I've written about why that's a bad idea at some length. Short version: the confirmations are the only thing standing between an ambiguous instruction and a very bad afternoon.
Watch the meter. Agents can get stuck in fix-loops, cheerfully burning tokens trying the same broken thing in slightly different ways. Type /cost occasionally. Ask me how I know.

And on the actual coding side: yes, you can now build small internal tools that used to require hiring someone like me. A pricing calculator. A script that reformats quotes onto your letterhead. A little dashboard of unpaid jobs. Genuinely, this works.

Good candidates: internal, not sensitive, low stakes, and honestly you'd have bodged it in a spreadsheet anyway.

Bad candidates: anything touching customer personal data, anything touching payments, anything a customer sees. Not because the AI can't write it. It can, and it'll work fine on Tuesday. The problem arrives six months later when a dependency updates and it silently breaks, and fixing it requires precisely the skill you were avoiding by using AI in the first place. Building is the easy half. Owning it forever is the other half, and nobody mentions that in the demo video.

The alternatives, honestly

I've written this around Claude because it's what I use daily and know best. But the shape of it ports.

ChatGPT's version is called Work, and it now lives inside the Codex app, which until recently was just OpenAI's coding agent. That's a slightly odd home for it if you're not a developer, but it's the same idea: connectors, file access, multi-step tasks that run without you watching. Every workflow above translates roughly one to one. If you're already living in OpenAI, stay there and don't let me talk you into a second subscription.

n8n, Make, Zapier are the layer you add when you want something to run without you sitting in a chat window. Self-hosted n8n on a spare Mac Mini or a five dollar VPS is genuinely cheap. It's also only free if someone owns it, and "someone" is you, on a Friday night, when an update breaks a workflow.

Hermes Agent from Nous Research is the always-on, self-hosted, talks-to-you-on-Telegram end of the spectrum. It's real, it's open source, it runs for pocket money, and I've written about it in detail. It's also a developer's toy rather than a business product. No audit logging, no support, you own uptime and security. Wonderful if you enjoy running a Linux box. If you don't know whether you enjoy running a Linux box, you don't.

Rough order of power, and of how much of your weekend it eats: Chat, then Cowork, then n8n, then self-hosted. Stop as soon as it's working. There's more on the broader agent landscape here.

What's a waste of your money

Unreviewed AI quotes. Covered above. The maths is seductive and the line items lie.
"AI local SEO" subscriptions at $99 a month. Answer your phone first. Come back to this when you've run out of better problems, which will be never.
Thin AI wrappers. Before you subscribe to any narrow "AI something" tool, ask what it does that your twenty dollar chatbot and the software you already pay for don't. Usually the answer is "a nicer logo".
Autonomous scheduling optimisation. Suggestions across a couple of vans, fine. Set-and-forget across a fleet with real constraints, no. Not yet.
Anything Australian and regulatory. A general chatbot will be confidently, fluently wrong about GST treatment, Fair Work award rates, and state licensing. It will not hedge. It will not blink. Your apprentice's pay rate is not a vibe.

Watch the meters too. Per seat, per minute, per token. Cowork tasks chew through a plan allowance far faster than chat does, and the first big bill is always a surprise.

Start here this week

Three things. In this order.

Turn on the AI you're already paying for. ServiceM8, Xero, MYOB, QuickBooks, all of them shipped real features in the last year. Zero new vendors, zero new risk.
Twenty dollars for Claude or ChatGPT, connectors wired to a dedicated account, not your admin login.
Build the project brain. Rates, prices, terms, service area. Thirty minutes. This is the step that separates a useful assistant from an expensive random number generator.

Then leave it alone for a fortnight and see what you actually reach for.

Next up on the blog: the phone. Which is where the real money is hiding, and where the real landmines are too.

I build this stuff for a living, out of Sydney. If you get stuck wiring it up, you know where to find me.