Operating system for a multi-branch racket-sport club network

Context

Racket-sport clubs outgrow generic booking tools the moment they open a second branch. Courts, player groups, wristbands, tournaments, open games, rentals and inventory all need to share one client record and one ledger — and off-the-shelf systems treat each location as an island with its own base and its own cash discipline. Tools adapted from salons and gyms carry the wrong primitives: they know appointments, not courts, sessions and racket-sport formats.

The network behind this engagement already ran real operations — wristband check-in at the door, cameras on the courts, booking in an external industry CRM. What it lacked was a single operating picture across branches.

The task

Show, in a working interactive demo, how one data model carries the entire operation of a multi-branch club network — concrete enough to argue product decisions with operators screen by screen, not a slideware wireframe. The demo had to cover the full functional surface: schedule and courts, player groups, clients, finance, analytics, tasks, tournaments, open games, rentals and inventory, thirteen modules in total, and had to respect the reality that clubs already live on an external CRM they will not abandon overnight.

Data model first

The core is the club data model. Branches, courts and time slots form the scheduling backbone; every player is a single client record shared across the network, whichever branch they visit. Finance and analytics hang off the same spine, so a booking, a court session and a payment are three views of one event rather than three systems to reconcile at month end.

Identity is physical: NFC/RFID wristbands and UIDs tie the person standing on the court to the client record. That is what closes the loop from booking to court to finance to analytics without an operator re-keying anything — and it is the same presence signal the network's court-video platform uses as its recording trigger.

Integration, not replacement

Because the clubs already run on an external industry CRM, the demo includes an integration layer over Telegram and webhooks: the operating system augments the existing stack rather than demanding a rip-and-replace migration. Bookings, clients and sessions can flow in from the systems the club already trusts.

On top of the operational state sits an AI analyst: it reads the live picture — court utilization, unpaid sessions, group fill rates, task backlog — and surfaces what needs attention, instead of leaving managers to dig it out of reports.

Outcome

The working interactive demo covers branch, inventory, wristband and game-session management for padel, tennis and other racket sports. It serves two roles at once: the argued, clickable foundation for a productized club operating system, and the design source for the network's production systems — the wristband check-in and court-video platforms built in adjacent engagements share its data model and identity principles.

What we built

• Schedule & courts

  Court and group scheduling across multiple branches under one client base and one ledger.

• Wristbands & UID

  NFC/RFID wristband identity ties a player to bookings, finance and sessions — the physical carrier of the client record.

• Bookings, games & rentals

  Online booking, tournaments, open games, rentals and inventory in one flow — 13 functional modules in total.

• AI analyst & integration

  An AI analyst reads the operational picture; an integration layer over Telegram and webhooks syncs with the club's external CRM.