The operator day
One club day, six operating decisions.
Six moments decide whether a club day works: member access at open, the lunch roster, the evening court desk, league night, the Stripe close, and the Monday report. Lobby runs all six on one operating record.
No credit card · No commitment
Club day trace
One day, one operating record
08:00
01 · Memberships
Can this member book right now?
12:00
02 · Classes
Who is actually on the roster?
18:10
03 · Bookings
Can we sell this hour?
20:00
04 · Leagues
What changed after this result?
23:30
05 · Payments
Where did this Stripe payout come from?
Mon
06 · Reports
What should we change next week?
Each moment writes to the same record. By 23:30 the payout already knows what happened at 18:10.
Six operating moments
Six moments, six desk questions.
An access check at the door, a roster at noon, sellable hours at 18:10, a result at 20:00, a payout at 23:30, and a decision on Monday. Staff answer each one from the record, not from memory.
08:00
Access decisionMembership gate
Can this member book right now?
A paused plan, off-peak rule, or package balance decides access before staff take payment.
Explore memberships
12:00
Waitlist cockpitClass roster
Who is actually on the roster?
Capacity, credits, coach changes, and the waitlist stay beside the class record.
Explore classes
18:10
Sellable inventoryCourt desk
Can we sell this hour?
Holds, payments, staff blocks, recurring bookings, and cancellations share one schedule.
Explore bookings
20:00
Score-to-standingsLeague night
What changed after this result?
The result changes ratings, standings, and open-play bands without spreadsheet night.
Explore leagues
23:30
Money trailStripe close
Where did this Stripe payout come from?
Payments, refunds, fees, and payout references stay tied to the booking or class that created them.
Explore payments
Mon
Decision boardOperator meeting
What should we change next week?
Occupancy, revenue, no-shows, unpaid bookings, and exports turn the week into actions.
Explore reports
Court 01
Padel · indoor
Court 02
Padel · indoor
Court 03
Padel · outdoor
Open play
Beginner social
17:00 — 18:30 · 4/4
Reservation
F. Langworth +3
Lesson
Coach Madison
20:00 — 21:00
Block
Maintenance
League match
Marchand vs Veiga
17:30 — 20:00 · Ladder R3
Free · €30/h
Reservation
A. Iliescu +1
17:00 — 19:00
Holding · 90s
New booking
Illustrative club data
18:10 · Court desk
Can we sell this hour?
Holds count down in the open. Staff blocks, lessons, and league nights sit in the same grid as player bookings, and a slot only reads booked once booking and payment state agree. The desk sells from the schedule, not around it.
23:30 · Stripe close
Every payout explains itself.
Each payment names the booking, class, or membership that created it. Refunds keep their booking context, Stripe fees stay visible, and the Lobby cut on bookings is €0.00.
Recent payments
Next payout
€2 184.00
Mon 19 May
Processor fees
Stripe
Set by Stripe · Lobby never touches them
Lobby cut
€0.00
No booking percentage. Ever.
Illustrative club data
One operating record
Nothing falls between systems.
Access decides availability. A hold becomes paid state. A roster becomes utilization. Every handoff happens inside the record, so the desk never compares two screens and Monday never starts with a reconciliation night.
Memberships -> Bookings
Access becomes availability
Membership status decides which courts, sports, and time bands a player can reserve.
Bookings -> Payments
Hold becomes paid booking
A court hold becomes a confirmed booking only when the payment clears. If it does not, the slot reopens.
Classes -> Reports
Roster becomes utilization
Attendance, late cancels, credits, and fill rate become operating data for staff planning.
Leagues -> Reports
Result becomes performance
Match results, open-play fill, and rating bands explain program demand beyond raw bookings.
Payments -> Reports
Stripe becomes finance review
Refunds, unpaid bookings, and payout references remain visible when finance exports the period.
From export to live
Seven days from export to live.
A migration starts with a dry-run import staff can inspect and ends with members booking on the club domain. The white-label setup is part of the same week, not a second project.
Import preview
Demo Club · dry run
| Source field | Target field | Rows | Status |
|---|---|---|---|
| Playtomic.members | lobby.users | 1 842 | ok |
| Playtomic.bookings | lobby.bookings | 18 204 / 24 mo | ok |
| Playtomic.memberships | lobby.clients | 412 | ok |
| Playtomic.coupons | lobby.coupons | 38 | ok |
| Stripe.customer_ids | preserved | 1 842 | ok |
| Stripe.past_payouts | reference-only | — | read-only |
Illustrative club data
Migration
Members, bookings, classes, and payment references land in a dry-run preview staff can inspect row by row. Nothing goes live until the import reads clean.
Read the migration planWhite-label setup
book.club.example
Member booking preview
club.example/book
Illustrative club data
White-label
Members book under your name, on your domain, with your payment flow. No marketplace between you and your members, and no Lobby branding in the member path.
Book a demoOperator playbooks
Read the operator notes.
Two working notes for operators planning a switch: how to move a club without losing the week, and how to keep Stripe reconciliation a short daily check.
Your schedule, not a sandbox
Bring the real club day.
Test every handoff.
30-day pilot · Cancel anytime · CSV export of your data