The feature that changed how we thought about delivery routing

The problem we didn't know we had

When we launched DropPilot, the core idea was simple. A driver gets a list of stops. We work out the best order. They follow the route, capture a signature or photo at each drop, and move on. It solved a real problem for solo operators and small teams.

But there's a gap between theory and reality. Most couriers, field service technicians, and fleet operations aren't solo. They have drivers. Someone needs to assign jobs to those drivers. Someone needs to know where they are. Someone needs to handle what happens when a driver is stuck in traffic, or needs to pick up a new job mid-round, or hasn't arrived at the next stop in forty minutes.

We received roughly fifteen messages like Sarah's in the first two months. Dispatchers, fleet managers, and operations coordinators wanted to use DropPilot, but they needed a way to oversee multiple drivers at once. They needed to be able to send routes to their team and see where everyone was in real time.

Why one tool beats two

The easy answer would have been to tell people to use spreadsheets alongside DropPilot, or to point them toward a separate fleet management platform. We didn't do that for a reason.

A dispatcher managing four drivers shouldn't need to open three different apps. One person logs into DropPilot, imports a CSV of their addresses for the day, and the system assigns stops to drivers based on what makes sense geographically and by workload. Each driver then follows their optimised route with live traffic updates, continuous ETA recalculation, and smart rerouting if they deviate. The dispatcher can see the whole operation in one place. Real time locations. Progress on each delivery. Proof of delivery arriving as it happens.

When a driver gets held up in traffic, the system detects the deviation and suggests a new route. When a new urgent job comes in, the dispatcher can assign it and the driver's route recalculates. There's no context switching. No manually updating spreadsheets. No guessing whether Susan's actually at the next stop or if the GPS data is three minutes old.

What we learned building it

We spent three months on team dispatch and fleet management. Most of that time wasn't spent on the clever bits. It was spent on the small, annoying, real-world details that matter when you're actually managing people.

Can a dispatcher see which driver is currently on their tenth delivery and might be approaching their limit? Yes. Can they pause a route, add a stop, and have it slot into the right position without breaking the optimisation? Yes. Can a driver see they've been assigned a new job and choose to accept or decline it before their current stop? Yes. Can the system capture proof of delivery in whatever format matters, whether that's a signature, a photo, or just a note, and attach it to the right delivery record? Yes.

We also learned that not every operation works the same way. A food delivery driver operates differently from a field service technician. A logistics team moving parcels operates differently from both. So we built DropPilot flexible enough to handle those differences without becoming so flexible that it's overwhelming. CSV bulk import, multi-stop optimisation with nearest-neighbour and 2-opt logic, live Google Directions integration for traffic awareness, and continuous ETA refresh. These aren't flashy features. They're the things that keep a delivery operation from falling apart at 3pm on a Thursday.

Who it's actually for

We released team dispatch in June. Within a month, we had courier services, logistics teams, and field service operations using it. Not startups. Not glossy tech companies. People who move things for a living and needed a tool that worked.

A solo driver can still use the free tier. Five rounds a month, five stops per round, completely free. They plan a route, drive it, capture proof of delivery. Their cost is zero. A dispatcher managing a small team can use the Team tier, which gives them unlimited rounds and stops, team management, and the dispatch interface. A larger fleet operation that needs custom setup or integrations can talk to us about Enterprise.

What matters is that the tool fits the work, not the other way around. A courier in Liverpool shouldn't have to learn enterprise software because she wants to manage her three drivers efficiently. A field technician shouldn't have to pay for features they don't use.

The conversation that mattered

Sarah messaged us again in August. She was using DropPilot Team with her three drivers. She said the biggest change was that she stopped worrying about whether people were where they said they were. The system showed her. She stopped spending forty minutes a day updating spreadsheets. The drivers did. She spent that time handling calls from clients or planning the next day's routes. Her drivers completed more drops per day because the routes were optimised and they weren't getting stuck following a suboptimal path.

That message probably matters more than any metric we track. It wasn't that the feature was clever. It was that it removed friction from an actual job. The route optimisation means fewer miles. The live traffic awareness means better ETAs. The proof of delivery means fewer disputes. The team dispatch means fewer hours spent coordinating. Those things add up. They matter to people who depend on reliable delivery operations.