Insight
Why hyperlocal delivery needs better infrastructure, not more riders
Last-mile delivery in small cities fails on utilisation, not on supply. Batch routing across categories is the structural fix — and it is only available to platforms that run more than one category.
In short
Hyperlocal delivery infrastructure is the dispatch, routing and proof-of-delivery layer that lets many businesses share one courier fleet. Batch routing — assigning several pickups and drops to one optimised run — is what makes last-mile economics viable outside dense metros.
The real constraint is idle time
A courier's cost is time, not distance. In a metro, a single-category platform can keep a rider busy because order density is high enough. In a city of a few hundred thousand people, one category cannot. The rider spends most of the shift waiting.
Adding more riders makes this worse, not better. The fix is raising orders per rider-hour, and the only structural way to do that in a small city is to pool demand from several categories onto the same fleet.
How batch routing changes the arithmetic
Dispatching one rider per order means each delivery carries the full cost of a trip. Batching groups nearby pickups and drops into one optimised route, so a single run can serve five stops. The cost per drop falls roughly with the number of stops that can be sequenced without breaking the promised delivery window.
The constraint is time-window feasibility, which is why the routing has to be intelligent rather than naive. A medicine delivery with a tight window cannot be batched behind three laundry pickups; the system has to know which combinations are legal before it assigns.
| Dispatch model | Stops per run | Relative cost per drop | Works below metro density |
|---|---|---|---|
| One rider per order | 1 | Baseline | No |
| Zone pooling, one category | 2–3 | Lower | Marginal |
| Cross-category batch routing | 4–6 | Lowest | Yes |
Reliability is the product, not speed
Consumer delivery brands compete on speed because it is legible in marketing. Infrastructure competes on reliability, because the buyer is a business whose reputation is on the line.
That is the design choice behind Deelo Runner. It is a managed network rather than an open gig pool: assignment is deterministic, handover is OTP-verified at both ends, tracking is live, and deliveries can be scheduled rather than only immediate. A shop can promise a customer a window and have that promise hold.
Frequently asked questions
How does batch delivery lower cost without lowering service?
By sequencing only those stops whose delivery windows are compatible. The router checks feasibility before assigning, so batching adds stops to an existing trip rather than delaying any single one. Cost per drop falls because the fixed cost of the trip is shared.
Why can't a single-category app do this?
Because it only has one demand curve. Groceries peak in the evening, medicine is spread through the day, laundry is scheduled, parcels are ad hoc. A platform running several categories can fill one category's troughs with another's demand; a single-category app has nothing to fill them with.
Related reading
- Why hyperlocal commerce is a platform opportunity, not an app oneA hyperlocal commerce platform is infrastructure that lets any local business sell, fulfil and retain customer…
- The local commerce operating system, explainedA local commerce operating system is a single software layer that runs a local business end to end — catalogue…
- Network effects in local commerce, and the one most models missLocal commerce marketplaces have three network effects: the two-sided effect between supply and demand, the de…
Reviewing Deelo as an investment?
The full investor deck runs as a single scrolling brief — problem, solution, product, market, model, financials and team.