A city of two million, and barely a cab in sight
Nashik has a metropolitan population of over 2 million people, a thriving wine industry, and a religious tourism economy anchored by the Kumbh Mela. Yet open Uber in most of the city and you will wait fifteen minutes for a ride that never confirms, or get a fare estimate that no driver will honour. The unit economics that make ride-hailing viable in Mumbai — dense demand, surge-tolerant riders, drivers who depend on the app full time — simply do not hold in a city where the auto-rickshaw still rules the street. This is not a Nashik problem; it is the default reality across India's tier 2 cities.
Why the metro playbook breaks below tier 1
Uber and Ola were engineered for cities where supply and demand are deep enough to keep cars circulating and surge pricing acceptable. In Nashik, Aurangabad, or Jalgaon, daily ride volumes are a fraction of metro levels, so driver idle time balloons and earnings collapse. Local auto and taxi drivers, who already own established stand-based networks and fixed customer relationships, see little reason to pay 20-25% commissions to a platform that cannot guarantee them rides. The result is thin driver supply, which produces long wait times, which kills rider trust — a doom loop the aggregator model cannot escape in smaller markets.
The auto-rickshaw economy nobody digitised
Roughly 70-80% of intra-city motorised trips in tier 2 Maharashtra happen by shared auto, single auto, or local taxi, not app-cab. These drivers operate from stands, run on word-of-mouth, and price by negotiation or fixed local rates that everyone already knows. National aggregators treated this network as something to disrupt and replace, when the real opportunity was to digitise it on its own terms — keeping the driver's stand, his pricing logic, and his standing in the neighbourhood intact. Ignoring that informal layer is precisely why metro apps feel alien in these cities.
What a tier 2 mobility product actually has to do
A taxi app that works in Nashik has to start from local reality: low commission so drivers actually stay, support for autos and shared rides rather than only sedans, cash-first payments, and fare logic that respects locally understood rates. It must work for a rider who books once a week, not five times a day, which means bundling mobility with other reasons to open the app. Depo's local taxi booking is built around this — onboarding existing auto and taxi drivers in the city rather than importing a fleet, and embedding the ride inside a wider hyperlocal platform so demand is aggregated across needs, not just rides.
The real market is 500 cities deep, not five metros wide
India's mobility opportunity is not another fight for share in Bengaluru traffic; it is the 500-plus tier 2 and tier 3 cities where no aggregator has built a product that fits. These cities collectively house several hundred million people whose transport spend is real but fragmented across informal channels. Win Nashik on its own terms and the same model travels to Sangli, Solapur, and Kolhapur with minimal adaptation. That is the market metro-first thinking keeps missing — and the one Depo is built to serve.