Digital queues and marked bays for e-rickshaws at busy metro exits
TL;DR Rankbay turns the scrum of e-rickshaws outside a metro exit into a marked bay with a digital queue. Drivers get turns in order and lose them for blocking the road. Metro operators or city bodies pay a monthly fee per exit, and drivers pay a small daily one.
E-rickshaws are how a big share of metro riders finish their trip. In a 2022 survey of 630 passengers at 34 Delhi Metro Blue Line stations, 35.9% reached the metro by e-rickshaw, second only to walking at 38.7%[1]. The study also found that access time and service quality shape whether people keep using the metro at all[1].
At busy exits that demand turns into a crowd. Drivers park three deep to grab passengers, block the carriageway and argue over turns. Riders, especially women at night, have no fixed place to find a ride. No public count of e-rickshaws per station exists, so you'll have to measure the scale of the crowding yourself.
The seed was built for dockless scooters cluttering pavements, which is a Western problem. In India shared scooters are a small presence, and the main operator already parks in designated zones on land partners provide[2]. The real crowding is e-rickshaws, so Rankbay applies the same zoning idea to them.
At each exit, painted bays hold a set number of vehicles. Drivers register once with their e-rickshaw registration and join a queue on a cheap phone app or by SMS, and a small display at the bay shows who's next. A driver who skips the queue, double-parks or refuses short trips loses priority for the day. A marshal from the operator runs each site during peak hours. Riders see a clear pickup point and an indicative shared fare on a board, set with the drivers' union. The data, such as waits, trips and peak loads, goes to the metro operator and traffic police every week.
Riders and drivers use it. The metro operator or municipal body pays a monthly fee per exit, because forecourt crowding is their complaint to handle. Drivers pay a small daily bay fee, set low enough that a fair queue is worth more to them than the old scramble. I found no public tender or price for this service, so treat every price as an assumption to test.
The legal base is settled. Since the 2015 amendment, e-rickshaws are defined vehicles under the Motor Vehicles Act, which means registered drivers and vehicles that can be identified[3]. Delhi Metro alone has 271 stations and carried 64.6 lakh riders a day in 2025, per a public summary of DMRC data[4]. Cheap phones and SMS make a digital queue workable for drivers without smartphones.
There's no published figure for metro forecourt management in India. The firmest number is behavioural, with about a third of surveyed Delhi Metro riders arriving by e-rickshaw[1]. Multiply that across 271 Delhi stations[4] and the metro systems in other cities, and busy exits run into the hundreds. A realistic first target is 20–30 exits in one city (our estimate).
The largest shared e-scooter operator shows that zoning works in India. It set up its zones on parking that landlords such as office parks handed over, and called its model B2G2C[2]. It now runs swap stations and serves delivery riders through partners in cities such as Kolkata[5]. It manages its own vehicles though, not the city's e-rickshaws. Nobody we found sells queue and bay management for e-rickshaws at metro exits, which is either an opening or a sign that buyers won't pay.
| Difficulty | Moderate (43/100) |
| Starting capital | ₹40–80 L |
| Time to launch | 4–6 months |
The software is simple. The difficulty is human, because drivers' unions, local traffic police, the metro operator and the municipal body all have a say over the same few square metres. Getting all four to agree on one exit is the real launch milestone, and each new city repeats it.
No licence for the software itself, but you can't run a bay without permission from several bodies.
Building this outside India? The categories above usually have a local equivalent, so check with your own regulator.
Don't let AI suspend a driver on its own. A wrong ban costs someone a day's earnings, so a marshal should decide every penalty.
Want to work out the AI layer for Rankbay? Talk to Yash →
Here's what can go south -
I'd run a small pilot on this if you've worked with transport unions or city government and are comfortable on the street at 9 p.m. If you're hoping to sell software from an office then it's not for you. Prove one thing first - that at one exit, driver earnings per hour hold steady or rise once the queue is in place.
Plan for roughly ₹40–80 L, covering the software, bay displays, marshals and a pilot at a handful of metro exits.
There's no single licence. You need written permission from the metro operator for its forecourt, and from the transport department, traffic police and municipal body for the stand itself.
Yes, wherever informal vehicles crowd transit exits. Who controls the forecourt and the stands changes by city, so map that before you build anything.
The free Rankbay validation kit has the line-by-line capital breakdown, the effort scoring, the permissions checklist, a 14-day validation sprint with pass/fail targets, a 90-day launch plan, 10 interview questions for drivers, metro staff and city officials, and 5 assumptions to test. Download the kit →
Thinking about building Rankbay or something close to it? The make-or-break work is getting drivers, police and the metro operator to agree on a single exit, and that's the kind of messy ground work I help founders plan. If you need a hand, you know where to find me. Talk to Yash →
For illustration only. Names are fictional and ideas hypothetical; sourced facts are real but may be out of date. Nothing here is legal, financial or professional advice, and Yash Khatri is not personally liable for any use of it. Read the full disclaimer.