The route that shouldn't have happened
Last September, a courier using DropPilot sent me a screenshot. Twenty-three stops across London. His original plan had him driving north to Finsbury Park, then backtracking south through the City, then west again. Traffic was thick. He was going to lose two hours. He punched in the new stop list, hit optimise, and watched the app reorder everything into a sensible loop. He finished at 4 PM instead of 6. That single afternoon felt like the entire reason we built this thing.
The problem nobody talks about until they're living it
Most delivery drivers I've met don't complain about the job itself. They complain about the work before the work. Someone hands them a list of addresses. That list is chaos. Stop one is in Shoreditch. Stop two is in Brixton. Stop three is back near Bethnal Green. They know the route is inefficient, but they're not route planners. They're drivers. So they spend the first hour of their day stitching together something sensible in their head, half-using Google Maps, half-using instinct.
Some dispatchers send jobs via email or spreadsheet in chunks throughout the day. Others use systems that spit out routes that make no geographical sense. A couple of customers told us they were manually rearranging addresses in a text file to save petrol. That was the moment I realised we weren't solving a nice-to-have. We were solving something that cost drivers money and time every single day.
What DropPilot actually does for your route
The optimisation engine uses nearest-neighbour routing plus 2-opt refinement. That's maths speak for: it finds a sensible starting point, then checks whether swapping the order of stops makes the journey shorter. The result is a route that respects geography, not just the order someone threw addresses at you.
But here's the thing that matters more: the route isn't static. Live traffic data streams in via Google Directions API. As you drive, DropPilot watches the traffic ahead. If you're about to hit congestion or if you've deviated from the planned route, it reroutes you automatically. Your ETAs refresh continuously. If a customer calls asking when you'll arrive, you've got an accurate answer. That was never true with a printed manifest or a static map.
The proof is in the capture
Once you arrive at a stop, you need proof. DropPilot lets drivers capture signature, take a photo, or leave notes. This isn't about being bureaucratic. It's about not having this conversation three days later when someone says they never got their package. With proof attached to each stop, there's no argument. There's a record.
For dispatchers managing multiple drivers or handling complaints, this changes the game. Instead of getting a phone call and having no idea whether the driver went to the address, you've got the data right there. Photo timestamped, signature captured, notes on the delivery.
Scaling from one driver to ten
When you're running deliveries solo, the app is your route planner and your record-keeper. When you've got a small team, things get complicated. You need to assign jobs to drivers, see where everyone is, handle changes when something goes wrong. That's where team dispatch comes in. Dispatchers can upload address lists via CSV, let the system plan optimal routes for each driver, and monitor everyone's progress in real time.
We built this because we watched small logistics teams and field service companies grow beyond the point where spreadsheets work, but they weren't ready to drop money on enterprise fleet management software that costs thousands a month. DropPilot sits in that middle ground. You get fleet visibility, team coordination, and route planning without the enterprise price tag.
Why we don't charge by the delivery
Early on, we had to decide how to price this. Per delivery? Per driver? Per stop? Those models make sense if you're a platform taking a cut. We're not. We're software. A driver brings their own jobs. We just help them plan the route and capture the proof. So we charge by how much you use the system: how many rounds per month, how many stops per round. The free tier gives you 5 rounds and 5 stops to try it. Plus tier gives you 30 rounds and 50 stops a month for £4.99. Pro is unlimited everything for £12.99. If you've got a team, Team tier is £49 a month with unlimited everything plus dispatch features.
We wanted pricing that felt fair whether you're a solo driver doing three deliveries a week or a small fleet doing a hundred stops a day. No surprise charges. No percentage of your earnings going to a platform.
What you get when the route just works
Efficiency gains aren't sexy until you're the one experiencing them. Less time on the road means more deliveries in a shift, or finishing earlier, or having time to actually eat lunch. It means lower fuel costs. For small operators, that's the difference between a good month and a bad one. For couriers in cities with congestion charges, it's the difference between entering the zone three times or once.
We've had drivers tell us they've gone from six to seven deliveries a day just by having routes that don't ping them across the city randomly. Others say they've cut petrol spend by a quarter. A food delivery driver told us he can now take on more orders from the same restaurants because his routes are more efficient.
That wasn't an accident. It was the point all along.
If your day starts with someone handing you a chaotic list of addresses, and you're spending the first hour of work untangling it, have you ever stopped to wonder how much that hour costs you in time and fuel? That's what DropPilot solves for.