Dispatch Network has raised ₹5 crore in pre-seed funding to expand its AI team and develop a proprietary Large Logistics Spatio-Temporal Model, or LLSTM. The Pune-based startup wants that model to improve order allocation, delivery routes and rider productivity across intracity logistics.
Antler India led the round, with participation from angel investors Krishi Fagwani, founder of Thrive, Yashin Mahadevia and Parth Modwadhia. Entrackr reported the financing on November 2, 2026, citing a company press release. The investment amounts to ₹50 million.
Dispatch already operates a delivery network in Pune and says its system assigns orders across multiple platforms. The funding is intended to expand the AI work behind that operation. The useful distinction is between an operating delivery service, a company-described decision model and the broader foundation-model capability Dispatch wants to build.
What the LLSTM Is Supposed to Do
Dispatch describes the LLSTM as a foundation model for intracity logistics and mobility. According to Indian Startup News, the company says it learns from a minute-by-minute view of the city, assigns every order Dispatch delivers and uses each decision and its outcome as training data.
That description puts three connected decisions at the center of the system:
- Order allocation: Which rider should receive a particular delivery?
- Work sequencing: Which order should that rider take next?
- Positioning: Where should the rider wait for another assignment?
Co-founder Navneeth Kannan described the ambition this way:
“We're building the decision layer for last-mile delivery: which order, which rider, and where they should be next.”
“Spatio-temporal” refers to space and time. A useful assignment depends on where riders, pickups and destinations are, alongside when an order becomes available and when a rider can serve it. The shortest journey to one pickup may leave a rider poorly positioned for subsequent work.
The published accounts provide a high-level description, but no architecture, training-data specification, benchmark methodology or clear boundary between the deployed system and the planned LLSTM development. They also provide no independent performance measurements. The foundation-model label is therefore Dispatch’s characterization; the available evidence cannot establish its technical scope or maturity.
My view is that the decision sequence matters more than the model name at this stage. Choosing a rider’s next two useful moves could have operational value even before the company demonstrates a broadly reusable logistics foundation model.
Why the Next Order Matters More Than One Short Route
Dispatch’s immediate target is the distance riders travel without carrying an order, often called empty kilometres. Those journeys consume fuel or battery charge, vehicle life and working time without directly producing delivery revenue.
The company estimates that riders can travel up to half their kilometres without an order, according to Indian Startup News. That is Dispatch’s description of the problem, not an independently established industry-wide rate.
Dispatch says it addresses this by sequencing work across platforms and centrally assigning orders to individual riders. It reports serving food delivery and quick-commerce businesses including Zomato, Swiggy, Zepto, Instamart and BigBasket, alongside restaurants and stores through direct APIs and the Open Network for Digital Commerce, or ONDC.
Consider an illustrative assignment decision. One available order might offer a nearby pickup but end far from likely demand. Another might take slightly longer to collect yet finish close to the next cluster of pickups. A system optimizing several consecutive jobs could prefer the second option, provided the delivery commitments still work.
That example explains Dispatch’s proposition; it is not a disclosed result from its model.
Cross-platform sequencing could help when demand peaks and quiet periods differ between services. Its usefulness depends on having sufficiently fresh information about available orders and rider availability. A prediction has limited operational value if the system learns about an order too late or cannot assign it.
Central allocation also makes the quality of the decision consequential for riders. I’d want any productivity assessment to examine who receives the longer pickups, less convenient destinations and waiting time, alongside the network-wide average.
Route Optimization Is Only Part of the Comparison
Dispatch’s pitch extends beyond choosing roads between fixed stops. It includes deciding which work to allocate and where riders should position themselves afterward.
That distinction should not become a claim that conventional route optimization is always static. Allocation, scheduling, demand prediction and routing can be combined in logistics systems without using a model branded as a foundation model. The financing reports supply no like-for-like comparison showing which component of Dispatch’s approach produces its claimed gains.
A meaningful comparison would hold operating conditions reasonably steady: similar order demand, rider availability, service areas and delivery commitments. It would then examine completed orders per rider-hour, empty distance and delivery reliability.
Lower empty distance alone would be an incomplete result if it came with longer customer waits or more missed delivery windows. Likewise, higher order throughput would need to be assessed against rider hours and workload.
This is the important test for a vertical AI business: whether its domain-specific decisions improve the operating outcome under clear constraints. The model’s branding cannot answer that.
The Scale Target Is About 14 Times Today’s Reported Volume
Dispatch says it has completed more than 100,000 deliveries since launching in Pune in June 2026. Its next stated goal is 50,000 orders per day across five cities.
Entrackr’s report gives the following company-reported figures:
| Measure | Reported volume | Status |
|---|---|---|
| June 2026 deliveries | 3,014 | Reported monthly total |
| October 2026 deliveries | 55,000 | Reported monthly total |
| Daily deliveries at announcement | About 3,500 | Reported current rate |
| Planned daily orders | 50,000 | Company target |
| Planned geographic footprint | Five cities | Company target |
October’s monthly total was approximately 18.2 times June’s. Reaching 50,000 daily orders from the reported 3,500 daily rate would require approximately 14.3 times the volume. Those are calculations from Dispatch’s figures, not additional company milestones.
The monthly totals and current daily rate cover different reporting windows, so they should not be treated as interchangeable measures of sustained throughput.
Dispatch planned to enter Mumbai in November 2026. That expansion matters technically as well as commercially: a system learning from Pune’s delivery patterns will encounter different pickup concentrations, travel times and demand patterns elsewhere.
Frequently Asked Questions
4 questions
1What Will Dispatch Network Use the ₹5 Crore For?
Dispatch says it will expand its AI team and develop its proprietary Large Logistics Spatio-Temporal Model for intracity logistics and mobility.
