The shared booking and venue-operations foundation can model timed products, locations, rooms, customers, reservations, and staff workflows. Industry-specific scoring, safety, retail, food-and-beverage, content, or outcome features remain scoped requirements unless they are demonstrated in the current product.
GridMagik supports configurable locations, booking products, availability rules, closed periods, customers, guests, transactions, reservation detail, operational calendar views, and staff access. These are reusable venue primitives, not proof that every vertical workflow is finished.
A prospect's must-have workflow becomes a written scenario with roles, data, success, failure, recovery, mobile, accessibility, reporting, and integration expectations. If the current release cannot pass it, the item stays a gap or roadmap milestone.
A production decision should exercise online booking, walk-up handling, capacity conflicts, guest changes, cancellation, payment failure, staff permissions, internet interruption expectations, day-end reporting, and data export using the venue's configured workflow.
Run the venue's real scenario with real roles and known failure cases before cutover.
Industry fit is a tested configuration and scope, not a logo on a landing page.
Publish products and server-generated availability for configured tenants.
Lock product and shared resources before committing competing bookings.
Connect guests and operational history in the venue tenant.
Move reservations into staff calendar and detail workflows.
Connected checkout and Terminal require venue-specific live-money approval.
Waiver status exists; legal-document and guardian signing remain incomplete.
OAuth, location discovery, Terminal requests, signed webhooks, and settlement pass provider-mocked tests; real credentials and readers still need acceptance. Other POS and calendar connectors remain planned.
Scoring, tabs, content gating, and outcome automation require explicit proof.
The shared booking and operations foundation is real. Treat vertical-specific functionality as supported only when it is demonstrated in the current release and included in the written rollout scope.
Not based on a marketing page. Replacement requires data migration rehearsal, workflow acceptance tests, payment and hardware validation, staff training, recovery planning, and agreed cutover criteria.
Stripe Connect and registered Stripe Terminal readers are in controlled beta. Square has a tested provider-mocked foundation but no real credential or reader acceptance yet; other terminal providers remain planned. Manual cash and external tenders are explicit ledger records, not provider calls.
They are written as gaps with an owner and release gate. GridMagik does not relabel a mock screen or generic note field as a complete vertical workflow.
30-minute walkthrough. Your pricing, your calendar, your receipts — running live in a sandbox on your data. No slides.
