The moment a delivery driver told me pen-and-paper was killing his day

The real problem isn't route planning. It's time.

Most delivery drivers know their patch. They've got the stopping points memorised. The problem isn't planning a route on a Monday morning. The problem is that every single day, something breaks that plan.

Traffic. A customer who cancels. A new job that comes in at 9.30am. A wrong turn because the satnav was glitching. A stop that takes twice as long as expected. By midday, half the route is in the bin.

We built DropPilot to handle that reality. The route optimisation engine (nearest-neighbour plus 2-opt algorithm) gets you a solid plan to start with. But the real work happens when you're out there. The app pulls live traffic data from Google Directions API and refreshes your ETA continuously. If you drift off the planned route, it detects that deviation and reroutes you automatically. No manual recalculation. No prayer.

That Tuesday morning courier? He's now finishing his round an hour earlier and handling two extra stops.

Dispatchers managing five drivers is different from managing fifty

When you've got a small team, you can text them changes. When you've got a fleet, that falls apart fast.

We built DropPilot so dispatchers could load a CSV file with fifty stops, let the system optimise them across drivers, and push the routes out in minutes. Each driver gets their own app. Each stop gets a sequence number. Proof of delivery comes back as a signature, a photo, or typed notes. The dispatcher sees everything in real time: who's finished what, who's running behind, where the fleet actually is.

One logistics manager told us this saved her team two hours of phone calls every morning. Two hours that now goes into handling exceptions and new bookings instead of playing traffic controller.

Food delivery, parcel couriers, and engineers all need the same thing

DropPilot isn't locked to one job type. A food delivery driver needs fast routes and proof of delivery. A field service engineer needs the same thing. A parcel courier running a double shift needs the same thing.

What they don't need is a platform that takes a cut. They don't need a consumer app on the other end tracking them. They need a tool that sits in their pocket, helps them plan their day, and gets proof of work back to whoever needs it. No commission. No marketplace. Just the app.

We've watched couriers use it. We've watched engineers use it. We've watched last-mile operators use it on rounds with thirty, forty, fifty stops. The feature set works the same way every time because the core problem is the same: how do you take a list of addresses and turn it into time saved and money kept?

The free tier lets you test this without risk

I built the free tier because I wanted field service people to actually try it. Five rounds a month, five stops per round. That's enough to run a small weekend delivery operation or test it before you sign your team up. The paid tiers are there for bigger operations: thirty rounds and fifty stops per round on Plus; unlimited rounds and stops on Pro. Team tier adds dispatch management and fleet features if you're running a crew.

But the reason for the free tier wasn't generosity. It was frustration. Too many tools assume you'll trust them with your operation before you've used them for five minutes. We didn't want that. Download it. Run a few deliveries. See if it actually saves you time. Then decide.

What we learned from launch week

On day one, we had three requests: one from a courier asking if we could show him the next three stops on one screen, one from a dispatcher asking if we could handle bulk address uploads, and one from an engineer who wanted to know if signatures auto-saved or if he had to upload them manually.

All three were live features by Friday. That's because this isn't a product built in a vacuum. Field service doesn't have time for software that makes assumptions. It needs tools that get out of the way and work the first time.

We've kept that momentum. When drivers hit a real pain point, we don't debate it. We build it. That's how CSV import happened. That's how continuous ETA refresh happened. That's how automatic rerouting happened.