Btaxi
Rider, Driver, Admin — designed and coordinated from scope to handoff. Khmer script, no standard banking API, low-end Android. Every constraint was real.
- Ride-Hailing
From single-tenant internal tool to a self-serve B2B SaaS platform — redesigning the configuration system, admin control center, and onboarding flow end-to-end.
[01]Problem_
An internal tool rigid by design — rebuilt for multi-tenant SaaS.
Every time a new client signed up, a developer had to go into the database and make changes manually. Not because anyone was lazy — because nobody planned for this to be a product.
First Release shipped within 12 months
Clients configure environments independently
Executive Summary


[02]THE PROBLEM_
FeedbackMe was built to serve one specific internal environment. When the business shifted to a commercial SaaS model, the product collapsed under diverse client requirements, requiring dev support for basic setups.
[03]DISCOVERY & APPROACH_
In an early-stage startup environment, polished onboarding journeys are useless if the underlying database configuration is broken. Discovery focused entirely on mapping the data configuration dependencies.
Technical Discovery Steps
[04]KEY OUTCOMES_
Successfully launched the First Release after 12 months of structural redesign. The core objective was met: delivering a stable, multi-tenant architecture that no longer relies on developers for basic client onboarding.
THE IMPORT ENGINE
Designed a frictionless file import flow that automatically translates client spreadsheets into active database structures.
Architected the front-end user journey while collaborating closely with Business Analysts and Engineering to define strict Excel template validation rules.
Reduced a multi-day manual configuration process down to a 2-minute self-serve upload.

[05]REFLECTION_
Logic Dictates UX: You cannot design a scalable interface until you understand the underlying database architecture.
Autonomy is Scalability: True SaaS value comes from eliminating developer intervention in routine client configurations.
Constraints Prevent Chaos: Giving users total customization freedom destroys the user experience; guardrails are mandatory.