06 · Roadmap

Prototype built. The path to launch is mapped.

Bootstrapped so far, we've prototyped the hard parts first: identity, geospatial matching, ride state and payments. Next comes our first funding and a pilot launch in one corridor, then engagement, scale and new revenue lines.

Phase 1Built in prototype

Foundation

  • Phone OTP auth with JWT + refresh rotation
  • Home & work onboarding on the map
  • Profile and saved locations
  • Pilot onboarding: vehicle, documents, verification, availability
Phase 2Built in prototype

Core ride marketplace

  • Commute routes as offers and requests
  • PostGIS + OSRM route-aware matching worker
  • Ride state machine with cancellations
  • Razorpay UPI payments with signed webhooks
  • In-app notification inbox
Plans A & BBuilt in prototype

Request lifecycle

  • 45 s live search with a “we'll notify you” fallback
  • Background matching and 30 s watcher
  • Reverse matching on new pilot offers
  • Request-expiry worker and recurring weekday rides
  • Cancel-with-reason, schedule validation, My Rides
NextUp next

Pilot launch

  • Secure our first investors (pre-seed)
  • Launch in one dense office corridor
  • Onboard and verify the first pilots and riders
  • Validate the pricing model with real commuters
Plan CPlanned

Engagement & retention

  • FCM push notifications
  • Extend departure window (+1 h / +2 h / custom)
  • Wallet ledger credits on payment capture
  • Ratings API feeding trust score
  • Cache-aside and k6 load testing on matching
ScalePlanned

City-scale infrastructure

  • Horizontal matching worker replicas
  • H3 geo-bucketing before PostGIS
  • ST_Intersects shared-length route overlap
  • PgBouncer pooling and queue-depth alerting
GrowthPlanned

Platform expansion

  • Employer programs and company-only pools
  • Monthly commute passes
  • Savings, CO₂ and badges for engagement
  • Multi-city launch playbook
What we measure

How we'll prove it in the pilot corridor.

The prototype already records every request, match, ride and payment with timestamps. Once we launch, these KPIs will come directly from real usage data.

Match rate

Share of requests that receive at least one match

Time to match

Seconds from request to first match card

Seat fill rate

Occupied seats ÷ offered seats per pilot trip

Repeat pairing

Riders who ride with the same pilot again within 14 days

Cancellation rate

Rides cancelled, broken down by stated reason

Payment success

Completed rides settled over UPI without intervention

Previous
← Business
Next
Invest →