Your London field team gets routed by ServiceTitan as if the Congestion Charge and ULEZ don't exist
Custom field service software in London typically runs £50k to £150k over 4 to 7 months. You build custom when scheduling and routing have to reckon with London's actual constraints, ULEZ, the Congestion Charge zone, parking, and travel times that off-the-shelf tools treat as a simple distance calculation. The trigger is when ServiceTitan's tidy route costs you money in charges and missed slots it never accounted for.
ServiceTitan, Jobber, and Housecall Pro schedule and route as if your engineers drive across open suburban grids. London isn't that. A route that looks efficient on distance can drag an engineer through the Congestion Charge zone twice, route a non-compliant van into ULEZ, or assume a fifteen-minute hop that's forty minutes in real traffic with nowhere to park. The off-the-shelf tool optimises a model of London that doesn't exist, and your dispatch team overrides it constantly with local knowledge the software lacks.
The cost is concrete. Charges you didn't budget for. Missed appointment windows because travel time was fantasy. Engineers stuck looking for parking on a job the system scheduled too tightly. For a London field-service operation, the gap between the routing tool's idea of the city and the real one is a daily tax on margin and customer satisfaction, and it grows with every van and every job.
What field service management costs in London
| Project scope | Typical cost | Timeline |
|---|---|---|
| Custom FSM with London-aware routing | £60k to £110k | 4 to 6 months |
| Full FSM platform with mobile app and live traffic | £100k to £150k | 5 to 7 months |
| Routing and scheduling module over existing FSM | £45k to £80k | 3 to 4 months |
The fix: field service management built for London, not rented
A London field-service operation has routing constraints, ULEZ, the Congestion Charge, real traffic, parking, that off-the-shelf tools built for open grids simply don't model. Custom field service software encodes the city your engineers actually drive: vehicle-aware routing that respects ULEZ compliance, charge-zone-aware scheduling, realistic travel times, and parking and access factored into job durations. Dispatch stops overriding the software with knowledge it should already have. Routes get cheaper and slots get hit because the system finally understands London.
- Routing ignores ULEZ and the Congestion Charge, costing you avoidable charges
- Appointment windows are missed because travel times are unrealistic
- Dispatch constantly overrides the tool with local knowledge
- Parking and access cause schedules to slip across the day
- You operate in a small area where ULEZ and the charge zone don't bite
- Your routing needs are simple and off-the-shelf estimates are good enough
- Job volume is low enough that manual dispatch handles the edge cases
- You can't sustain maintaining London-specific routing rules
The capability list that earns its budget
London field service management: the full scope
Digital Heroes builds the full field service management stack for London teams. Typical engagements cover dispatch software, work order management, technician scheduling, mobile field app, ServiceTitan alternative, Jobber alternative and route optimization.
How long it takes, phase by phase
Exactly what you get
Field service software that understands the city your engineers actually work in. Routing that knows which vans are ULEZ-compliant and which routes cross the Congestion Charge zone, scheduling that uses realistic London travel times instead of open-road fantasy, and job durations that factor in parking and access. Engineers get a mobile app with London-aware navigation; dispatch gets a board that shows charge exposure and slot risk per route. The local knowledge your team uses to override the system gets built into the software instead.
How to choose a developer in London
Hire a team that takes London's routing reality seriously, ULEZ, the Congestion Charge, real traffic, parking, because that's the entire reason off-the-shelf tools fall short here. Ask how they'd keep the charge and ULEZ rules current, and how they'd capture the overrides your dispatch team makes today. A partner who treats routing as plain distance will rebuild the problem. Connect the build to your CRM (Customer Relationship Management), inventory management software, and helpdesk software so jobs, parts, and customer history flow to the engineer at the door.
- Vehicle-aware routing that respects ULEZ compliance and avoids needless charges
- Congestion-Charge-aware scheduling that stops vans crossing the zone twice
- Realistic London travel times so appointment windows actually get met
- Parking and access factored into job durations, ending too-tight scheduling
- Dispatch trusts the system instead of overriding it with local knowledge
- Encoding London's routing rules and keeping them current as ULEZ and charges change is ongoing work
- Live traffic and mapping data integration adds cost and dependency
- Higher up-front spend than Jobber, justified by charge savings and hit slots
- A small operation in one area with simple routing may not need this
- !They treat routing as plain distance; ask how they handle ULEZ and the charge zone
- !Travel times assume open roads; ask how they use live London traffic data
- !No engineer mobile app plan; ask how field staff get London-aware navigation
- !They ignore parking; ask how access realities affect their scheduling
- !Quote without ride-alongs; ask how they'll learn your real dispatch overrides
Most London teams pricing field service management end up comparing notes on lms, crm, shopify too; the systems share one data spine.
Rohan advises mid-market and enterprise teams on ERP, CRM and custom software, and has led delivery on dozens of business-software builds.
Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
Why does ServiceTitan route our vans badly in London?
Tools like ServiceTitan optimise on distance and assume open road networks. London adds ULEZ compliance, the Congestion Charge zone, dense traffic, and parking, none of which they model. So a route that looks efficient incurs avoidable charges and misses slots. Custom software encodes those constraints.
Can the software keep up with ULEZ and charge changes?
Yes, if it's designed to. The charge and ULEZ rules live in a maintained configuration so that when zones or rates change, the routing updates centrally. This ongoing maintenance is part of the trade-off versus an off-the-shelf tool.
How does it stop missed appointment windows?
By modelling realistic London travel times from live traffic data and factoring in parking and access, so slots are scheduled against reality rather than optimistic distance estimates. That's what closes the gap between the planned route and the engineer's actual day.
Do engineers get a mobile app?
A good build includes one, giving field staff London-aware navigation, full job detail, parts, and the customer history they need at the door. The app is also how completed-job data flows back without paperwork.
How long does an FSM build take?
Four to seven months. A routing and scheduling module over an existing FSM lands in three to four; a full platform with a mobile app and live traffic runs five to seven. The London routing logic drives most of the timeline.