Operator systems
One system for bookings, payments and owner reporting.
We build for dive and tour centers, activity operators, clubs and small properties. We map how a day runs at your operation, then build one database behind the front desk, the floor and the owner's phone. You own the code and the data.
01 · What the system runs
Bookings and seat capacity
Every booking lands on its day, against the seats, boats, rooms or guides that day holds. The front desk sees what is left to sell before it confirms, so an outing never sells past its last seat.
- Day sheetEvery slot, its capacity, and who is booked on it.
- Seat limitsA slot closes when its last seat sells.
- Group bookingsOne booking for many guests, each with a record.
- ChannelsDirect, agency and marketplace bookings in one list.
02 · What the system runs
Payments and commissions
Card, cash and transfer payments are recorded against the booking they pay for. Staff and agency commissions are calculated from the same record, so payday uses the numbers the front desk already entered.
- Card paymentsStripe or your processor, matched to the booking.
- Balances dueWho still owes money, and how much, before the guest arrives.
- CommissionsPer staff member and per agency, calculated by rule.
- CurrenciesEach figure carries its currency and the exchange rate used.
03 · What the system runs
Owner reporting
The owner opens one screen and sees today, the weeks ahead, sales and cash. Each figure comes from the bookings and payments already in the system, so nobody rebuilds it in a spreadsheet.
- TodayWho is booked, who has paid, and what is still open.
- AheadBookings against capacity for the coming weeks.
- MoneySales, costs and cash by period.
- Cost per outingWhat each trip cost to run against what it sold for.
04 · What the system runs
Procedures as checklists
Your standard operating procedures live in the system as checklists. A checklist opens when a booking needs it, so the morning equipment check appears on the days a trip runs.
- Procedure libraryEvery procedure in one searchable place.
- Booking triggersA checklist opens when a booking calls for it.
- Sign-offEach item ticked by a named person, with the time.
- Audit trailA record of every check, ready when an inspector asks.
Proof
We built this for a dive and tour operator in Mexico.
Bookings, seat capacity, payments, commissions, owner reporting and procedure checklists run from one database. The figures count what the build contains.
Database
177
Tables in one database. Every screen the staff and the owner use reads from it.
Automations
37
Automations that run inside the system without anyone starting them.
Integrations
12
Live integrations, including Stripe, Wise, Plaid and DocuSeal.
Checklists
196
Standard operating procedures, each turned into a checklist inside the system.
Try it
Run a sample day yourself.
The working system page runs a model operator with a day sheet, guest records and live numbers. Change any input and every figure on the page recalculates.