AI for trade and field service businesses

The day

One day, two places

Read this as a single Tuesday. The left side is what happens on site, the right side is what happens in the office, and the point is how often the same piece of information has to cross between them.

1. 6.10am
   SiteCrews leave the yard

   A hot water replacement, two services and a callback that nobody has had time to read the history on.

2. 6.45am
   OfficeThe run sheet is already drafted

   Jobs ordered by suburb and access window, with the two that need parts flagged against what is actually on each van.

3. 8.20am
   SiteThe wall comes off

   What is behind it looks nothing like the quote. Four photos and a thirty second voice note go into the job.

4. 8.35am
   OfficeA variation exists before the extra work starts

   Those photos and that note become a priced variation against the original scope, waiting for the supervisor to approve and the customer to accept in writing.

5. 10.00am
   OfficeThree enquiries arrive three different ways

   A web form, a missed call and a message on the Google listing. Each becomes a job card with the address, the fault described in the customer's words, and the photo they sent.

6. 11.30am
   SitePaperwork gets dictated, not deferred

   Test results and job details are spoken into the phone on site instead of being reconstructed from memory at six o'clock.

7. 1.15pm
   OfficeTwo quotes go out the same day

   Standard work drafted from your rate card and the last three similar jobs, checked by the owner, sent before the customer rings somebody else.

8. 3.40pm
   SiteJob closed properly

   A forty second voice note covering what was done, what was used, what was tested and what the customer was told.

9. 4.10pm
   OfficeNotes, materials and an invoice draft

   That voice note becomes the job notes, the materials list and a draft invoice. The office checks it rather than writes it.

10. 5.00pm
    OfficeTomorrow is drafted

    Callbacks, maintenance jobs coming due, a quote sent last week that has gone quiet, and the invoices now well past their terms.

None of that removes a person. It moves the typing off the people who are already tired, and it closes the gap between work happening and work being recorded, which is where cash and margin actually live.

The problem

Why the handoff is the expensive part

Plumbers, electricians, air conditioning and solar installers, cleaners, pest controllers and locksmiths mostly run ServiceM8, Tradify, Fergus, AroFlo or simPRO, with Xero or MYOB behind it. That software is good. It is not the bottleneck.

The bottleneck is that a job is understood on site and recorded in the office, and the translation is manual. A tech knows the meter box was undersized, the access was awful and the customer asked about a second quote. By the time that reaches the office it has become three words in a job note, if it arrives at all. The office then writes an invoice that does not reflect what happened, the owner wonders why the job lost money, and nobody can reconstruct it a month later.

Every one of the common complaints in a trade business traces back to that handoff. Quotes that take four days because the detail has to be chased. Invoices sent a fortnight after completion because the notes were thin. Variations never billed. Compliance paperwork completed from memory on a Sunday. An office manager who cannot take leave because the knowledge of how it all works lives with them.

Quoting

Quoting is the decision that sets the year

For most established trade businesses, quoting is the single most valuable process to get right. The win rate on a quote sent the same day is not the same as one sent on Friday for a job the customer asked about on Monday, and consistency matters as much as speed: two estimators pricing the same job differently is a margin problem disguised as an admin problem.

What a drafting agent can genuinely do is assemble. It reads the enquiry, the photos, the site notes and the history of similar jobs you have already priced, then produces a draft with the scope written out, the inclusions and exclusions spelled out, the assumptions listed, and labour and materials laid out against your own rate card. Where the job does not resemble anything in your history, the draft says so and asks for a site visit rather than inventing a figure.

The price itself is yours. An owner or estimator checks the figure, adjusts for the things only a person knows, and sends. Nothing is quoted outside your pricing rules, and no discount is offered by software.

Variations

Variations are where the margin leaks

Ask any trade business owner where the money goes and variations come up within a minute. Extra work gets done on a verbal nod. It is never documented, so it is never billed. Or it is billed six weeks later and the customer disputes it, and the relationship costs more than the work was worth.

This is a paperwork problem, and paperwork problems are the ones worth automating. The anatomy of a variation that holds up is always the same, and all of it can be drafted from a voice note and a handful of photos taken while the tech is standing in front of the problem.

