Custom Field Service Management Software

Field service management is the software category for any business whose work happens somewhere other than the office — installations, servicing, inspections, planned maintenance. The pattern is always the same: a job is scheduled, a crew travels to a site, work is done, evidence and paperwork are produced, and someone back at the office needs all of it to invoice, claim warranty and answer the customer's next phone call. Most UK businesses in this position run that entire chain on a whiteboard, a spreadsheet, a WhatsApp group and a stack of paper job sheets — and it works, right up until it doesn't.

The Real Cost of Paper Job Sheets

The obvious cost is time — someone re-typing job sheets into an invoicing system. The expensive costs are the ones nobody logs. An invoice that goes out four days late is four days of working capital. A warranty claim rejected because there's no dated photo of the installed unit is a repair you now pay for yourself. A customer dispute you can't evidence is a discount you didn't plan to give. A recall you can't scope because you don't know which serial numbers went to which addresses is a very bad week.

And there's a slower cost: without structured data on what happened on site, you can't see which crews are slow, which job types are consistently underquoted, or which product lines generate the most callbacks. You are running an operation on anecdote. Every business I've worked with in this space had a strong opinion about which crew was the problem — and roughly half of them turned out to be wrong once the data existed.

Where This Works Best

HVAC, refrigeration and air conditioning — multi-day installations, F-Gas record-keeping, commissioning data per unit, and manufacturer warranty claims that require photographic evidence and serial number capture. The paperwork burden here is heavy enough that it usually justifies the system on its own.

Solar PV, batteries and heat pumps — MCS certification, DNO paperwork, handover packs and performance commissioning data. Grant-funded and scheme-backed work in particular carries audit requirements that a phone camera and a shared drive won't satisfy for long.

Windows, doors and glazing — survey-to-fit workflows where the measurement stage determines the manufacturing order, and a survey error becomes a remake. Structured survey capture on site, tied to the order, is where most of the value sits.

Facilities and planned maintenance — recurring visit schedules across many sites, asset registers, condition reporting and SLA compliance. The value here is less about individual jobs and more about proving coverage across a contract at the end of the quarter.

Off-the-Shelf FSM vs Custom

I want to be straightforward about this, because it affects whether you should hire me at all. Platforms like Simpro, BigChange, Jobber, Commusoft and ServiceTitan are mature, well-built products, and for a large share of UK trades businesses they are the right answer. If your process is close to standard, buy the product.

Custom becomes the better economics in a few specific situations. When per-user, per-month pricing across 40+ field staff exceeds the amortised cost of owning software. When your job types genuinely don't fit the platform's data model, and your team compensates with free-text notes and a separate spreadsheet. When the FSM has to be one component in a larger operational system — order management, stock, manufacturing — rather than an island with a CSV export. And when your commissioning or compliance paperwork is specific enough that engineers end up completing a PDF on the side, which quietly means the platform isn't actually your system of record.

Designing for the Engineer, Not the Office

The single biggest reason field service software fails is that it's designed by people who will never use it in the rain. Every extra screen, every field the office wants "just in case", every form that requires two hands and good light is a reason for the engineer to fill it in badly at the end of the day from memory — which produces data that's worse than useless because it looks reliable.

My rule is that the app must be faster than the paper it replaces, from the engineer's point of view, on day one. Camera-first workflows. Large touch targets. Pre-filled everything the office already knows. No free-text where a tap will do. Offline by default so the app never blocks on a spinner. If the engineers grumble but use it, the system will work. If they work around it, no amount of management pressure will fix that.

What It Costs in the UK

A fixed-price discovery and process map — shadowing crews, documenting the real workflow, and producing a scoped build plan — starts around £3,500 and takes about a week. A pilot system covering one crew and one job type, with dispatch and a working mobile app, typically runs £12,000–£25,000 over 6–10 weeks. A full multi-crew platform with evidence capture, document generation, warranty tracking and integrations into your existing order and accounting systems generally sits in the £45,000–£110,000 range across 4–8 months.

Whether that beats a subscription depends almost entirely on headcount and fit. At 10 field staff on a standard process, buy the product. At 40+ field staff with genuinely non-standard workflows and an existing system it must integrate with, custom usually pays back within two to three years and you own the asset at the end.

Getting Started

The first step is never a build — it's a day in the field. I go out with a crew, watch what actually happens between the job being scheduled and the paperwork landing back at the office, and map where information gets lost. That produces a scoped plan with a cost per module, and quite often it also identifies two or three fixes worth making before any software is written.

Based in Manchester, I work with installation, maintenance and equipment businesses across the UK. If your crews are still returning paper job sheets, or your FSM platform has become the thing everyone works around, let's talk it through.