Gym & Padel Platform
One system to run a gym and padel club: members book classes and courts from their phone, coaches run their sessions from their own app, and the club sees its bookings, numbers, and café sales in one place.
Today, without it:
- a booking app here
- memberships there
- café on its own till
With the platform:
- Members, Coaches, The club
- One club system (Memberships, credits, the club’s rules)
- Classes, Padel courts, Café till, Club dashboard
The hard part: The club’s rules apply the same way everywhere.
The problem
Members want to book a class or a court from their phone in seconds. The club wants to know what is selling and who is coming. When memberships, bookings, coaching, and the café till each live in a different tool, neither happens, and every exception lands on the front desk.
What it does
- Members book classes and padel courts from their phone
- Coaches run their sessions from their own app
- Membership rules applied the same way everywhere, so staff never have to police them
- A dashboard showing how the club is doing
- The café till in the same system as everything else
Four modules, one system
- Class booking for members, with a coach-facing app
- Court reservations for padel
- A metrics dashboard for the club’s operators
- A cafeteria point of sale
Fair rules, applied by the system
The hard part of a booking product is not the calendar, it is the club’s rules: what happens to unused credits, when a member pauses their membership, or when one member tries to take every popular court slot. Those rules live in the system itself, so they hold the same way in the member app, the coach app, and the club’s dashboard.
Architecture
- An Expo application for customers and coaches
- A Next.js progressive web app for administration
- Supabase and PostgreSQL as the shared source of truth
- A pnpm monorepo in strict TypeScript, with shared design tokens and a component kit for each app
The diagram on this page is an illustrative system flow, not a screenshot of the product.