A feature teardown of Rapido's booking flow by Shivam Bajaj. Built only from public sources; I have no access to Rapido's internal data.
Rapido is an Indian ride-hailing platform that started with bike taxis and now offers autos and cabs. Its pitch to captains (drivers) is a low-cost alternative to the 20–30% cuts typical of the category, using a subscription model for autos and cabs (Outlook Business interview). It was reported to lead rivals with about 16.5 lakh daily rides (Outlook Business).
Feature in focus: booking a ride, from opening the app to a captain being on the way. This is where a rider decides whether the app can be trusted.
Valuation and ride-volume figures vary across sources, so I use only what the cited articles state.
Illustrative archetypes based on public complaints, not real individuals.
Who: Office-goer in a metro who books a ride to work every day
Goals: Reach on time at a predictable price
Pain points: Cannot get a ride in peak hours; captains cancel after seeing the drop (ThePrint)
Who: Young professional with last-minute plans, often late evening
Goals: Book fast and pay by UPI
Pain points: Unsure whether the captain will cancel; trouble at odd hours or when paying digitally (Business Today)
Who: Student or shift worker using a bike or auto for short hops
Goals: Lowest fare for a short trip
Pain points: Fare changes or extra money demanded outside the app (Free Press Journal)
Who: Commuter or student riding home after dark
Goals: Feel safe and reach home quickly
Pain points: Hypothesis: unsure about captain details and trip sharing at night
Opportunity: Prominent trip sharing and captain verification
Who: Bike, auto or cab driver earning per trip
Goals: Steady trips and fair pay
Pain points: Cancellations are a top rider complaint, so the cause matters; destination-visible-first is a reported driver trigger (Business Today)
Opportunity: Fair-fare cues and cancellation feedback to captains
Who: Tries the app after a friend recommends it
Goals: A quick first ride without confusion
Pain points: Hypothesis: unsure which vehicle type to pick and what the fare will be
Opportunity: Simple vehicle guidance and an upfront fare
Cancellations are the recurring theme. LocalCircles surveys put driver cancellations at the top of app-taxi grievances, with the share varying by survey (reported as 79% in one release) (ThePrint; Deccan Herald). These surveys cover app taxis in general, not Rapido alone.
My reading of the booking flow. Pain points come from the public sources above, plus a reported app outage (YourStory).
| Launch app | Enter location | Select ride | Book | Track & review | |
|---|---|---|---|---|---|
| Goal | Get a ride quickly | Set pickup and drop | Pick the right mode and price | Confirm and pay | Know the ride is coming and rate it |
| Action | Opens app, location detected | Types drop, adjusts pin | Compares bike, auto, cab | Chooses payment, taps Book | Watches captain approach, shares trip |
| Feeling | Hopeful | Neutral | Careful about price | Anxious: will anyone accept? | Relieved, or frustrated if cancelled |
| Pain point | App slow in peak hours or during outages | Wrong pin or drop | Unclear which option arrives soonest | Captain cancels after seeing drop or payment | Fare differs from app, rating skipped |
| Idea | Resilient app, fast first load | Nudge to confirm pickup pin | Show pickup time per option and a confidence level | Automatic priority re-match, no fee on captain cancel | Allow rating after the ride, with fare breakdown |
Illustrative wireframes of the booking flow. They are not screenshots of Rapido's app, and screens 3 and 4 include my proposed changes. All copy and amounts are placeholders.
1. Home: a clear “Where to?” field and ride-type choice
2. Choose a ride: pickup time per option, and a note that the captain sees the drop and payment mode
3. Finding a captain: live status so waiting feels less uncertain
4. Proposed: automatic priority re-match if a captain cancels
My suggestions, not claims about Rapido's roadmap.
If a captain cancels, automatically re-request the next nearest captain and move the rider up the queue, with no fee to the rider. Why: cancellation is the top complaint. Risk: needs to avoid punishing captains who cancel for genuine reasons.
Next to each ride option, show expected pickup time and how likely it is to be accepted soon. Why: helps riders choose the option that actually arrives sooner. Risk: a wrong estimate hurts trust more than none.
Let a rider book for a family member, share live tracking and the captain's details with them. Why: a common need that avoids phone calls. Risk: safety and fraud checks.
Allow one or more intermediate stops with the fare updated upfront. Why: fewer off-app negotiations for multi-stop trips. Risk: longer trips are less attractive for captains unless the fare reflects them.
| Key partners Captains (bike, auto, cab), payment providers, city transport regulators | Key activities Matching, pricing, captain onboarding, safety, support | Value proposition Riders: affordable rides across bike, auto and cab. Captains: low or no commission, with a daily subscription for autos and cabs | Customer relationships Self-serve app, in-app support, ratings | Customer segments Daily commuters, students, last-mile riders, captains as the supply side |
| Key resources Captain network, matching and pricing technology, brand | Channels Mobile app, word of mouth, captain referrals, local campaigns | Revenue Commission on bike rides, subscription fees from auto and cab captains, delivery services | ||
| Cost structure Technology and operations, incentives and marketing, support and safety, payment fees | ||||
Reported FY25 revenue lines include subscription (about ₹275 crore), two-wheeler commission (about ₹277 crore) and delivery (about ₹340 crore), per Open magazine. Competition from zero-commission rivals is discussed by Sacra.
Completed rides per week.
% of booking requests that become completed rides.
% of riders who book again within 30 days.
Independent teardown. Not affiliated with Rapido. Survey figures come from press coverage of LocalCircles surveys and are indicative. Check key figures against primary sources before reuse.