CASE STUDY 03FULL-STACK PRODUCT

Taking service discovery through to booking

A multi-city booking platform connects service discovery with availability and business appointment management.

ROLE / CONTEXTFull-Stack Developer
PERIOD / STATUSProject work
TOOLS / AREASReact · Node.js · Express · MongoDB

01 / CONTEXT

The problem

A booking journey connects two sides of a product: a customer wants to find a service and reserve a time, while a business needs to control availability and manage the resulting appointment.

Bookd supports discovery across cities and service categories, together with business tools for appointments, availability and bookings. The platform has customer, business and admin experiences backed by an Express API and MongoDB.

02 / PERSONAL SCOPE

My contribution

  • Built a full-stack service-booking platform supporting businesses across multiple cities.
  • Created dashboards for appointments, availability and booking management; expanded the catalog to more than ten service categories.

03 / OUTCOME

What changed

Bookd connects service discovery and booking across multiple cities, with a catalog of more than ten categories and business dashboards for appointments, availability and bookings.

THE SYSTEM IN PRACTICE

One booking, connected across the stack.

Discovery, availability and booking validation each have a different responsibility in the customer journey.

FOLLOW THE FLOW

01 / Discover

Find the right business and service.

The customer interface brings together business listings, categories and service details before the booking starts.

CUSTOMER WEB APP

02 / Availability

Calculate the options that fit.

The API combines business configuration, existing bookings and capacity rules to return availability for the selected date and booking method.

EXPRESS API + BOOKING RULES

03 / Book

Validate again when the customer commits.

The booking endpoint checks the selected method, time, availability and required answers before persisting the booking.

VALIDATION → MONGODB

04 / Manage

Continue the journey on the business side.

Business dashboards provide the tools to manage appointments, availability and bookings after a customer submits.

BUSINESS PORTAL

ENGINEERING CONSIDERATIONS

The details behind the interface.

Availability is a calculation.

Different services need different rules. Bookd’s booking engine supports time slots, service and staff capacity, resources and shared-capacity sessions. Availability is computed from those rules and existing demand, then checked again during booking creation.

Separate configuration from the customer journey.

Business types define setup requirements and booking methods. The customer interface consumes that configuration, while the backend remains responsible for permissions and booking validation. This lets different kinds of businesses share the platform without forcing them into one booking form.

LOOKING AHEAD

Where I’d take it next.

  • Build repeatable booking scenarios for each method, including overlapping times and capacity limits.
  • Keep validating booking forms and status messages with the businesses that use them.
  • Measure the time from discovery to confirmation and use it to prioritize the slowest parts of the journey.