The September checklist

The September checklist

Peak season is about eight weeks away. From late October the phone starts and doesn’t really stop until February, and whatever is loose in your business right now will be twice as loose when every second call is a breakdown.

This is the list we run through with customers in the last weeks of winter. None of it takes long. All of it is easier now than it will be in December.

Block out an hour with whoever runs operations and work down it in order. Most businesses find two items they’re fine on, three that need a fortnight of attention, and one that explains a problem they’ve been living with for a year.

1. Confirm every PM contract, and get the jobs on the board

Preventative maintenance is the only revenue you can forecast, and it’s the first thing that gets bumped when the breakdowns start. Confirm the contracts now, get the scheduled jobs generated for the next six months, and you’ll protect that work when the pressure comes on.

It’s also the cheapest sales conversation available to you. A customer whose PM is confirmed in August isn’t taking a cold call in October — and the ones who’ve let their maintenance lapse are exactly the ones who’ll ring you in a panic on the first 38-degree day.

2. Shrink the gap between finished and invoiced

Pick ten jobs from last month and measure it. Whatever that number is in August, it gets worse in December — the volume doesn’t change the admin capacity. Go into summer with the gap as small as you can make it, because peak season is when cashflow either carries you or squeezes you.

While you’re there, run the list of jobs marked completed but never invoiced. Almost every business has more sitting in that list than they’d guess, and clearing it before summer is the fastest money you’ll make this quarter.

3. Read last summer’s callbacks

Pull the repeat visits from last January and February and look for the pattern. Same site? Same asset? Same fault? That list tells you exactly where the training, the parts stock or the process will fail you again — and you’ve got eight weeks to do something about it.

Two patterns are worth acting on immediately: the same fault at the same site — usually a repair that should have been a replacement, and a conversation to have with the customer now — and the same fault across different techs, usually a training or parts-stock problem you can fix in an afternoon.

4. Check your asset records on the sites that matter

Take your ten biggest maintenance customers. Can you see model, serial and fault history for their critical plant without ringing anyone? If not, make it a standing instruction for the next eight weeks: photograph the plate, capture the details, every visit.

Eight weeks of that habit across a full crew adds up to a surprising amount of history, and it covers exactly the sites you’ll be sending unfamiliar techs to when everyone is stretched in January.

5. Tidy your quoting templates

Summer quoting is fast quoting. If your standard inclusions, rates and after-hours loadings are current before the rush, your techs can quote on site instead of promising to send something through — and the quote sent from the driveway wins far more often than the one that arrives on Thursday.

Check your after-hours and weekend rates while you’re in there. Plenty of businesses go into summer charging what they set two winters ago, then work every Saturday in January for a margin that didn’t survive the last two years of parts pricing.

6. Decide what you’re not doing

The businesses that cope best in summer are the ones that decided in September which work they’d turn down. Know your minimum call-out, your after-hours position and which customers get priority — before you’re making that call at 6pm on a 39-degree Friday.

7. Agree who covers what, in writing

Summer runs on goodwill until it doesn’t. Set the on-call roster for December and January now, agree the rate, and tell everyone in August rather than sorting it out in the second week of a heatwave. The same goes for the office: someone has to keep invoicing moving while the phones run hot, and that person shouldn’t also be the one dispatching.

If working through this list turns up things your current system can’t tell you — how many PMs are due, what’s unbilled, which assets you’ve touched twice — that’s worth a conversation now rather than in November.

Book a 20-minute demo before the season starts, or call us on 0457 228 884. Australian-founded, Australian-led, 30 years in HVAC&R and electrical.

AI won’t fix a broken process

AI won’t fix a broken process

Every vendor in field service software is selling you an AI layer this year. Agents that write your job notes, assistants that answer questions about your data, tools that brief your techs before they arrive.

Some of it is genuinely useful, and we’re building in that direction too. But after 30 years of watching Australian service businesses buy software, we’d say this: none of it helps if your techs still can’t see today’s run and your invoices still go out nine days late.

We’ve been through a few of these waves. Handhelds were going to fix field service. Then the cloud was. Then mobile apps. Each one genuinely helped the businesses that had their process sorted, and each one disappointed the businesses hoping the technology would supply the discipline they didn’t have. There’s no reason to think this wave is different.

What has changed is the pace of the claims. A feature that would once have been sold as a time-saver is now sold as a member of your team. Read the fine print on most of it and you find something genuinely handy — automatic job summaries, better search, a nicer way to ask a question of your own data — wrapped in language that implies it will run the business for you.

