The maths that keeps your delivery day moving

Why the order of your stops matters more than you'd think

Most delivery apps show you a list of addresses and leave the rest to you. That works fine if you've got three stops. But when you're managing 20, 30, or 50 addresses across a city, the difference between a decent route and a chaotic one isn't luck. It's maths.

DropPilot starts with what's called nearest-neighbour optimisation. In plain terms: after your current location, the app looks at every remaining stop and picks the closest one. It repeats that process for each subsequent pickup or drop-off. This gets you a workable route fast, which matters because dispatchers or drivers often need to plan on the fly, not spend half an hour in calculation.

But nearest-neighbour alone leaves money on the table. Picture yourself two hours into a route and realising you've crossed the same street four times. So we layer on 2-opt refinement, which essentially asks, 'If I swap the order of these two stops, do I save distance?' The algorithm runs through promising swaps and locks in the shortest version. It's not a guarantee of perfection, but it catches the obvious inefficiencies that cost you time and fuel.

When the traffic lights change, so does your route

A planned route is only a plan. Five minutes into your delivery day, roadworks close a main street. A delivery van breaks down two junctions ahead. The weather shifts and gridlock tightens around the city centre. Your ETA that made sense at 9am is useless by 10.

DropPilot talks to Google Directions API constantly. Not just once when you start, but as you move through your day. It pulls live traffic data and recalculates your ETA to each remaining stop every few minutes. You see that in the app: your times shift in real time as conditions change.

It goes one step further. If you drift meaningfully off your planned route, the app detects that and offers a recalculated route based on where you actually are right now. A driver last week ran into unexpected congestion on their way to a stop and took a detour. The app saw the deviation, paused, and handed back a new route from their current position that still got them through their remaining 12 stops efficiently. They didn't have to think about it. The app just knew.

Scaling from 5 stops to 50 without breaking your workflow

We built DropPilot for solo drivers first. You take a day's work, load it into the app, and go. But we quickly learned that couriers and small logistics teams often manage multiple drivers. A dispatcher in Manchester might be sending out four vans. Each driver brings back their own set of deliveries. Without a way to bulk-load addresses, the dispatcher ends up typing them in one by one, which is fine for five but becomes a nightmare at 50.

That's why we added CSV import. A dispatcher can export a list from their system or spreadsheet, upload it to DropPilot, and the app carves it into sensible rounds, assigns drivers, and each driver gets their optimised route ready to go. We've seen teams cut their dispatch prep time from 45 minutes to about eight minutes using that feature alone.

The free tier lets you test the workflow with 5 stops per round, 5 rounds a month. If you're running a single van and want more capacity, the Plus tier opens up to 50 stops per round and 30 rounds monthly. For teams that dispatch multiple drivers or run daily operations, the Pro tier removes all limits. If you're managing a fleet across multiple locations, there's a Team tier that adds proper dispatch controls and user management.

Proof matters more than you'd think

Once you arrive at a stop, the work isn't done. The customer wants to know it's been delivered. Your company wants to know it happened. So DropPilot lets you capture proof right there in the app: a signature, a photo, or typed notes. That record stays attached to the delivery and is there when questions arise later.

We added that because we kept hearing from drivers and dispatchers that proof of delivery was essential but usually clunky. You'd have to use a separate app, fill out a form, send photos later. With DropPilot, it's one screen. Mark the stop complete, capture your proof, move to the next address. The dispatcher sees it come through in real time on their end.

The gap between plan and reality

The hardest part of building a route planner wasn't the algorithm. It was understanding that a driver isn't a robot following a fixed sequence. You take a wrong turn. A customer isn't home. You pick up an extra job while you're out. A traffic jam reshuffles everything.

We designed DropPilot around that reality. The optimisation gets you to a smart starting point. The live traffic keeps you moving. The deviation detection and rerouting mean you're not locked into a plan that's already obsolete. And because dispatchers can load entire days at once and drivers can see what's coming, there's room for thinking and decision-making rather than just execution.

Marcus understood that instinctively. He wasn't using DropPilot as a set-it-and-forget-it system. He was rerouting himself when conditions changed, trusting that the app's suggestions were sound because they were based on live data and actual road conditions, not a calculation made hours before.