Every delivery or field service operation hits the same wall eventually. The spreadsheets stop scaling at 15-20 stops a day. The SaaS tool you signed up for nearly fits, but not quite. Dispatch planning still takes an hour each morning. Drivers call in because the app sent them through a low bridge or into a ULEZ zone their van cannot enter.
We build route planning software that matches how your operation actually works, not how a SaaS product assumes it should.
Why off-the-shelf route planning software falls short
There are over 30 commercial route planning tools on the market. Most of them share the same set of problems:
-
Pricing that scales against you. Per-driver models (typically £30-50 per user per month) mean your software bill grows every time you add a vehicle. Live tracking, customer SMS notifications, and advanced reporting are often paid add-ons that double the headline price. A 10-vehicle operation can easily spend £21,000-36,000 over three years before factoring in setup and integration costs.
-
Rigid workflows that do not bend. Most tools assume a standard delivery workflow: orders in, routes out, stops completed. If your operation involves skill-based job allocation, multi-depot vehicle management, hazmat restrictions, zone-based driver assignment, or emergency callout handling, you are either paying for an enterprise tier or building workarounds in spreadsheets.
-
Poor integration with what you already run. SaaS route planners are built for Shopify-to-delivery pipelines. If your orders come from a Sage ERP, a custom warehouse system, or a legacy database, you are looking at expensive middleware, manual CSV imports, or Zapier chains that break under load. Pushing delivery status back to the source system is a common pain point: your order management portal stays out of sync while someone re-keys data at the end of the day.
-
Black-box optimisation. The routing algorithm decides the stop sequence, but you cannot see why. Dispatchers distrust routes that look inefficient. Drivers override the app. Nobody can tune the logic to account for rules like “keep drivers near their depot at end of day” or “avoid assigning new starters to high-value deliveries.”
-
US-centric defaults. Most commercial platforms are US-headquartered with US-hosted data. UK-specific requirements like ULEZ and Clean Air Zone compliance, HGV route restrictions, accurate postcode coverage, and low bridge data are afterthoughts rather than foundations. GDPR compliance depends on a Data Processing Agreement rather than genuine UK or EU data residency.
-
Locked-in and locked out. Data export is limited. Custom fields do not map to your business. Switching vendors means starting from scratch. And if the vendor gets acquired, changes pricing, or sunsets a feature, your operation is exposed.
The workarounds accumulate. Spreadsheets appear alongside the dashboard. Someone re-types data between systems. Eventually the software gets quietly abandoned and dispatch goes back to phone calls and gut feel.
What we build instead
We start by mapping your current workflow: how jobs arrive, how dispatchers allocate work, what constraints your drivers actually face, and which systems need to talk to each other. Then we build software that fits that reality rather than forcing you to adapt to ours.
You pay once for the build, not per driver, per stop, or per month. There are no seat fees, no usage tiers, no feature paywalls. Adding five more vans does not change your software costs. For operations running 20+ vehicles, this pricing model typically pays for itself within two to three years compared to SaaS subscriptions.
The optimisation logic is transparent and tuneable. We build on proven open-source routing engines (OSRM, GraphHopper) and constraint solvers (Vroom, jsprit) rather than licensing a black-box algorithm. This means we can encode your actual business rules directly into the solver: driver zones, vehicle restrictions, skill matching, customer priority, depot stagger times. And when dispatchers question a route, we can explain exactly why stops are sequenced that way.
Integrations are built in, not bolted on. The system connects to your ERP, accounting software, CRM, warehouse management, or telematics platform through proper APIs. Order data flows in. Delivery status flows back. No re-keying, no CSV imports, no Zapier workarounds that fail at peak volume.
UK rules sit in the foundation. ULEZ and Clean Air Zone restrictions, low bridge heights, weight limits, HGV-prohibited routes, and accurate postcode coverage are part of the core map data, not an afterthought. GDPR-compliant data handling with UK or EU hosting is the default, not a premium add-on.
The architecture is modular. Adding EV routing constraints, a customer-facing tracking portal, dynamic re-optimisation, or a new depot later does not require a rebuild. And the team you work with during the project is the same team that answers the phone after go-live, in London, in your time zone.
Features we typically build
Every project is shaped to the client, but most include some combination of these:
Route optimisation and dispatch
- Multi-stop route generation accounting for traffic, vehicle capacity, time windows, stop priority, and driver skills
- Automated dispatch that allocates jobs by location, availability, vehicle type, and qualifications
- Dynamic re-optimisation when jobs cancel, urgent work comes in, or traffic shifts mid-day
- Multi-depot support with vehicle-specific constraints (weight, size, hazmat, refrigeration)
- Zone and territory management with driver assignment rules
Driver mobile app
- Turn-by-turn navigation with UK-specific restrictions (low bridges, weight limits, ULEZ zones)
- Proof of delivery with photo capture, signature, barcode scanning
- Offline mode that syncs when connection is restored
- Two-way communication with dispatch
Live tracking and visibility
- Real-time vehicle tracking with ETAs and delay alerts
- Customer-facing tracking links with SMS or email notifications
- Geofence-based triggers (depot arrival, customer site entry, zone breach)
- Driver behaviour monitoring: speeding, harsh braking, idle time
Reporting and analytics
- Mileage, fuel consumption, cost per delivery, and on-time performance dashboards
- Driver productivity and vehicle utilisation metrics
- SLA compliance and exception reporting (late deliveries, missed windows)
- Environmental reporting: CO2 per route for ESG requirements
- Custom report builder with export
Integrations
- E-commerce platforms (Shopify, WooCommerce) for order import
- ERP and accounting (Sage, Xero, SAP) for invoicing and cost tracking
- CRM (HubSpot, Salesforce) for customer data
- Telematics and fleet management systems
- Warehouse management for load planning
- Webhook and API support for custom system connections
Compliance and security
- UK GDPR data handling with immutable audit trails
- UK or EU data hosting, or on-premise deployment
- Role-based access for dispatchers, managers, drivers, and customers
- Working Time Directive integration for driver hours monitoring
- Data subject access request and right-to-erasure workflows
How a project usually runs
Discovery and planning (2-3 weeks). We sit with dispatchers, drivers, and managers. We watch the current process, map how jobs flow through the operation, document the constraints that matter, and define what success looks like in numbers. We identify which integrations are needed and what data needs migrating: customer records, vehicle fleet details, driver skills and certifications, and address data.
Development (8-12 weeks for MVP). Our UK team builds the system in fortnightly cycles. You review working software every two weeks and give feedback as we go, not at the end. A typical first phase delivers route optimisation, a dispatch interface, a driver mobile app, live tracking, basic reporting, and your most critical integration.
Testing and rollout (2-4 weeks). We run the new system against real scenarios and do user acceptance trials. Rollout happens in phases, usually starting with a pilot on 5-10 routes before going live across the fleet. We run the new system in parallel with the old process until everyone is confident.
Training and handover. Dispatchers get 2-4 hours of training on the web interface. Drivers get 1-2 hours on the mobile app. IT teams get API integration and troubleshooting sessions. We provide documentation and video walkthroughs alongside on-site training where useful.
Post-launch support. Twelve months of support and updates are included. After that, you can carry on with a support contract or take it in-house. You own the code either way.
Total timeline is usually three to six months from first conversation to a live system. Simple, single-depot builds finish faster. Complex multi-site implementations with deep ERP integration can take longer.
What it costs and why
Custom development costs more upfront than a SaaS subscription. The economics shift around the two to three year mark.
A typical MVP (route optimisation, dispatch interface, driver app, live tracking, basic reporting, one key integration) costs in the region of £20,000-50,000. A full-featured build with dynamic routing, multi-depot support, advanced analytics, customer portals, and deep system integrations runs £50,000-150,000 depending on scope.
For context, a mid-market SaaS tool for 10 vehicles typically costs £18,000-36,000 over three years in subscription fees alone, before setup, integration work, and add-ons for features like live tracking and customer notifications. At 50 vehicles, SaaS costs can reach £2,000-2,500 per month. A custom build has near-zero marginal cost per additional vehicle after the initial development.
After the build, there are no per-seat fees, no per-stop charges, no feature paywalls. You own the IP. You can change the software whenever the business changes. We give you a fixed estimate after the discovery conversation, not before.
Where this kind of software gets used
Custom route planning tends to pay off anywhere mobile work is the core of the operation:
-
Last-mile delivery and e-commerce fulfilment. High order volumes, tight delivery windows, same-day demand spikes. Route optimisation reduces cost per delivery; dynamic routing handles volume surges without adding headcount.
-
Courier and parcel networks. Multi-drop routes with 200+ stops per vehicle per day. ULEZ and Clean Air Zone compliance, working time regulations, and competitive pricing pressure make generic tools inadequate.
-
Field service teams. Engineers, inspectors, maintenance crews scheduled by skill, certification, and SLA. Time-window constraints and emergency callout handling need more than a standard delivery workflow.
-
Community healthcare. District nurses and care workers routed by patient priority, visit duration, and continuity of carer. NHS data handling requirements often rule out US-hosted SaaS platforms.
-
Waste collection and recycling. Fixed collection rounds with dynamic capacity constraints, bin fill-level monitoring, and environmental compliance reporting for landfill diversion.
-
Food and pharmacy delivery. Temperature-controlled routing, tight time windows (30-45 minutes for food, strict chain-of-custody for prescriptions), and customer notification requirements.
-
Retail distribution. Multi-depot load balancing across store networks, mixed urban and rural routes, and integration with inventory management systems.
-
Utilities. Emergency callouts mixed with planned maintenance, geographic dispersion, technician certification matching, and offline capability for rural areas.
-
Local authorities. Recycling, street cleaning, social care rounds, and school transport. UK public sector procurement often requires on-premise or UK-hosted solutions.
-
Construction and plant logistics. Moving equipment and materials between sites with vehicle-specific routing (oversized loads, weight restrictions) and site access scheduling.
Each sector brings its own constraints, compliance rules, vehicle types, and customer communication needs. Those get built into the system from day one rather than approximated by a generic workflow.
Common Questions About Custom Route Planning Software
How does custom development cost compare to SaaS route planning tools?
SaaS route planning typically costs £30-50 per driver per month, plus add-ons for live tracking, customer notifications, and advanced reporting that can double the headline price. A 10-vehicle operation might spend £18,000-36,000 over three years on SaaS subscriptions alone. Custom development costs more upfront (an MVP typically starts around £20,000-50,000), but there are no per-driver or per-stop fees afterwards. For operations with 20+ vehicles, total cost of ownership usually favours a custom build within two to three years.
What's the typical development timeline?
A working MVP with route optimisation, a dispatch interface, a driver app, and live tracking usually takes 8-12 weeks. Phase two work like dynamic re-optimisation, multi-depot support, customer tracking portals, and deeper integrations with ERP or accounting systems typically adds another 8-16 weeks. We give you a fixed timeline estimate after the discovery conversation.
How do you handle updates and changes after launch?
All builds include 12 months of support and updates. After that, we offer flexible support contracts or can hand over to your IT team. Because you own the code, you are never locked into our services. Changes to business rules, new vehicle types, or additional integrations can be made at any point without waiting for a SaaS vendor's product roadmap.
Can you integrate with our existing systems?
Yes. We regularly connect route planning builds with telematics providers, ERP systems (Sage, SAP, Xero), e-commerce platforms (Shopify, WooCommerce), CRM tools, and warehouse management systems. We build API-first, so data flows between systems in real time rather than through CSV exports or manual re-keying.
What about data security and GDPR compliance?
We build all solutions to UK GDPR standards with encryption, role-based access controls, and immutable audit trails. Unlike most SaaS route planning tools which default to US-hosted infrastructure, we can deploy on UK or EU servers, or on-premise if your compliance requirements demand it. This matters particularly for NHS logistics, local authority work, and any operation handling sensitive customer location data.
Do you provide training for our team?
Yes. Dispatchers typically need 2-4 hours of training on the web interface, while drivers need 1-2 hours on the mobile app. We provide documentation, video walkthroughs, and on-site sessions where useful. We also support IT teams with API integration and webhook configuration training.
What routing and optimisation technology do you use?
We build on proven open-source foundations like OSRM or GraphHopper for routing, paired with VRP solvers like Vroom or jsprit for constraint-based optimisation. This avoids vendor lock-in and gives us full control over the algorithm. Unlike SaaS black-box routing, we can tune the optimisation logic to match your specific priorities, whether that is minimising fuel cost, respecting driver zones, or meeting customer time windows.