Automation is a multiplier, and multipliers work both ways

Point a clever model at a job record nobody filled in properly and you get a confident summary of nothing. Automate a quoting process that’s wrong and you’ll produce wrong quotes faster than you ever could by hand.

The businesses getting real value out of automation are the ones whose data was already clean — because their process was already sound. That’s the uncomfortable bit. The prerequisite isn’t a licence. It’s a workflow your team actually follows.

It’s the same reason a report is only as good as the data behind it. If half your jobs are missing their parts, no amount of clever summarising will tell you your real margin. It will tell you the wrong number faster, and with more confidence than a spreadsheet ever had.

The unglamorous things that actually move the numbers

In our experience there are four, and none of them will ever be a launch announcement.

One thread from quote to invoice, so nothing is re-keyed. A schedule everyone can see. Job costing that includes the parts, so margin is a fact rather than a feeling. And a preventative maintenance program that runs itself, because that’s the revenue you can forecast twelve months out.

Get those four right and the business feels different within a quarter.

If you only do one, do the first. Almost every problem an owner brings us — margin they can’t explain, invoices going out late, techs ringing the office all day — traces back to the job record being re-typed somewhere between the site and the ledger.

The second is the schedule everyone can see, because it’s the fastest to fix and the whole office feels it inside a week. The third is job costing that includes parts, which is where most businesses discover their real margin is several points off what they assumed. The fourth — preventative maintenance running itself — is the one that changes how the business is valued, because forecastable revenue is worth more than reactive revenue to a buyer, a bank, or you.

Where automation genuinely earns its place

We’re not luddites about it. Automation is excellent at the repetitive, rule-based work: raising the PM jobs when they’re due, pulling the parts onto the invoice, flagging the job that’s been sitting at “completed, not invoiced” for a fortnight.

That’s the boring bit, and the boring bit is where the money is. It’s also safe to automate, because the process behind it is deterministic — you’re not asking a model to guess what happened on site.

The distinction we hold to is simple: automate the things where being wrong is obvious and cheap, and keep a human on the things where being wrong is expensive and invisible. Raising a scheduled PM job is the first kind. Deciding what to charge for a contested three hours is the second.

That’s also the honest reason we don’t lead our marketing with AI. We’d rather show you a scheduling board your dispatcher can run on day one than a demo of something clever that depends on data you don’t have yet. When the data is there, the clever parts get much more useful — and we’ll build them.

Ask any vendor these three questions

Including us. What does week one look like, with dates? Who answers the phone when it breaks, and where are they? And what won’t your software do for a business like mine?

That third one is the tell. Everyone can demo the good bits. Thirty years in, we know where we fit — HVAC&R and electrical contractors who need configuration around their own process — and we know where we don’t. We’d rather say so before you sign than six months into an implementation.

Australian-founded, and it matters more than it sounds

We don’t raise the flag for the sake of it. It matters for practical reasons: our support hours are your working hours, we know what a Reece or Actrol account looks like, we’ve built for Australian compliance and after-hours rates, and when something breaks at 7am you speak to someone who can change it — not someone logging a ticket for a team who start work as you’re knocking off.

Thirty years in the same market also means we’ve watched businesses grow from eight techs to forty. We built for that transition specifically, which is why we don’t chase the sole-trader end of the market and don’t pretend to.

If you’re a one-van operation, there are simpler and cheaper tools than us and we’ll happily name them. If you’re running 10 to 50 techs across HVAC&R or electrical, with maintenance contracts, project work and real asset obligations, that’s the shape of business we’ve spent three decades building for.

Ask us the hard question. Call 0457 228 884 or book a demo — Australian-founded, Australian-led, and you’ll speak to someone who knows the industry, not a script.

Your asset history is the moat

Your asset history is the moat

Every maintenance contract eventually comes up for renewal, and when it does you’re in a room with someone comparing you to a number on a page. If the only thing that separates you from the next contractor is price, you’ll win some and lose some, and the ones you win will be the ones you shouldn’t have.

There’s one thing a competitor genuinely cannot copy: what you know about that customer’s equipment.

Not the price. Not the response time — anyone can promise four hours. What they can’t copy is six years of knowing that the unit on the north side ices up every February, that the isolator sits behind the false ceiling, and that the plant room key lives with the café next door.

What the record actually buys you

Three things, and they’re all commercial rather than technical.

