08 Sep 2026
Software
Job management software built for a generic trade business (plumbers, electricians, cleaners) will handle scheduling and invoicing fine, but process serving, repossession and debt collection have requirements those tools were never built for. Before committing to a platform, it's worth checking it actually answers these — and worth actually testing them, not just taking a sales page's word for it.
1. Does it capture what your specific job types actually need?
A repossession needs a vehicle condition report — odometer, tyre and panel condition, what was actually in the vehicle when recovered. A debt-collection job needs a proper financial assessment — contact details, employer, assets, an honest read on ability to pay. A generic “notes” field isn’t the same thing as a purpose-built form for either, and the gap only becomes obvious once you’re relying on that record months later, in a dispute, and discover it’s thinner than you thought.
2. Does it check agent licensing before assignment, or just record it?
There’s a real difference between a licence field sitting on a profile as a reference note, and a system that actually won’t let an unlicensed agent be assigned to a job that legally requires one. The first relies on someone remembering to check; the second makes the mistake structurally impossible. Ask specifically which one you’re being offered — “we track licences” and “we enforce licensing at assignment” sound similar but aren’t.
3. Is it built for New Zealand, or adapted from somewhere else?
Address formats defaulting to the wrong country, currency assumptions, unfamiliar date formats, and — more substantively — where your data is actually stored and processed are all real, practical differences, not cosmetic ones. A tool built primarily for a much larger overseas market will often treat NZ as an edge case rather than the default, and that shows up in small frictions that add up over daily use.
4. Does field evidence actually hold up?
GPS-tagging and timestamps captured automatically at the point of logging are worth more than notes written up later from memory, especially once something gets contested. Ask specifically whether location and time attach automatically at the moment of capture, or whether that’s something an agent has to remember to add manually — the difference matters exactly when it’s needed most.
5. How does pricing actually scale?
Per-job fees punish growth — the busier you get, the more it costs on top of what you’re already paying. Understand whether a platform charges by seat, by job, or some mix, before volume becomes a cost problem you didn’t see coming. It’s also worth asking directly whether agents and client logins count toward any per-user cost, since that can quietly become the biggest line item on a bill you didn’t expect.
6. What happens to your data if you leave?
A platform that makes it easy to self-serve export everything — jobs, clients, financial records, your team roster — is a very different proposition to one where getting your own data out means a support ticket and a wait, or worse, isn’t really possible at all. This is worth checking before you commit, not after you’ve decided to leave and discover the answer the hard way.
A few red flags worth watching for
A demo that only shows the happy path and dodges specific questions about licensing enforcement or data export. Pricing that’s only available after a sales call rather than published plainly. Vague answers about where data is actually hosted. None of these are automatically disqualifying on their own, but a platform confident in its answers usually just gives them.
None of this is about ruling out generic tools entirely — plenty of small agencies get by on general-purpose software for a while. It’s about knowing which gaps you’re accepting if you do.
