Software for businesses whose work happens somewhere else
Field service has a problem office software never solves: the work is at the customer, the person doing it is in a van, and the signal is unreliable.
If your business sends people out to do work, your software has a constraint most business tools were never designed for. The person who needs the information is not at a desk. They are in a van, on a roof, in a basement, or in a cellar with one bar of signal and gloves on.
Software built for an office assumes a keyboard, a large screen and a connection. Field service software has to assume none of those and still be the fastest way to do the job - because if it is slower than a phone call and a notepad, it will lose to the phone call and the notepad.
We build for those conditions, and NearOps - our own white-label platform for field service teams - is where we worked most of it out.
What usually goes wrong
These come up in nearly every conversation we have in this industry.
Scheduling by phone
The office spends the morning coordinating, and every change means three more calls.
Matching by radius
Twenty miles across a city and twenty miles across open country are not remotely the same job.
Paperwork after the fact
Job sheets filled in at the end of the day from memory, or not at all.
Chasing invoices
Work completed on Tuesday, invoiced on Friday, paid whenever - because billing is separate from the job.
Customers with no visibility
Every "what time are you coming" is a phone call someone has to take and answer.
No signal, no software
The tool stops working exactly where the work happens, so people stop using it.
The pieces that fix it
You don't need all of these. Most businesses start with one.
Location-aware matching
Real coverage areas by postcode or ZIP and honest travel implications, instead of a circle on a map.
Scheduling that respects reality
Job durations, travel time and capacity built into the diary rather than assumed.
Mobile-first job management
Built for a phone in one hand, with large targets and short flows.
Offline tolerance
Work captured without signal and synced when it returns, rather than lost.
Capture at the job
Photos, notes, signatures and parts recorded where the work happens, not reconstructed later.
Payment at completion
Invoice or take payment on site, while the customer is standing there and satisfied.
Customer self-service
Booking, status and documents online, which removes most of the inbound phone traffic.
Engineer onboarding
Verification and record-keeping for subcontractors and independents.
What we learned building NearOps
NearOps is our own white-label platform for service businesses, with engineers matched to jobs by location. Building it forced us to get specific about problems that sound simple in a specification.
Geography was the biggest one. Matching by radius produces results that look reasonable on a map and are useless in practice, because travel time bears little relationship to straight-line distance and engineers have preferences about where they will actually go. Coverage turned out to be something engineers should declare rather than something we should calculate.
The second was that an engineer-facing tool has to be worth using on its own merits. If it only becomes useful once there is plenty of work flowing through it, nobody stays long enough for that to happen.
Build or buy
There are mature field service management products and for a straightforward operation they are usually the right answer. We'll tell you when that is the case rather than taking on a build you don't need.
Building makes sense when something about how you operate doesn't fit the standard shape: an unusual dispatch model, a mix of employed and subcontracted engineers with different rules, work that requires specific compliance capture, or a customer-facing experience you want to own rather than rent. It also makes sense when you're paying per seat for a large field team and the maths has stopped working.
Work in this industry
NearOps
Service businesses run their bookings, dispatch, payments and payouts through NearOps under their own brand. Matching engineers to jobs by coverage area rather than a radius is the part that turned out to be hard.
Read Client build · Ecommerce, trade portal and reg lookupJF Automotive
For an automotive business, almost every enquiry starts with the same question - what car have you got? Answering it on the page instead of in an email changes the whole conversation.
ReadQuestions people actually ask
Do you build apps that work without signal?
Yes, and for field work it is essential rather than optional. Work gets captured on the device and synced when the connection returns, with conflicts handled sensibly rather than silently overwriting. The important design decision is which actions are allowed offline - some things genuinely should not happen without a live check, and pretending otherwise causes worse problems than a blocked screen.
How does location matching actually work?
We use declared coverage areas rather than a radius around a home address, based on postcode or ZIP data. A radius looks sensible and performs badly, because travel time doesn't track straight-line distance and engineers have real preferences about where they will travel. Letting them declare coverage produces far better matches for both sides.
Should we build or use an existing field service product?
If your operation is fairly standard, use the existing product - it will be cheaper and faster and we'll say so. Building earns its cost when something about your model doesn't fit the standard shape: an unusual dispatch arrangement, a mix of employed and subcontracted engineers, specific compliance capture, or a per-seat bill for a large field team that has stopped making sense.
Can customers book online themselves?
Yes, and it is usually the fastest return in the whole project. Online booking that understands real job durations, travel time and engineer availability removes most of the coordination calls from the office day. The important part is that it reflects genuine capacity - a booking system that promises slots you cannot deliver is worse than none.
What we would use
Custom Software
Most businesses outgrow their tools long before they replace them. Custom software is what you build when the spreadsheet, the shared inbox and three subscriptions have quietly become the process.
Web & Mobile Apps
Most business apps fail for boring reasons: they are slow on the phone the customer actually owns, they break on bad signal, or nobody could find them. We build for those conditions first.
Websites with Built-in Software
Most business websites are a brochure with a contact form. The ones that earn their keep let the customer do something - book, get a price, look something up, check a status.
Tell us what is slowing you down
A short conversation is usually enough for us to tell you what it would take to fix it, and what it would cost you to leave it alone.