Skip to content
all workflows

case study · full-stack saas

EventSaaS case study

Marriage halls and event companies run bookings on paper and spreadsheets. → A multi-tenant platform for venues and event companies, from one hall to multi-branch.

GitHub (opens in new tab)
EventSaaS dashboard with demo data: booking totals, revenue, an October booking calendar and upcoming events

Screens

  • EventSaaS booking calendar for October with colour-coded bookings per day and status totals
    Booking calendar
  • EventSaaS bookings list with event, date, hall, client, payment and status columns
    Bookings
  • EventSaaS booking detail: event details, client and a payment summary with the share already paid
    Booking detail
  • EventSaaS halls page with two halls, their capacity, price per event, amenities and upcoming bookings
    Halls & venues

Screens from a local run with fictional demo data.

  1. 01 · The problem

    The problem

    Marriage halls, banquets and event companies run bookings on paper and spreadsheets.

  2. 02 · My role

    My role

    TODOyour role

  3. 03 · Architecture

    Architecture

    1. Venue / event company

      single venue → multi-branch

      → Bootstrap + JS UI

    2. Bootstrap + JS UI

      → PHP 8.2 app

    3. PHP 8.2 app

      full-stack, multi-tenant

      → MariaDB, TODO: modules (bookings, halls, billing?)

    4. MariaDB

    5. TODO: modules (bookings, halls, billing?)

  4. 04 · Key decisions

    Key decisions

    • TODOhow tenants and branches are modelled

  5. 05 · Challenges

    Challenges

    • TODO

  6. 06 · Result

    Result

    TODOstatus (in use? demo?) and any real outcome.

  7. 07 · Stack

    Stack

    • PHP 8.2
    • MariaDB
    • JavaScript
    • Bootstrap