AIat workStart an enquiryEnquire

Home / Blog

The report that keeps the contract: writing jobs done at 10pm by the person who owns the business

Nobody in a cleaning or maintenance business is searching for AI training. They are, however, writing tenders on a Sunday.

Search volume for "AI training" in the cleaning industry is close to nothing. The same is true in most trades. If you built a marketing plan around those keywords you'd conclude there's no market here.

There is. It's just that nobody is shopping for AI training. They're trying to get a tender out by Friday, and they're doing it themselves, at night, after a full day of running jobs.

Two documents decide the year

In contract-driven work, the commercial reality comes down to two pieces of writing.

The submission wins the work. A tender or a capability statement, usually against a template that asks for things in a format nobody enjoys: methodology, scope of works, staffing model, quality assurance, WHS approach, references. Most of the content already exists in the business as knowledge. Almost none of it exists as text that can be reused, which means every submission starts closer to blank than it should.

The monthly report keeps the work. Facilities managers and strata committees renew on the basis of a document. A thin report with a photo and a sentence signals a supplier who isn't paying attention, regardless of how good the actual work was. A specific report that names what was done, what was found, and what's coming up next month reads like a supplier worth keeping.

Both of these land on the owner. Both happen outside billable hours. And both are the kind of structured writing where an hour of properly set-up work replaces most of a weekend — with no client-confidential information involved at any point, which sidesteps the whole privacy argument before it starts.

Where the time actually goes

When we sit with owners in this sector and list the jobs, the same five come up:

  1. Tender and quote responses — long, templated, repetitive between submissions, and always urgent.
  2. The monthly or quarterly client report — same structure every time, different facts.
  3. Site instructions and scopes of works — often needing to be understood by a casual, frequently multilingual workforce.
  4. Incident and defect write-ups — written quickly, read later by someone deciding whether you're a problem.
  5. Job ads and inductions — constant, because turnover in this sector is constant.

Not one of those is a client-confidentiality question. Every one of them is a writing job with a stable shape, which is exactly the kind of work where a reusable setup pays for itself in the first week.

Signs this is the right first job for you

  • It has a template or a format that barely changes
  • You do it monthly or more
  • It's currently done after hours
  • Someone else in the business could do it if it were less fiddly
  • Losing the contract it protects would hurt

The instruction quality lever

The one that gets underrated: instructions to the field team.

In a business with a large casual workforce, the gap between what the owner meant and what happened on site is an operational cost that shows up as rework, complaints and lost contracts. The document in the middle is usually a hurried message written between jobs.

Taking one clear set of instructions and producing consistent, plain-language versions — including in the languages your team actually reads — is not a productivity trick. It changes what gets done on site. That's a direct lever on renewal, and it's the reason cleaning and property maintenance became a full track rather than a footnote under trades.

If you can name the document that decides whether you keep your biggest contract, that's the job we'd build first.

Start an enquiry

Why the training has to look different here

A workshop framed as "AI fundamentals" will not fill a room in this sector, and it shouldn't. The people who need it are not going to spend half a day on a topic; they'll spend two hours on the tender.

So the engagement shape that works is a done-with-you workflow build: one job, on your real documents, built while you watch, ending with a setup that produces your format from your inputs. You don't learn a subject. You leave with the monthly report taking forty minutes instead of an evening, and the method is transferable to the next document whether or not you ever think about it as a skill.

The same logic runs through the trades and field services track, where the headline is same-day quoting and follow-up rather than anything about AI — because that's the problem, and AI is just the method.

What stays with you

The judgement. What to promise in a tender, what price to put on it, what to say about a defect that might become a dispute, and whether a site is safe. None of that moves, and any training that implies otherwise is selling you a problem rather than solving one.

What moves is the typing, the structuring and the remembering-what-goes-in-section-four. Which, if you're the person doing it on a Sunday, is most of what you resent about it.

Questions people ask about this

Our staff barely use email. Does this apply?

This isn't training for the field team. It's for the one or two people writing tenders, reports and instructions — usually including the owner.

Can it write the tender for us?

No. It can turn what you know about the site into a structured, complete response in your voice, in an evening instead of a weekend. The judgement about what to promise stays yours.

What about instructions for a multilingual team?

That's one of the highest-value uses in this sector: taking one clear set of instructions and producing consistent plain-language versions, which improves what actually happens on site.

Read next

If the tender is currently a Sunday job

A done-with-you workflow build takes one of these jobs — the tender, the monthly report, the site instructions — and rebuilds it on your real work with you in the room.

Start an enquiry
Start an enquiry