NearOps: matching engineers to jobs by location
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.
What this is
NearOps is our second in-house product: a white-label platform for mobile field service teams. A service business takes bookings, dispatches engineers, manages coverage zones, syncs calendars, collects payments and tracks engineer payouts through it, all under its own brand.
Most service teams run that on calls, WhatsApp, a shared calendar, manual assignment and a payout spreadsheet. It works until it does not. Matching is driven by location, using postcode and ZIP lookup to work out who can realistically reach a job.
- Multi-tenant platform architecture, white-labelled per business
- Coverage-area matching using postcode and ZIP data
- Booking, dispatch and job flow
- Calendar sync, payments and engineer payouts
- Ongoing operation and support
Geography is harder than a radius
The obvious approach to matching engineers to jobs is a radius: find everyone within twenty miles. It fails immediately in the real world, because twenty miles across a city and twenty miles across open country are completely different propositions, and because a straight-line distance ignores whether there is a river, a motorway or a mountain in between.
It also ignores what engineers actually want. Coverage is not a circle around a home address - it is a set of areas someone is genuinely willing to travel to, which often follows road networks and personal preference rather than geometry. We built matching around declared coverage areas and real travel implications instead of a radius, which made the results dramatically more useful to both sides.
Where it is today
Worth being plain about the scale: five engineers on the platform, more than 2,300 completed jobs, and declared coverage reaching every county in the UK.
The jobs figure is the one that matters, because it means the booking, matching, payment and payout flow has been exercised properly rather than demonstrated.
What is in it
- White-label booking, branded per business
- Multi-tenant platform
- Coverage zones and location matching using postcode and ZIP lookup
- Engineer dispatch and job flow
- Google Calendar sync
- Stripe payments and engineer payouts
Where to go next
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.
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.
Software for Field Service and Trades
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.
Our product, sold to the trade · Garage management softwareRampDesk
Garages don't run a sales pipeline. They run vehicles through stages. RampDesk is the software we built because nothing off the shelf models that.
Want something like this?
Tell us what your business runs on and where it hurts. We'll tell you what it would take to build something similar for you.