You quote from facts. When you know the age, the model, the last four faults and what was replaced in 2022, you price the work properly. The contractor quoting blind is either guessing high and losing, or guessing low and eating it.

You win the conversation about next year. “That compressor is nine years old and it’s tripped twice this summer — here’s what I’d budget for” is a different conversation from “let us know if anything breaks”. It moves you from supplier to advisor, and advisors don’t get re-tendered every year.

You survive the disputes. Photos, times, parts and a signature attached to the job settle the “that’s not what we agreed” conversation before it starts.

There’s a fourth benefit that only shows up when something goes wrong: compliance and warranty. When a manufacturer wants proof the unit was serviced to schedule, or an insurer wants evidence of the last inspection, the business that can produce a dated record with photos attached settles it in an email. The business that can’t spends a fortnight reconstructing it from memory and bank statements.

Why most registers never get built

Not because anyone disagrees with the idea. Because building one as a project is miserable — a spreadsheet, a fortnight of someone’s life, and it’s out of date the month after it’s finished.

The registers that work are the ones that build themselves. Every visit adds to the record because the tech is standing in front of the unit anyway. Photograph the asset plate, capture the model and serial, note what was done. Four seconds a visit, and after a year you have something no competitor can produce.

Keep the capture list short or it won’t happen. Model and serial off the plate, a photo of the plate itself, location on site, and what was done today. That’s it. Anything longer and techs start skipping fields — and a register with holes in it is worse than none, because you stop trusting it, and once you stop trusting it you stop looking.

The one habit worth enforcing: photograph the plate before you touch anything. Four seconds while you’re standing there, and it saves the phone call eighteen months later when someone needs a model number to order a part.

“That’s for the big facilities contracts, not us”

We hear this from businesses with twenty techs who are, in practice, already maintaining a few hundred assets. You don’t need an FM division. You need the last three visits, in one place, before you quote.

And it compounds. Year one it’s useful. Year three it’s the reason you keep the contract when a national comes in under you.

Here’s what that looks like in the room. The customer has two quotes. Yours comes with a list of their twelve critical assets, their age, and a note on the three that will likely need replacing in the next two years. The other one is a price. Even if you’re not the cheapest, you’ve made the decision about risk rather than cost — and you’ve made it hard to switch, because whoever comes next starts from zero.

How it works in TSMPlus

Assets live against the site, jobs attach to the asset, and the tech sees the full history on their phone before they open the plant room door — including offline, which matters in basements and cold stores. Preventative maintenance contracts generate their own jobs against those assets, so the record keeps building whether or not anyone remembers to update it.

Because the register builds itself out of work you’re doing anyway, there’s no project to schedule and nobody spends a fortnight on a spreadsheet. You simply have more history in a year than you have now, and considerably more in three.

Where to start if you’re starting from nothing

Don’t try to back-fill. Pick your ten largest maintenance customers, make asset capture mandatory on every visit to those sites from today, and leave the rest to catch up naturally as work comes through. Within a season you’ll have solid records on the accounts that actually decide your year.

Then use it in front of the customer at least once a quarter — a short note on what you serviced, what you found and what you’d watch. That’s the moment the register stops being an admin task and starts being the reason they renew.

Start the register with your next job. Start a free trial, or book a demo and we’ll show you what a year of asset history looks like in practice.

Live in a week: an honest rollout plan

Live in a week: an honest rollout plan

The question we get asked most often isn’t about features. It’s “how long will this take, and how much of my time is it going to eat?”

The question we get asked most often isn’t about features. It’s “how long will this take, and how much of my time is it going to eat?”

It’s a fair question, and the honest answer is that most software rollouts in this industry go badly for the same two reasons: the business tries to switch everything on at once, and nobody was ever told what week one would actually look like. So here it is — day by day, for a business running around twenty techs.

Before day one: two decisions, one list

You need to decide two things before anyone touches the system. First: which workflow hurts most right now — scheduling, quoting or invoicing? That’s the one you go live with. Second: who owns this internally? One person, usually the operations manager. Not a committee.

Then there’s the list: your customers, your sites, and your active jobs. Most businesses can export that from their accounting system in an afternoon. We do the rest of the data work from there.

Monday: configuration, not training

Day one is us and your operations lead in a room — or on a call — setting the system up around how you already work. Job types, your stages, your invoicing rules, who sees what. This is the part that matters, and it’s the part generic platforms skip: we configure to your process rather than asking you to adopt ours.

