Business Problem

Sumeru Holidays ran cabs the way most regional travel operators do — on phone calls, WhatsApp threads, and spreadsheets. Three things were breaking:

• No self-serve booking. Every airport transfer or point-to-point ride needed a human to confirm it, capping how much the business could take on.

• Empty seats. Cars ran single-passenger on high-demand airport routes, with no way to pool riders going the same way.

• Zero operational visibility. Vendors, package-trip approvals, service availability, and payment status lived outside any single system — so ops teams had to reconcile manually and customers waited for answers.

The brief: Turn a call center operation into a product without losing the trust of customers used to talking to a person.

What I Designed with The Team

• Booking in three decisions — trip type (airport / pickup-drop), transport mode, and time — so the core flow stays under a minute on a phone in a taxi queue.

• Pooling as an option, not a default — ride-sharing surfaced with clear price and co-passenger context, letting riders trade privacy for cost knowingly.

• My Trips as the trust layer — upcoming, live, and past rides in one place, replacing the "Where's my cab?" phone call.

• An admin portal ops actually runs on — vendor management, package-trip approvals, service-availability toggles, and trip/customer/payment detail views in a single console.

• One system, two surfaces — a shared design language across Flutter mobile and ReactJS web so a 4-person engineering team could ship both in 7 weeks.