Reservation system

Context

A major nightlife group operating several clubs in parallel, each with its own programming, events and PR team. The operation runs on three distinct user roles with completely different workflows: PR people capturing reservations on the street and via social channels, floor staff (bartenders and hostesses) handling them live during the night, and management needing to see the business through real data before the shift even closes.

Challenge

• Three roles with opposing needs lived in different tools: spreadsheets for PR, notebooks on the floor, manual nightly reports.
• Data from each venue ended up fragmented after closing. Impossible to know which PR person converted best, which venues performed, or which events drew the most real bookings.
• Onboarding a new venue (capacity, tables, events, pricing, commissions) required engineering work every single time.

Solution

The system is made up of three tools connected to the same database in real time:

• PR mobile app — Capturing reservations on the street.
• Floor mobile app — Live management of reservations, tables and walk-ins for bartenders and hostesses.
• Web back-office — Platform administration and data exploration through interactive reports.

Outcome

• One single platform replaces spreadsheets, notebooks and manual reports.
• Management checks venue and event performance without waiting for the night to close.
• PR people see their commissions live; the floor team works against the same data as the office.
• New venues onboard in minutes, no code or deploy required.

Stack

• Backend: Laravel 13 with Inertia, relational DB and real-time APIs.
• Web (back-office): React rendered via Inertia.
• Mobile (PR + Floor): Ionic with Angular and Capacitor. One codebase for iOS and Android.
• Infrastructure: cloud-hosted with CI/CD, production monitoring and error reporting from sprint one.