How many separate products do I have to run?

One, plus two accounts you own anyway: Stripe, so payments land in your own account, and your door vendor's, for the lock you bought.

Does the door code know when a booking is cancelled?

Yes. The credential is issued when payment is confirmed and revoked when the booking is cancelled, in the same system.

Do I need a separate tool to watch the bay PCs?

No. Each bay's PC checks in, and silence past the alert bound reaches you by email and text.

How long does setup take?

The whole path, sign-up to a bookable venue with a lock and a bay PC connected, is walked and timed as one scripted run with no help needed.

Home / Answers

Can one system run booking, payments, the door and the bay instead of stitching vendors together?

What an unstaffed studio has to connect to take a booking and open a door, how much of it OpenTeeSheet does itself, and which parts still need a vendor account of your own.

Updated 2026-11-06. Every quote links to where it was published.

In owners' own words

“not stitching together a half-dozen vendors anymore”
A launch-monitor maker's own booking product launch post (vendor-authored) · source

“For unmanned and hybrid venues, the booking system is the access system”
Golf simulator booking software buyer's guide (vendor-authored) · source

“Where it falls short is everything golf-specific: no native access control integrations”
The same buyer's guide, on a general space-booking tool · source

What it is

The usual unstaffed studio runs on four or five accounts: a scheduler, a payment processor, a door-access product, something to watch the bay PCs, and a spreadsheet to hold the memberships none of them know about. Each pair of them has a seam, and the seams are where an evening goes wrong: a cancelled booking whose door code was never revoked, a payment that succeeded while the booking did not, a bay nobody noticed was offline until a golfer was standing in it.

Stitching also sets the floor on what the owner has to understand. Every account has its own login, its own bill, its own notion of a customer, and its own support queue to sit in when something breaks at eleven at night. For a two-bay studio that is one person's whole evening.

How OpenTeeSheet does it

Sign-up to a bookable venue with a door lock connected and a bay PC checking in is one path inside the product, walked step by step and timed against a real database with nothing outside the product needed at any step.	Pinned by automated tests: selfserve-timed.test.ts, onboard-one-venue-realdb.test.ts
Booking, the card at booking and the door credential are one transaction: the code is issued only when the payment is confirmed, and it is revoked when the booking is cancelled.	Pinned by automated tests: booking-finalize.test.ts, booking-payments.test.ts, cancel-booking.test.ts
The bay itself is in the same system: the bay PC's agent gets its schedule from the booking it belongs to, starts the session on the booked bay and stops it at the end.	Pinned by automated tests: bay-session-realdb.test.ts, bay-session.test.ts
Each bay's PC checks in, and silence past the alert bound reaches the owner by email and text, so nobody needs a separate monitoring product.	Pinned by automated tests: golf-tech-claims.test.ts, golf-tech-iot-realdb.test.ts
Memberships, packs, extra players, add-ons and league seasons are sold on the same booking page and charged with the same booking, instead of living in a separate tool.	Pinned by automated tests: memberships-realdb.test.ts, pack-expiry-realdb.test.ts, guest-fee-realdb.test.ts, leagues-realdb.test.ts
Bookings, door grants and bay sessions have one published data format, and the same document comes from the dashboard download, the app, the API, the MCP tool and the command line, so a studio can automate without a fifth vendor.	Pinned by automated tests: open-format.test.ts, golfer-shots-profile-realdb.test.ts

The bar we measure it against

A new owner goes from sign-up to a bookable venue with a door lock and a bay agent connected in under 10 minutes on a scripted run with no help, and the monthly price for 4 bays with door access and bay sessions is at or below the cheapest sourced stitched stack.

Where it stands today: The setup path is walked and timed end to end against a real database, and the price for 4 bays with door access and bay sessions included is the published $149. The stitched-stack price comparison is not published on the site, and two accounts outside the product are still required: a Stripe account to be paid into, and the door vendor's own account for the lock the studio owns.

Not built or not measured yet

Two accounts stay outside the product by design: Stripe, because the money must land in the venue's own account, and the door vendor's, because the lock belongs to the studio. OpenTeeSheet is the only system the owner operates day to day, but it is not the only account they hold.

The side-by-side price comparison against a stitched stack is in the research behind this page, not published on the site.

What owners report from other tools

A general space-booking tool has no native access control, by the buyer guide's own words, so the door, the bay and the memberships become separate products the owner connects and watches.

Questions

How many separate products do I have to run?: One, plus two accounts you own anyway: Stripe, so payments land in your own account, and your door vendor's, for the lock you bought.
Does the door code know when a booking is cancelled?: Yes. The credential is issued when payment is confirmed and revoked when the booking is cancelled, in the same system.
Do I need a separate tool to watch the bay PCs?: No. Each bay's PC checks in, and silence past the alert bound reaches you by email and text.
How long does setup take?: The whole path, sign-up to a bookable venue with a lock and a bay PC connected, is walked and timed as one scripted run with no help needed.