What changed

The condition found on site, described plainly, with the photos attached and timestamped to the moment they were taken.

Why it changed

The reason the original scope no longer covers it, written in language a customer will accept rather than trade shorthand.

What it costs

Additional labour, materials and time drawn from your rate card, with the original quoted scope shown next to it.

Who approved it

A supervisor approval and the customer's written acceptance, captured before the extra work starts rather than after.

Where it lives

On the job in your job management system, in a register the owner can read, so the end of month invoice includes it.

For contract work the same logic carries into progress claims. The claim is assembled from what has actually been recorded as complete, which is a different and better experience than reconstructing a month from memory.

Scheduling

Scheduling a crew that keeps moving

Scheduling in a field business is not a calendar problem, it is a constraint problem. Travel between suburbs, access windows set by a tenant or a body corporate, which parts are on which van, who holds the licence for the work, whether an apprentice is supervised, and which jobs are callbacks that have to go first whatever else is booked.

An agent can hold all of that at once and draft a run sheet, reorder the day when a job blows out, and write the running late message for the office to send before the customer rings to ask. It can also flag the thing nobody notices until it is too late: a job booked without the part, or a second visit booked for the same property on a different day.

The dispatcher still decides. Reordering somebody's day is a judgement about customers and about crews, and it stays with the person who knows both.

Compliance

The paperwork that has to exist, properly

Trade work generates documents that are not optional, and the consequence of getting them wrong is not an awkward email, it is a licence problem. Software can assemble and chase these. It cannot issue or sign them.

• Electrical complianceDetails for a certificate of testing and compliance assembled from the job record and the test results, ready for the licensed electrician to check and issue.
• Notifiable plumbing and drainage workThe job details, photos and dates collected into the form the licensee lodges, with a flag when something required is missing.
• Gas workCompliance paperwork prepared from the job record, with the certificate itself issued by the licensed person who did the work.
• Safe work method statementsDrafted from your existing templates for the specific task and site, for the supervisor to review before the crew starts.
• Licences and insurancesExpiry dates tracked for the business, each licensed worker and your subcontractors, with reminders well before the date.
• Warranty and handover packsManuals, test records, certificates and warranty terms collected into one document for the customer at completion.

The practical gain is that the pack is complete while the job is fresh, rather than assembled under pressure when a builder, an insurer or a regulator asks for it months later.

Your stack

What your job management software already knows

Most of what these workflows need is already being captured. It is just sitting in a form nobody can act on at six in the morning.

• ServiceM8Job cards created from enquiries, notes and materials from voice notes, and invoice drafts ready for the office to check.
• Tradify or FergusQuote drafts from your rate card, a daily schedule summary, and quotes that have gone quiet surfaced for follow up.
• AroFlo or simPROLarger crew scheduling, variation registers, progress claim assembly and compliance document tracking.
• Xero or MYOBInvoices drafted on the day of completion, overdue accounts chased on your schedule, and a weekly read on cash.
• Google Business ProfileEnquiries captured from the listing and review replies drafted for a person to post, not published automatically.
• Microsoft 365 or Google WorkspaceShared inbox sorted by job and urgency, with builder and strata correspondence matched to the right project.

Guardrails

Licences, certificates and what software must not sign

Your licence, your certificates and your warranties are yours, and the responsibility that sits behind them is not delegable to a tool. Nothing we build issues a compliance certificate, signs a safe work method statement, prices outside your rules or commits you to a completion date. Those are decisions by licensed people, and the workflow is designed to put the information in front of them faster, not to take the decision away.

Anything about safety is kept out of drafting entirely. An incident, a near miss, a defect that makes a site unsafe or a dispute with a builder goes to a person immediately, with no draft attached, because a tidy summary of a safety problem is worse than a phone call. The same applies to anything about somebody's employment.

Customer information is handled under the Privacy Act, in business grade accounts with training on your data switched off, and each workflow is given access to the one system it needs. Your team learns the same boundaries in AI training, and the build itself sits in AI implementation.