RAPIDOProduct metrics case study
Live model · portfolio piece
Interactive model

The same ride growth can be
healthy or hollow.

Rapido monetizes its supply, not its rides — commission on bikes, a captain subscription on autos and cabs. Drag the levers and watch whether growth actually pays. The contribution-per-ride tile is the one number volume can’t fake.

Levers
Indexed to a baseline quarter (100).
100
100
100
Scenarios
NORTH STAR
Weekly fulfilled rides
24.1M
Net revenue / week
₹23.3 cr
BRIDGE
Contribution / ride
₹6.66

Liquidity funnel

Requests30.1M
Matched28.0M
Accepted25.2M
Completed24.1M
Avg ETA4.2 min
Unmet demand6.0M

Captains & monetization

Active auto/cab captains1.40M
Utilization (rides/captain)9.6
Multi-homing rate42%
Threshold-crossing rate55%
Bike commission / wk₹11.7 cr
Auto/cab subscription / wk₹11.6 cr

Illustrative model — relationships are directionally accurate; absolute figures are synthetic for demonstration.

Three scenarios, one lesson

Tap a card to load it into the model above, then watch which tiles move — and which one tells the truth.

Balanced growth

Demand and supply rise together. Utilization holds, crossing rate steady — rides and revenue climb in step.

The healthy path
Tap to load →

Over-acquisition trap

Supply outruns demand. North Star ticks up, but utilization and crossing rate fall — contribution per ride drops.

Volume hides a leak
Tap to load →

Fee hike (the wrong fix)

Revenue and contribution jump green — but the North Star falls and multi-homing spikes. The marketplace contracts.

Locally positive, globally negative
Tap to load →
The same ride growth can be healthy or hollow — only the bridge metric tells you which.

What you’re looking at

This is the working model behind a product-metrics case study on Rapido. Its premise: because Rapido monetizes its supply side — commission on bikes, a captain subscription on autos and cabs — a fulfilled ride adds to the North Star equally but only converts to revenue under different conditions in each segment. Growing rides is therefore not the same as growing the business.

The model encodes that as a feedback loop. Add auto/cab captains faster than demand can feed them and utilization falls, fewer captains cross the ₹10,000 earnings threshold to become payers, and a rising share of rides generate North Star credit but no revenue. The contribution-per-ride tile is built to catch exactly that divergence.

What the three levers do

Rider demand
How many ride requests come in. More demand raises utilization, fulfillment, and the odds captains hit the paying threshold.
Auto/cab captain supply
How many subscription-side captains are active. Add more than the demand can feed and each earns less, so fewer cross ₹10,000 to become payers — revenue stalls even as rides rise.
Subscription fee
What auto/cab captains pay. Raising it lifts revenue per payer, but pushes captains to multi-home, which quietly drains liquidity.

Key terms

Contribution per ride — the bridge
Revenue minus cost on each completed ride. The one number ride volume can’t fake; watch it beside the North Star.
Threshold-crossing rate
Share of auto/cab captains earning past ₹10,000 a month — the point they start paying the subscription. Falls when utilization falls.
Multi-homing rate
Share of captains also driving for Uber, Ola, or Namma Yatri. Rises when take-home drops — a leading signal that liquidity is about to weaken.
Utilization
Rides per active captain. The engine behind the threshold-crossing rate.