One system for the venue, not a booking form with reports attached
Twelve parts, one account, one record of what happened. Each page below says what the part does and where it is up to, including the ones we have not finished.
Taking the booking
- Bookings → In build
Timed fixed-capacity sessions, private buyout, buffers and combinable resources.
- Booking widget → In build
Renders in your own page, so your analytics and attribution keep working.
- Payments → In build
Your own Stripe account, you stay merchant of record, no card fields on your domain.
- Vouchers → At launch
Across venues and across kits, part-redeemable, with a liability ledger.
What happens after the sale
- Operations → Live
Run sheet, check-in with waivers inside the flow, and what actually happened captured at the end.
- Experience kits → In build
The parts of the day that are not the booking, priced at ten dollars and capped like everything else.
- Setup → Live
Sessions live and taking money today, with depth revealed as it becomes relevant.
- Multi-venue → In build
Shared by default, one filter across every view, per-venue timezone and currency.
The numbers and the shell around them
- Revenue operations → Live
Revenue per available slot, decomposed, so you can see which lever moved.
- Reporting → Live
All of your history in one query, one canonical definition per metric.
- Cost and labour → Live
Cost per booking and revenue per staff hour, read against the roster you already keep.
- White label → Live
Your brand and your team's own words, included at one venue as well as at twenty.