Get onboard. Stage by stage.

It doesn't fit work that's organised by shifts. In roster-based businesses, the unit isn't a job — it's a shift at a venue or location, repeating on a pattern, filled by whoever's available and qualified. Cleaning crews on recurring commercial contracts. Hospitality venues with weekly rosters and penalty rates. Retail floors that need cover. Call centres on rotating shifts. ServiceM8 has no concept of a roster, shift, availability window, swap, or award rule. Fitting one in means fighting the platform every week. For those businesses the right tool is a workforce management platform — Deputy, Tanda, or Connecteam in this market — sometimes paired with a job system if there's site work alongside the roster.

It doesn't scale into hundreds of staff with the structural complexity that comes with that. The things that break at enterprise scale are the things you don't notice when you're small: multi-entity setups (separate ABNs rolling up to a group), cost centres and divisions with their own P&Ls, granular role-based permissions, multi-tier approval workflows, consolidated reporting across business units, dimensional GL coding, integration with enterprise ERPs like SAP or Oracle, and the audit trail and segregation-of-duties controls that compliance teams ask for.

ServiceM8 handles project-shaped work up to a point. Project management — properly — means dependencies, critical path, resource allocation across multiple concurrent projects, progress claims under a head contract, variation registers, RFI logs, defect tracking, retention and release schedules, and version-controlled documents like drawings and specs. ServiceM8 has none of that natively, and the workarounds creak under the weight of a real construction or civil project. If the business is running multi-month builds with subcontractors, coordinating several trades at once, dealing with progress claims and variations against a head contract, or working from drawings that change week to week — they want a project management platform. Procore, Buildxact, or CoConstruct depending on the shape, or a tier above for serious civil work. ServiceM8 can sit alongside for the service arm of the same business; it can't be the spine of the projects side.

ServiceM8 is configurable, not pre-cooked. Done well, it earns back the setup tenfold. Done badly — or not at all — it sits there as a bill. The reason ServiceM8 fits so many different shapes of trade and field service business is the same reason it doesn't fit any of them out of the box. Job categories, custom fields, badges, queues, forms, email templates, automations, integrations — these are levers the platform gives you, not defaults it ships with. A buyer who wants to sign up, log in, and start dispatching against a workflow that already matches their business is going to be disappointed. Pre-cooked products exist, but they're making compromises on someone else's process — and you may not see those compromises until you're three months in and the business has bent itself around them.