01 Executive summary
redBus is India's leading bus-ticketing platform, and its problems aren't about discovery or checkout — those work well. The damage happens after booking, where operator behaviour the platform doesn't control quietly erodes the trust redBus depends on.
Across three interviews and twenty-nine survey responses, one pattern kept surfacing: users don't distrust redBus the app, they distrust the operators redBus lists — and when something goes wrong, they feel the platform doesn't have their back. The sharpest failure of all is the last-minute operator cancellation: it strands travellers, forces rebooking at inflated prices, and sends them to competitors or direct-operator sites for good.
Users face last-minute cancellations by operators with no alternative arranged — because operators carry no accountability and redBus lacks quality enforcement. The result: severe disruption, forced rebooking at 3–4× price, platform abandonment, and broken retention.
02 Flows & frictions
Mapping the core journey, the front half is strong and the back half is where trust leaks:
| Touchpoint | Works well | Friction |
|---|---|---|
| Search → bus list | Fast, many options, rich filters | Hard to judge reliability; photos show new buses, reality is older |
| Seat selection | Visual layout, gender indicators | Seat map sometimes mismatches the real bus |
| Payment → confirm | Many payment options, quick | Delayed confirmation; operator may cancel after |
| Cancellation → refund | Clear cancel CTA, visible status | Refund timelines unclear; 10–15 days; opaque GST |
| Tracking & boarding | GPS reduces anxiety | Inaccurate tracking; "boarding point" is really a distant collection point |
03 What users actually said
The survey sized the problems; the interviews explained why they hurt.
A telling detail: trust in ratings averaged just 3.5/5. Only 55% trust reviews moderately or more — so the very mechanism meant to reduce uncertainty isn't doing the job.
04 SWOT
Strengths
- Market leader — 58.6% of respondents use redBus
- Deepest operator network & integrations
- Loved visual, gender-aware seat selection
- Bus-specialist depth vs full OTAs
Weaknesses
- No operator accountability / quality control
- Marketing-vs-reality bus quality gap
- Slow, opaque refunds (10–15 days)
- Weak support; price parity leaks to direct booking
Opportunities
- Operator tiering & quality certification
- Loyalty / subscription for frequent travellers
- Cancellation protection & auto-rebooking
- Uber-grade tracking; family-safety features
Threats
- Direct-operator disintermediation (34.5%)
- Full-service OTAs (MakeMyTrip, Paytm)
- Trust erosion from repeated quality issues
- Flights & intercity cabs for higher-income users
05 Who we're solving for
Researches obsessively, compares platforms, monitors daily price swings, and increasingly books direct after being burned. Wants reality to match the listing and operators held to a standard.
Books the same routes repeatedly for family, prioritises reliability over small savings, and feels unrewarded for loyalty while paying triple during festivals. Wants accountability and recognition.
06 Prioritisation (PIF)
Every problem scored on Population, Intensity and Frequency (1–5). Two rose to the top; the tiebreak went to the one most tied to retention and most within redBus's control.
| Problem | Pop | Int | Freq | Total |
|---|---|---|---|---|
| Operator quality uncertainty | 5 | 4 | 4 | 13 |
| Last-minute cancellations (P0) | 4 | 5 | 3 | 12 |
| Poor customer support | 4 | 4 | 3 | 11 |
| Slow / unclear refunds | 3 | 4 | 3 | 10 |
| Price differences across platforms | 3 | 3 | 4 | 10 |
| Inaccurate tracking / boarding | 3 | 3 | 3 | 9 |
Why cancellations won P0 over the higher-scoring quality problem: every interview raised it, its intensity is maximal (stranded passengers, trip failure), and — unlike weather or traffic — operator behaviour is squarely within redBus's control via agreements, penalties, tiers, and alternative-bus guarantees. Solving it proves the platform is worth more than aggregation.
Improve 3-month retention by 15% over 6 months for leisure and regular-commuter segments, by closing the last-minute-cancellation and operator-accountability gaps.
07 The solution: "redBus Guarantee"
Prioritisation is only half the job — the other half is building the fix. I wrote a full PRD turning the P0 into a three-pillar system that makes a journey complete even when an operator fails.
1 · Prevention
- Reliability score (90-day cancel rate) on every search result
- "Guaranteed Journey" badge for <1% operators
- Sort & filter by reliability
2 · Deterrence
- Financial penalties scaled to cancellation timing
- Progressive suspension (warn → 7d → 30d → ban)
- Reason verification to stop abuse
3 · Protection
- Alternative-bus guarantee within 2 hours, price diff covered
- Instant auto-refund, no ticket raised
- Compensation + meal/hotel vouchers on long waits
Lift 3-month retention 45% → 52%, halve operator cancellations 8% → 4%, and secure an alternative within 2 hours for 85% of affected users — all inside guardrails that keep operator churn under 10%.
The build is sequenced by RICE, not ambition: Reliability Score + Badge ships first (RICE 27, lowest effort, highest reach), then penalties and auto-refund, with the harder Alternative-Bus Guarantee phased in last. A phased rollout on high-density routes de-risks the operator-churn and supply-coverage unknowns before going wide.
What this teardown taught me
- Accountability is the product, not a policy. The root of the distrust is operators facing no consequences — so the solution centres on changing operator incentives, not just softening the user's refund screen.
- Score the problem, then score the solution. PIF found the right problem; RICE sequenced the fix so the cheapest high-reach lever ships first.
- Retention is the honest metric. Conversion looks healthy; the leak is repeat usage — so every pillar is tied back to the retention north star.