The hyperlocal proof Swiggy delivered
Swiggy did something genuinely hard: it proved that real-time hyperlocal logistics — matching a customer, a restaurant, and a rider within minutes — can work at national scale in India. It built dense rider networks, sharp ETAs, and a habit loop strong enough to make food delivery routine across hundreds of cities. Quick commerce through Instamart then showed the same rails could move groceries in ten minutes. The core lesson is settled: Indians will adopt hyperlocal services when the experience is fast, reliable, and genuinely local.
Why food-first only takes you so far in tier 2
Swiggy's economics are anchored in dense, high-frequency food and grocery orders concentrated in metros and large tier 1 cities. Push that model into a tier 2 town and order frequency drops, average order values shrink, and the standalone delivery business gets hard to sustain. Restaurant density is lower, dark-store math is tighter, and a single vertical struggles to justify the local operating cost. The hyperlocal opportunity in smaller cities is real, but it is not shaped like a food-delivery app.
Tier 2's needs are broader than a food order
What a resident of Solapur or Sangli needs hyperlocally is wider than dinner: a ride across town, a verified plumber, a flat to rent, a used bike to buy, the right shop for a specific item. Each of these is a hyperlocal problem — local supply, local trust, local discovery — but none alone has the metro-grade frequency to support a dedicated app. The demand is distributed across many everyday needs rather than concentrated in one high-frequency category. That distribution is the defining feature of the tier 2 market.
Aggregating frequency instead of chasing one vertical
The strategic answer is to flip Swiggy's depth-in-one-vertical model into breadth-across-needs. If no single service in a tier 2 city has enough frequency on its own, combine several — mobility, discovery, classifieds, property — into one app so the aggregate keeps users coming back. A resident might book a taxi twice a week, search a business now and then, and sell a phone once a year; individually thin, together a daily-relevant habit. Depo is built on exactly this aggregation of frequency, the inverse of the single-vertical metro playbook.
What carries over, and what does not
From Swiggy, the durable lessons carry over: obsess over local supply density, design for trust and reliability, and build a habit loop, not a one-time transaction. What does not carry over is the assumption that one high-frequency vertical and metro density will fund the model in a smaller city. Tier 2 India needs a hyperlocal platform engineered for breadth and low individual frequency, operating city by city on local supply and local trust. Swiggy proved hyperlocal works in India; tier 2 just needs it built the other way around.