Field service platforms are built for a general shape of business: a job, a technician, a customer, an invoice. If your operation fits that shape, there are mature products and you should buy one.
The problem is that a large number of field businesses don’t fit it — not because they’re unusual, but because the job isn’t the point. For an inspection company, the deliverable is a certificate. For a calibration business, it’s a traceable record. For a customs broker, it’s a document set that satisfies an authority. The visit is incidental; the evidence is the product.
That distinction determines whether off-the-shelf software will work for you, and it’s the one most buying guides skip.
First: what kind of field business are you?
Job-shaped businesses. A customer calls, someone attends, work is done, an invoice goes out. Plumbing, general repairs, most installation work. Well served by established platforms. Buy one.
Route-shaped businesses. Recurring visits on a schedule to the same sites. Pest control, cleaning, landscaping, planned maintenance. Reasonably well served, though recurring scheduling is where cheaper products get weak.
Evidence-shaped businesses. The visit produces a record that must be defensible later — to a regulator, an insurer, a client’s auditor, or a court. Fire safety inspection, elevator maintenance, equipment calibration, environmental compliance, building surveys.
Most software disappoints the third group, because the features they need most are treated as add-ons: versioned certificates, controlled forms, technician qualification tracking, retention rules, and an audit trail that survives someone leaving the company.
The evaluation criteria that actually predict fit
Does it model your asset, or just your customer?
Generic platforms are organised around customers and jobs. Evidence-shaped businesses are organised around assets — this extinguisher, this lift, this tank, this meter — each with a history, a location, a next-due date, and a compliance status independent of who currently owns the site.
Ask: can I open an asset and see every inspection it has ever had, including under a previous owner? If the answer requires exporting to a spreadsheet, the model is wrong for you, and no amount of configuration will fix it.
Can it produce your actual document?
Every regulated field business has a document that must look a specific way, contain specific fields, and carry a signature or a certificate number. Ask the vendor to produce your form during the trial — not a generic PDF with your logo.
The follow-up matters more: what happens when the standard changes and the form needs a new field? If the answer is a support ticket and a fee, factor that into the cost, because forms change more often than anyone expects.
Does it work with no signal?
Plant rooms, basements, lift shafts, remote sites, ships. If your technicians work where there is no connectivity, offline capture isn’t a feature, it’s the product. Test it properly during the trial: put a device in airplane mode, complete a full inspection with photographs, and bring it back online. Watch what happens to the photographs specifically — that’s where weak implementations lose data.
Does it track who is allowed to do the work?
In many regulated trades, a job can only be signed off by someone holding a current qualification. Software that lets an unqualified technician be dispatched will eventually cause a real problem. Ask whether competencies are tracked, whether expiry blocks assignment, and whether the record is retained after the person leaves.
How does data get out?
The single most important commercial question, and the one that gets asked last. Can you export your assets, history, documents, and photographs, in a usable format, without paying? Ask to see an export during the trial. A vendor who can’t demonstrate it is offering you a one-way door.
Build, buy, or configure
Buy when a product exists that models your assets, produces your documents, and works offline. Do not customise it heavily — customisation on someone else’s platform combines the constraints of both approaches.
Configure a platform when the underlying model fits but the forms and workflows need shaping. Budget properly for it. A configuration project on a mature platform is real work, and the cost is routinely underestimated because the licence fee looks like the price.
Build when the asset model itself is wrong for your trade, the compliance regime is specific enough that no vendor has bothered, or your process is the competitive advantage. That’s a genuine business case rather than an ego project — but be honest that you’re taking on maintenance for as long as you use it.
A reasonable test: if you can list three things a platform can’t do, and each one costs you real money every month, building starts to make sense. If your list is preferences rather than costs, configure.
Mistakes that recur
- Buying on the demo. Demos are run against clean data by someone who knows the product. Insist on a trial with your own data and your own technicians.
- Ignoring the technicians. The people using it on a roof in the rain determine whether the rollout succeeds. If they hate it, they’ll keep using paper and you’ll have paid for both.
- Underestimating data migration. Years of asset history in spreadsheets is the hardest part of any rollout and is rarely in the quote.
- Not planning for a client’s audit. Someone will eventually ask you to produce every record for a site over five years. Find out now how long that takes.
Frequently asked questions
Is field service software worth it for a small team? Usually, once you’re past about five technicians or any compliance obligation. Below that, the gain is scheduling convenience; above it, the gain is defensibility.
How long does implementation take? Configuration and migration typically dominate. Assume months rather than weeks if you have historical asset data, and treat any quote that assumes otherwise sceptically.
Should we build our own? Only if the asset model or compliance regime genuinely isn’t served, and the gap costs you money. Then it’s a sound investment. Building to avoid a licence fee rarely pays back.
What about integrating with our accounting system? Check whether the integration is native, via a middleware service, or a CSV export described as an integration. The difference matters at month-end.
Internal links: #10 fire safety inspection software, #11 elevator maintenance software, #12 commercial roofing software, #13 customs broker software, #14 custom vs off-the-shelf, /industries. External references: the standard governing your own inspection regime; your national accreditation body’s record-keeping requirements. CTA: “If no platform fits your trade, that’s worth a conversation.” → /contact