Product architecture

A focused workspace built around three actors and one promise: appointments that actually happen.

BraidSuite ties together booking, deposits and reminders into a single rules engine so braiders spend less time chasing confirmations and more time creating.

Three roles, three surfaces

Client

Browse styles, book a slot, pay a deposit, get reminders.

Braider

Calendar, services, client list, business insights.

Admin

Oversee braiders, payments, users and platform health.

Booking flow


  ┌──────────┐    pick    ┌──────────┐    select   ┌──────────┐    pay      ┌──────────┐
  │  Client  │ ─────────▶ │ Service  │ ──────────▶ │ Time slot│ ──────────▶ │ Deposit  │
  └──────────┘            └──────────┘             └──────────┘             └────┬─────┘
                                                                                  │
                                                                                  ▼
  ┌──────────┐  reminder  ┌──────────┐    confirm  ┌──────────┐    create  ┌──────────┐
  │ Reminder │ ◀───────── │ Engine   │ ◀────────── │ Braider  │ ◀───────── │Appointment│
  └──────────┘            └──────────┘             └──────────┘            └──────────┘

Data model

users

  • id
  • name
  • email
  • role
  • active

services

  • id
  • name
  • price
  • durationHours
  • active

appointments

  • id
  • clientId
  • braiderId
  • serviceId
  • date
  • status

payments

  • id
  • appointmentId
  • amount
  • type
  • status

Rules engine

Deposits

A non-refundable deposit (default 25% of price) holds the slot. Refunded automatically on braider-initiated cancel.

Reminders

T-72h confirmation, T-24h reminder, T-2h check-in. Auto-cancel if unconfirmed within 24h of the appointment.

Conflicts

Slots reserved by service duration. Overlapping requests are queued and offered the next free slot.

System overview


   Client App  ─┐                              ┌─►  Notification Service
                │                              │
   Braider App ─┼──►  API Gateway  ──►  Core  ─┼─►  Payment Service
                │                              │
   Admin App   ─┘                              └─►  Data Store (Postgres)
Storage layer keeps the source of truth; every surface speaks to the same booking engine.