Time from your side: about half a day.

It’s worth saying what we do rather than what you do. We handle the data import, the configuration, the accounting integration and the sanity-checking afterwards. What we can’t do is make the decisions — how you want jobs staged, what your invoicing rules are, who’s allowed to change a price. Those need someone from your business in the room, which is why one clear owner matters more than a big committee.

If your process is genuinely unusual — and in HVAC&R and electrical it often is, between site access rules, PO requirements and after-hours rates — this is the day we build around it rather than asking you to change it. That’s the difference between software that sticks and software that gets quietly abandoned in month four.

Tuesday: the office team

Schedulers and admin staff learn the board and the job screen. Two hours, hands on, with real jobs rather than demo data. By the end of the session they’re building jobs faster than they were on the whiteboard — that’s the bar, and if we don’t hit it we keep going until we do.

We start with the jobs already in the diary rather than made-up examples, because the questions people actually have are specific: the customer who wants two POs on one job, the site that needs the same tech every time, the recurring job that has to be split across two months. Answering those in the session is what turns training into confidence.

Expect one person to pick it up in an hour and one person to need a second sitting. That’s normal, and worth planning for rather than pretending everyone learns at the same speed.

Wednesday: the techs

This is the day everyone worries about, and it’s usually the easiest. The mobile app takes about forty minutes to explain, mostly because there isn’t much to explain: here’s your day, here’s the job, here’s the site history, here’s how you sign it off.

Techs aren’t afraid of technology. They’re afraid of software that’s slower than the paper it replaced. If the app doesn’t save them time on the first job, they’ll go back to the docket book and you’ll never get them back — so we design for that first job.

The pitch to the crew is short: you stop writing the same thing twice, you stop driving dockets back to the office, and you stop getting rung at 7pm about a job you did on Tuesday. Framed that way, adoption is rarely the fight people expect.

One thing worth deciding in advance: whether techs capture time as they go or at the end of the day. Both work. Not choosing is what causes the mess.

Thursday: run it in parallel

One day of belt and braces. Jobs go into TSMPlus and the old process keeps running alongside. You’ll find the three or four things nobody thought to mention — the customer who needs two POs, the site that’s technically two sites, the after-hours rate. We fix those on the day.

Parallel running for a single day is deliberate. Run it for a fortnight and you’ll have two half-maintained systems and a team that trusts neither. One day is enough to surface the surprises without letting the old process reassert itself.

Friday: live

Friday you invoice out of TSMPlus. That’s the moment it becomes real, and it’s deliberately the end of week one rather than month three — because the invoicing win is the one everybody in the business feels immediately.

Then you stop. Don’t add modules for a few weeks. Let the new normal settle, then pick the next workflow — purchasing, preventative maintenance, asset registers, project costing.

A realistic month two looks like this: purchasing tied back to jobs so your costing is real, then preventative maintenance contracts generating their own work, then asset registers building themselves off the back of both. Each of those is a couple of hours of setup, not another week.

What actually goes wrong

Three things, in our experience. Dirty customer data that nobody wants to own. A business that tries to switch on eleven workflows in week one. And an owner who delegates it entirely and then changes the rules in week three.

None of those are software problems, which is why we’d rather talk about them before you sign than after.

What it costs you in hours

Add it up: half a day for your operations lead on Monday, two hours for the office team on Tuesday, forty minutes per tech on Wednesday, and a day of mild inconvenience on Thursday. Call it a day and a half of real business time across a week.

Compare that with the number most people carry around in their head — a month of disruption and a system nobody uses. That fear is well earned, but it comes from rollouts that tried to change everything at once, usually with a vendor on another continent.

The other number worth putting next to it is what the current process costs every week. If two people spend an afternoon each chasing dockets and re-keying jobs, that’s a day of wages a week, every week, forever. A day and a half once is not a difficult trade.

And if it does go long — because your data was messier than anyone thought, or a key person was away — you’ll hear it from us early rather than discovering it in week five. Telling you the awkward thing quickly is most of what good implementation actually is.

Ask us for a rollout plan for your business — with dates on it — before you commit to anything. Book a demo, or call 0457 228 884.

Before day one: two decisions, one list

You need to decide two things before anyone touches the system. First: which workflow hurts most right now — scheduling, quoting or invoicing? That’s the one you go live with. Second: who owns this internally? One person, usually the operations manager. Not a committee.

Then there’s the list: your customers, your sites, and your active jobs. Most businesses can export that from their accounting system in an afternoon. We do the rest of the data work from there.

