<aside> <img src="/icons/hashtag_gray.svg" alt="/icons/hashtag_gray.svg" width="40px" />

Designing a metric system for a marketplace that monetizes its supply, not its rides

</aside>

Links -

Interactive dashboard·

image.png

Deck

image.png

TL;DR


Context & the tension

Rapido is India's most distinctive mobility platform — not its largest. It's multi-modal by design, winning on affordability and two-wheeler density, increasingly in the markets Uber and Ola underserve. ₹934 cr operating revenue in FY25 (+44% YoY), a $3 bn valuation (Series F, May 2026), 400+ cities, 9M captains and partners, and a ₹258 cr net loss that narrowed ~30%.

The tension: every standard marketplace runs on one logic — GMV × take rate. Rapido split its monetization, so its two ride segments scale on different axes. Bikes are the original, highest-volume product, earning a ~15–20% commission per ride and making up over half of total ride volume. Autos and cabs run on zero-commission SaaS — captains keep 100% of fares, and Rapido earns a subscription instead (autos ₹9–29/day; cabs ₹500/month, charged only after ₹10,000 is earned). The lever that grows one segment doesn't move revenue the same way in the other — which is exactly why an off-the-shelf framework misreads the business.


The Insight

The North Star is weekly fulfilled rides — active riders × requests per rider × fulfillment rate. It's the one metric that holds across both monetization logics.

Why not the obvious candidates:

Fulfillment requires a completed ride, so affordability and liquidity must both be present — that makes it structurally immune to the GMV trap. Frequency (requests per rider) is the direct read on the "default app" thesis: Rapido isn't winning a single ride decision, it's becoming the app a user opens regardless of occasion (bike when solo, auto or cab with family).

The bridge metric is contribution per fulfilled ride — it links value creation to value capture, and it's the number that catches the moment ride growth stops paying.