Booking System

ReactPrismaPostgreSQLEM

2025/Concept/Product engineering

A scheduling product for services that need availability rules, customer intake, and internal booking controls.

Booking products look simple until staff availability, buffers, intake data, rescheduling, and cancellation rules start overlapping.

The challenge was to design a system that feels lightweight for customers without pretending the operational complexity does not exist.

I broke the system into availability rules, customer intake, and internal controls so each part could stay understandable as the workflow grew.

The model separates what the customer sees from what the business needs to manage: staff calendars, blackout dates, service durations, buffers, and follow-up rules.

The concept gives customers a clean scheduling path while keeping staff-facing tools for exceptions, follow-up, and calendar control.

The UI is designed to make the happy path obvious, but it still leaves room for the messy real-world cases that scheduling products always run into.

The project shows how service booking can stay lightweight for customers without hiding the operational complexity teams need to manage.

It is a strong example of designing the interface and data model together instead of treating scheduling as just a calendar component.