Monday: configuration, not training

Day one is us and your operations lead in a room — or on a call — setting the system up around how you already work. Job types, your stages, your invoicing rules, who sees what. This is the part that matters, and it’s the part generic platforms skip: we configure to your process rather than asking you to adopt ours.

Time from your side: about half a day.

It’s worth saying what we do rather than what you do. We handle the data import, the configuration, the accounting integration and the sanity-checking afterwards. What we can’t do is make the decisions — how you want jobs staged, what your invoicing rules are, who’s allowed to change a price. Those need someone from your business in the room, which is why one clear owner matters more than a big committee.

If your process is genuinely unusual — and in HVAC&R and electrical it often is, between site access rules, PO requirements and after-hours rates — this is the day we build around it rather than asking you to change it. That’s the difference between software that sticks and software that gets quietly abandoned in month four.

Tuesday: the office team

Schedulers and admin staff learn the board and the job screen. Two hours, hands on, with real jobs rather than demo data. By the end of the session they’re building jobs faster than they were on the whiteboard — that’s the bar, and if we don’t hit it we keep going until we do.

We start with the jobs already in the diary rather than made-up examples, because the questions people actually have are specific: the customer who wants two POs on one job, the site that needs the same tech every time, the recurring job that has to be split across two months. Answering those in the session is what turns training into confidence.

Expect one person to pick it up in an hour and one person to need a second sitting. That’s normal, and worth planning for rather than pretending everyone learns at the same speed.

Wednesday: the techs

This is the day everyone worries about, and it’s usually the easiest. The mobile app takes about forty minutes to explain, mostly because there isn’t much to explain: here’s your day, here’s the job, here’s the site history, here’s how you sign it off.

Techs aren’t afraid of technology. They’re afraid of software that’s slower than the paper it replaced. If the app doesn’t save them time on the first job, they’ll go back to the docket book and you’ll never get them back — so we design for that first job.

The pitch to the crew is short: you stop writing the same thing twice, you stop driving dockets back to the office, and you stop getting rung at 7pm about a job you did on Tuesday. Framed that way, adoption is rarely the fight people expect.

One thing worth deciding in advance: whether techs capture time as they go or at the end of the day. Both work. Not choosing is what causes the mess.

Thursday: run it in parallel

One day of belt and braces. Jobs go into TSMPlus and the old process keeps running alongside. You’ll find the three or four things nobody thought to mention — the customer who needs two POs, the site that’s technically two sites, the after-hours rate. We fix those on the day.

Parallel running for a single day is deliberate. Run it for a fortnight and you’ll have two half-maintained systems and a team that trusts neither. One day is enough to surface the surprises without letting the old process reassert itself.

Friday: live

Friday you invoice out of TSMPlus. That’s the moment it becomes real, and it’s deliberately the end of week one rather than month three — because the invoicing win is the one everybody in the business feels immediately.

Then you stop. Don’t add modules for a few weeks. Let the new normal settle, then pick the next workflow — purchasing, preventative maintenance, asset registers, project costing.

A realistic month two looks like this: purchasing tied back to jobs so your costing is real, then preventative maintenance contracts generating their own work, then asset registers building themselves off the back of both. Each of those is a couple of hours of setup, not another week.

What actually goes wrong

Three things, in our experience. Dirty customer data that nobody wants to own. A business that tries to switch on eleven workflows in week one. And an owner who delegates it entirely and then changes the rules in week three.

None of those are software problems, which is why we’d rather talk about them before you sign than after.

What it costs you in hours

Add it up: half a day for your operations lead on Monday, two hours for the office team on Tuesday, forty minutes per tech on Wednesday, and a day of mild inconvenience on Thursday. Call it a day and a half of real business time across a week.

Compare that with the number most people carry around in their head — a month of disruption and a system nobody uses. That fear is well earned, but it comes from rollouts that tried to change everything at once, usually with a vendor on another continent.

The other number worth putting next to it is what the current process costs every week. If two people spend an afternoon each chasing dockets and re-keying jobs, that’s a day of wages a week, every week, forever. A day and a half once is not a difficult trade.

And if it does go long — because your data was messier than anyone thought, or a key person was away — you’ll hear it from us early rather than discovering it in week five. Telling you the awkward thing quickly is most of what good implementation actually is.

Ask us for a rollout plan for your business — with dates on it — before you commit to anything. Book a demo, or call 0457 228 884.