When it is worth moving off ServiceM8 (and when it is not)

ServiceM8 is a good product. That does not make it right forever. Four honest signals it has stopped fitting, and three that mean you should stay put.

Let us start where we should: ServiceM8 is a good bit of software. It is well built, it is genuinely useful, and thousands of Australian trade businesses run happily on it. Most of the businesses using it should keep using it.

But we get asked this a lot, so here is an honest read on when it stops being the right tool, and, more importantly, when it has not.

Stay where you are if…

It does 90% of what you need. The last 10% is almost never worth a build. Live with it.

Your frustration is really a process problem. A common one: people blame the software for jobs being scheduled badly, when nobody has agreed who schedules and when. New software will reproduce the same mess, faster.

You have not actually set it up properly. A surprising number of unhappy users are running a default configuration from three years ago. Paying someone good for a day to configure it properly is a fraction of any other option.

It may be time if…

1. The workarounds have become the system. There is a spreadsheet next to the software that everybody actually relies on. There is a WhatsApp group that is the real source of truth. When the workaround is where the business really runs, you are already maintaining a custom system, just a fragile one made of spreadsheets and memory.

2. The thing that makes you different is the thing it cannot do. This is the strongest signal. If your competitive edge is, say, reconciling crane-scale weights against a weighbridge before invoicing, and no product supports that, then your edge is being carried by hand. Generic software is built for the average of an industry. Your advantage is precisely where you are not average.

3. Per-seat cost is shaping your decisions. When you hesitate to give a new hire a login, or people are sharing accounts, the pricing model has started distorting how you run the business. That is a real cost, and it is worse than the invoice, because shared logins wreck your data.

4. You are running several tools that do not talk. One for jobs, one for invoicing, something else for the website enquiries, a separate thing for compliance paperwork. The cost is not the subscriptions, it is the person moving data between them, and every gap where things get missed.

Do the honest sum

Add up: subscriptions across every tool, per-seat growth over the next three years, the hours a week someone spends moving data by hand at their real cost, and your best estimate of what gets under-billed because information does not carry through.

Compare that to a one-off build you own, plus its running costs, which for a business of this size is usually a couple of hundred dollars a month in hosting and services.

Sometimes the sum says stay. That is a good outcome: you have saved yourself a large project and you know why you are staying.

If you do move, move carefully

Do not switch overnight. Run the new system in parallel with the old one for at least a week with real jobs, and do not turn the old one off until the new one has handled a full cycle, including the messy ones. Get your data out first, and check you can actually read it.

And be clear-eyed about the fact that a custom build takes months, not days. If you need relief this quarter, fix the configuration and the process first. Building is the right answer to a structural problem, not an urgent one.