Running a small fleet? Here's how DropPilot handles the chaos

The dispatcher's burden

Most dispatch tools are either sprawling enterprise software that costs a fortune or delivery marketplaces designed for platforms, not for independent teams or small courier services. We noticed a gap: what about the manager of a five-driver operation who needs to assign jobs quickly, see live positions, and know when packages will arrive?

In DropPilot, a dispatcher imports addresses via CSV. Bulk upload, no manual entry for each stop. The app then clusters and optimises those stops across multiple drivers using nearest-neighbour routing plus 2-opt refinement. Real-world traffic patterns feed in via Google Directions API, so ETAs aren't guesses; they update continuously as conditions change. A driver hits unexpected congestion, the route reroutes automatically. A dispatcher can see all of it happening.

What matters is visibility and control. The dispatcher isn't guessing whether a driver will finish by 5pm. They're watching live positions, refreshing ETAs, and if something's gone wrong, they already know.

Routes that adjust, not rigid plans

Early versions of DropPilot had static routes. A driver would complete them as assigned, end of story. Then a real courier sent us a screenshot from the field: "My planned route took me down a closed road. I had to deviate." We'd built detection for exactly this, but the system wasn't rerouting smartly enough.

Now, the moment a driver deviates from the planned sequence, DropPilot detects it and suggests a rerouted path using the remaining stops and live traffic conditions. The dispatcher sees the deviation flag. If it's sensible, they let it stand. If the driver took a wrong turn, they can reoptimise immediately.

That matters because dispatch isn't about forcing drivers into predetermined sequences. It's about ensuring they can deliver all their stops efficiently, and the team can account for reality as it unfolds. A roadworks closure, a customer who asks for a later slot, or a traffic jam shouldn't derail the entire day.

Proof, not faith

A delivery isn't complete until there's proof. DropPilot lets drivers capture a signature, take a photo, or leave notes at each stop. The proof uploads as part of the completion data, so dispatchers and clients see evidence of delivery without a separate system.

We've found this simple feature cuts disputes in half. A customer claims they never received a package; a photo timestamp and a signature screen tell the real story. For food delivery or time-sensitive parcels, that record is worth the thirty seconds it takes to capture.

The proof doesn't need to be elaborate. A note saying "left with neighbour, green door" is often enough. The signature optional. It's there when you need it, unobtrusive when you don't.

Team versus solo

DropPilot has a free tier: five delivery rounds per month, five stops per round. Enough for a solo driver or someone testing the water. The Plus tier gives thirty rounds and fifty stops per round; suitable for a driver doing serious work. The Pro tier opens unlimited rounds and stops, no ceiling.

But a team needs more. The Team tier adds multi-user dispatch: a manager can assign routes to multiple drivers, see the fleet map live, and pull analytics on how many deliveries happened, where the bottlenecks are, and how long stops typically take. The dispatcher doesn't need to be out in the van; they're running the operation from an office or laptop.

For larger operations, Enterprise tiers offer custom terms. The point isn't that we've built a one-size-fits-all product. It's that we've built a product for people who own their own deliveries, not for platforms that aggregate and resell them.

Real-time, real decisions

Live traffic integration sounds straightforward until you're actually running it. A driver's ETA changes as they move. Sometimes it gets better, sometimes worse. We refresh it continuously so dispatchers and customers see the same number. If a stop is suddenly going to be thirty minutes late, the dispatcher and driver know together. They can decide whether to skip a low-priority job, notify the customer, or reorder the remaining stops.

That responsiveness is what separates dispatch from prediction. You're not planning the entire day on the office wall. You're adapting in real time as it unfolds, with everyone seeing the same data.

Why this matters for your operation

Whether you're a courier service, a field technician with multiple jobs, a food delivery driver working multiple platforms, or a logistics team managing last-mile deliveries, the core problem is the same: how do you get people and packages from A to B to C efficiently, without losing track of where anyone is or whether the job's done?

DropPilot doesn't take a cut of your earnings or sit between you and your customers. It's a tool your team uses. A dispatcher assigns routes via CSV. Drivers see optimised stops with live traffic. Proof of delivery attaches to each completion. Everyone knows where things stand. That's the whole point.