← Selected work
Case 04 / 04
Platform / Operations
Car Care System
Project brief
A booking and garage-management platform for four very different users — customers, merchants, staff and admins — in one system.
The problem
A garage runs on bookings, bays, staff schedules and customers who just want to know when their car is ready. Most of that lived in phone calls and notebooks. The platform had to serve four audiences at once without becoming four separate apps.
What I owned
- UI/UX flows for each role — the customer booking a slot, the merchant managing their garage, staff working through jobs, and admins overseeing the network.
- Database schema that keeps roles cleanly separated while sharing one source of truth for bookings and services.
- Backend architecture in NestJS, plus the frontend modules in React and Tailwind CSS on top of Supabase.
What happened
The product was built end to end, but the startup behind it closed, so the platform never reached scale. I’m keeping it here because the engineering decisions held up and still shape how I build:
- Schema first. Modelling bookings, services, bays and people before any screen made four interfaces four views of the same truth.
- Roles are relationships, not user types. A person can be staff at one garage and a customer at another.
- Scope data by owner from day one. Access rules became a property of the schema, not scattered checks.
Stack
React · NestJS · Tailwind CSS · Supabase