Lolo Cab
Lolo Cab (Triptota Services) moved from an outdated WordPress presence and phone/on-call bookings to a real ride platform: Flutter apps for users, drivers, and vendors, plus an admin dashboard. I owned the complete backend myself, mentored the team on admin and mobile flows, peer-reviewed code, and shipped the server side that ties the whole product together, including shared rides, one-way and round trips, airport transfers, payments, and DigiLocker KYC.
The challenge
The business was stuck on an outdated WordPress site with customers booking rides on call. That model did not scale: no reliable product surfaces for riders, drivers, or vendors, no proper admin ops console, and no backend that could support modern trip types, payments, and KYC. They needed three mobile apps and an admin dashboard, and technical leadership to deliver the backend and keep the team aligned.
Business requirements
- Replace the outdated WordPress site and on-call booking workflow with a digital ride platform
- Ship three Flutter apps: users (riders), drivers, and vendors
- Ship an admin dashboard for operations, verification, and platform management
- Build the complete backend (owned end to end) to power all four clients
- Support shared rides, one-way trips, round trips, and airport transfers
- Expose RESTful APIs for ride creation, seat sharing, pricing, and booking lifecycle
- Integrate multiple payment gateways for booking and settlement flows
- Implement automated KYC verification for vendors and drivers via DigiLocker
- Mentor the team on admin dashboard and mobile app flows; peer-review all client work
- Keep API contracts stable so users, drivers, vendors, and admin can ship in parallel
The approach
I took full ownership of the backend and engineering leadership: designed and completed the APIs and integrations for ride/booking lifecycle, seat sharing, pricing, payments, and DigiLocker KYC, while mentoring teammates on the admin dashboard and mobile app flows and peer-reviewing their code so all three Flutter apps and the admin console stayed aligned to one server contract.
What was done
- 01
From WordPress & phone bookings to product scope
Framed the rebuild around four clients (user, driver, and vendor Flutter apps plus an admin dashboard) so the business could leave on-call bookings and the outdated WordPress site behind.
- 02
Complete backend ownership
Designed and implemented the full backend myself: REST APIs for ride creation, seat sharing, pricing, and booking lifecycle across shared, one-way, round-trip, and airport transfer products, plus payment gateways and DigiLocker KYC for vendors and drivers.
- 03
Mentorship for admin & mobile flows
Mentored the entire team on admin dashboard flows and mobile app journeys for users, drivers, and vendors, so client features matched the backend capabilities and ops needs.
- 04
Peer review & delivery
Peer-reviewed team code across the apps and dashboard, unblocked technical decisions, and completed the backend so all surfaces could integrate against a stable, production-ready API.
Results
- Replaced a non-scalable WordPress + phone-booking model with a digital multi-sided ride marketplace
- Unblocked parallel delivery: three Flutter apps (users, drivers, vendors) + admin on one backend contract
- Owned the full server side solo: rides, pricing, booking lifecycle, payment gateways, DigiLocker KYC
- Made vendor/driver onboarding compliance-ready with automated DigiLocker KYC
- Raised team delivery quality through mentorship on admin/mobile flows and peer review across clients
