Extend
18 minutes left. Nothing booked behind you.
Offer another 30.Subject to availability, price and venue rules.THE COPA PLATFORM
Your platform.
Behind your experience.
Booking, memberships, POS, events, staff, communications and pricing share the same guest and visit context. Run your whole venue, with your brand in front.
NATIVE APPLICATIONS. OPEN PROVIDER ECOSYSTEM.
Replace venue software. Connect the specialists.
COPA performs the venue jobs that need shared identity, visit and operating context. That can replace separate products—not simply add another dashboard above them.
Work COPA does
- Booking, memberships & credits
- Native resource scheduling, membership benefits and venue credit workflows. Payment processing remains with your provider.
- Guest records & member portal
- Accounts, booking history, membership and venue follow-up workflows. Replacement is scoped to these jobs, not every general-purpose CRM feature.
- Staff operations
- Scheduling, availability, time clock, time off, swaps, timesheets and checklists. These workflows are implemented; venue rollout and acceptance are required. Payroll processing stays separate.
- Leagues & venue messaging
- Supported league, team and standings workflows, plus lifecycle messaging. Delivery services remain separate. Challenges and newer automated workflows have their own activation requirements.
- Bay OS & device controls
- Native session management and supported-device controls. Activity engines remain specialized software; equipment compatibility and commissioning are confirmed per venue.
Infrastructure COPA connects
- Payment rails
- Retained POS / KDS
- Activity engines
- Accounting
- Voice & message delivery
- Music
These providers can remain behind the experience. Their subscriptions, licenses, processing fees and usage costs do not disappear.
See provider-specific scopeNative capability ≠ automatic rollout
The original venue platform includes operating native workflows. Independent COPA deployments still require customer bootstrap, branding, commerce and hardware validation. Implemented modules are not all active in every venue.
Waitlists, pricing automation, recovery and governed Wally actions have separate rollout requirements. General CRM, waiver suites and universal device management are not claimed as fully replaced.
EXPLORE THE WHOLE OPERATION
There’s an entire venue
inside COPA.
Choose the part of your business you want to explore. Each area connects to the same guests, visits and operating context.
01 / EXPLORE
Booking & guest experience
Availability, participant identity, arrival, ordering and the next visit.
02 / EXPLOREPricing & revenue intelligence
Rate rules, simulations, gap recovery, demand elasticity and controlled automation.
03 / EXPLOREVenue operations
The floor, the team, active sessions and the exceptions that need attention.
04 / EXPLOREWally & intelligence
Conversational access to context, with clear permissions and activation boundaries.
05 / EXPLORECommerce & service
The activity, the order, the tab and the team should share the same context. COPA connects guest ordering, staff POS, fulfillment and the work that happens after the sale.
06 / EXPLOREStaff & shift management
Scheduling is only the beginning of a shift. COPA connects availability, time, floor context, checklists and manager oversight so the handoffs have somewhere to live.
07 / EXPLOREMemberships & relationships
Bring guest history, memberships, credits, credentials and corporate benefits into the same operating model. The person should not disappear when they move from booking to the floor.
08 / EXPLOREMarketing & retention
Your marketing tools should know more than an email address. COPA connects campaigns, lifecycle activity and delivery oversight to the guest and the venue.
09 / EXPLORELeagues & community
Crews, leagues, challenges and events give guests something to return to. COPA connects that community activity to resources, participants and the work of running the venue.
10 / EXPLORECoaching & performance
Connect the lesson business to the guest’s practice and activity history. COPA brings scheduling, packages, coaching context and performance views into the same relationship.
11 / EXPLOREHardware & venue systems
COPA reaches into the activity space: kiosks, PCs, displays, service devices and supported AV. Give physical-system issues the same operational context as a booking or order.
12 / EXPLOREReporting & control
A connected operation needs useful reporting and clear authority. COPA gives operators analytical views, audit context and controls over people, configuration and emerging automation.
THE REAL COST OF DISCONNECTED SOFTWARE
Your staff shouldn’t be
your integration layer.
Replace the overlapping software.
Connect the infrastructure that remains.
You pay for the stack.
ILLUSTRATIVE MONTHLY SOFTWARE MIX- POS / restaurant softwareSpecialist POS may stay
- $350
- Booking / resource schedulingNative booking in COPA
- $425
- Staff ops / scheduling / time clockNative workflows; rollout scoped
- $200
- CRM / email / SMS softwareGuest workflows move; delivery stays
- $325
- Membership / loyaltyMemberships & credits move; other loyalty scoped
- $200
- Waivers / leagues / other toolsSupported leagues move; waivers not assumed
- $200
- Hardware / automation / connectorsSupported device controls move; specialists stay
- $350
Software subscriptions$2,050 / month
Illustrative software mix. Actual costs vary by provider, usage, location and configuration. Bundles may overlap.
THE HUMAN INTEGRATION LAYER
Your staff.
Copy. Check. Chase.
Explain. Re-enter. Repeat.
Separate logins.
One team bridging the gaps.
Your customer should experience your venue — not your software stack.
Native jobs move into COPA; specialist services stay connected. See replacement scope. The illustrative bill excludes processing fees, metered delivery, equipment, implementation and separate specialist licenses.
Then you pay your people to connect it.
Before manager reconciliation. Before missed extensions. Before lost orders.
$18,250 / year
8 shifts/day × 15 minutes × $25/hour × 365 days
Illustrative friction cost. Not measured COPA savings.
And you still lose opportunities between systems.
Booking knows the schedule.
POS knows the tab.
CRM knows the customer.
COPA knows
the visit.
03 / THE OPPORTUNITY
Shared context makes the next move visible.
Order
Active visit. Open tab. Guest still playing.
Another round without leaving the experience.The guest, resource and tab supply the service context.Recover
A cancellation creates 90 minutes of inventory.
Put that capacity back to work.Review the opening, the audience and the offer.Illustrative opportunities, not live actions or autonomous promises. Availability, permissions, confirmation and rollout scope still apply.
One Venue OS.
Three ways it pays.
- Consolidate
- Replace overlapping venue software. Keep specialized infrastructure.
- Operate
- Less searching. Less re-entry. Less reconciliation.
- Grow
- Extensions, orders, recovered capacity and return visits.
ACTUAL PRODUCT. SAMPLE DATA.
See the work.
Follow the visit.
A short walkthrough of COPA’s booking, staff and guest interfaces. These captures use actual product components, fictional records and neutral styling.
01 / BOOK
A time, a price and a reason to choose you.
The actual booking time picker groups availability by part of the day and displays the member rate supplied to it. This sample shows a selected slot and different afternoon and evening prices.
Shown: booking time picker with fictional availability and prices.Captured from the current implementation in an isolated environment. This is a guided visual tour, not a live transaction demo. Venue branding, navigation and final configuration may differ.
WHO COPA IS FOR
You run an experience.
The software should keep up.
COPA is built for operators coordinating bookable spaces, repeat guests, memberships, hospitality and a team on the floor. The strongest fit is a venue where those jobs overlap every day.
Golf & competitive socializing.
Simulator venues, social darts and activity-led hospitality. Timed sessions, groups, food and drink, and physical equipment are central to the operating model built at the first venue.
Clubs & hybrid activity venues.
Racquet, training, bowling and other bookable experiences may share the same operating problems. We assess their resource rules, scoring systems, equipment and service model before proposing a rollout.
Opening, upgrading or expanding.
Plan the stack before a new opening. Replace the manual glue in an existing venue. Or assess a repeatable operating model for more locations—with brand and location requirements scoped first.
Does this sound like your venue?
- You sell time in bays, lanes, rooms or other resources.
- Members, groups and returning guests matter to the business.
- Activity, service and payment need to follow the same visit.
- Staff are switching apps to answer ordinary guest questions.
A PRACTICAL FIT CONVERSATION
If you only need a simple appointment calendar or standalone till, a full venue operating system may be more than you need. COPA is for the complexity between those tools.
We’re discussing scoped operator and design-partner rollouts. New brands and additional venue types require implementation work, not just a logo change.
See what a rollout involvesEXPLORE THE FULL PLATFORM
A whole venue’s worth of capability.
Open a capability group to see the work it covers—and what becomes possible when it shares context with the rest of the venue.
01 / Guest & MemberRecognize the person, not just the reservation.
Connect the guest-facing website, account and membership to the visit. Benefits and relationships belong to the guest wherever the experience takes them.
WHAT THAT LOOKS LIKE
A returning member arrives with their identity, booking and benefits already connected.
Explore these tools in detail- Accounts and identity
- Memberships, tiers and benefits
- Corporate relationships
- Apple and Google Wallet credentials
- Native mobile experiences
- Customer history and CRM
- Lifecycle messaging
02 / Booking & RevenueMake the space work with the schedule.
Coordinate resources, activities, prices and participants with authoritative availability. Build the next sale on the context of the current visit.
WHAT THAT LOOKS LIKE
A group wants longer. COPA checks the next booking, applies the right price and confirms before extending.
Explore the full pricing toolkit- Live, activity-aware availability
- Temporary holds and confirmed bookings
- Membership pricing and credits
- Participants and crews
- Waitlists and gap recovery
- Extensions and rebooking
- Versioned dynamic-pricing policies and simulations
- Demand elasticity and Gap Pricing Copilot
- Price floors, ceilings, date locks and automation limits
03 / Play & PerformanceThe activity is part of the relationship.
Carry session and gameplay context into the experiences guests return for: practice, coaching, competition and playing together.
WHAT THAT LOOKS LIKE
The end of a session can become the start of a coaching conversation or the next competition.
Explore these tools in detail- Activity launch and session control
- Gameplay history
- Shot and round capture for supported systems
- Player performance
- Coaching and lessons
- Programs and challenges
- Shareable round cards
04 / CommerceEvery order has a place in the visit.
Connect food, drinks, retail and activity purchases with the tab, service destination and payment state. Keep exceptions in the same operational record.
WHAT THAT LOOKS LIKE
An order from the room reaches service with its visit context, rather than becoming a separate transaction to reconcile later.
Explore these tools in detail- POS and booking-attached tabs
- In-bay, mobile and staff ordering
- Kitchen and bar displays
- Split payments and house accounts
- Refunds, comps and voids
- Terminal payments and provider adapters
- Settlements, accounting and retail
05 / Staff & OperationsGive the team a common picture.
Connect the people running the floor to the work in front of them. Managers can coordinate service while keeping approvals and access under control.
WHAT THAT LOOKS LIKE
A manager handles a service exception with the booking, tab and staff context in view.
Explore these tools in detail- Staff app and manager operations room
- Scheduling and availability
- Time off and shift swaps
- Time clock and timesheets
- Payroll exports
- Checklists and playbooks
- Roles, transaction limits and audit trails
06 / Venue SystemsReach the equipment behind the experience.
Bring the physical estate into the operating model, from activity PCs and identity readers to displays and the systems that need recovery.
WHAT THAT LOOKS LIKE
A display fault becomes a visible operational issue tied to the room, rather than a surprise reported by the guest.
Explore these tools in detail- Windows Bay OS and kiosks
- QR/NFC readers and companion devices
- Display and projector control
- Printers and payment terminals
- Device health and fleet management
- Remote commands, diagnostics and recovery
- Music and environment integrations
07 / Community & RetentionMake your venue part of the routine.
Build continuity beyond the booking. Connect the reasons people return with the people they return with.
WHAT THAT LOOKS LIKE
The venue can connect a guest’s activity history, crew and membership when shaping the next experience.
Explore these tools in detail- Leagues and programs
- Challenges and leaderboards
- Crews and group relationships
- XP, status and club records
- Player and visit history
- Membership engagement
- Relevant follow-up and rebooking
08 / Multi-VenueKeep the model consistent. Let the location be local.
Bring oversight and repeatable operations together with venue-specific resources, hours, pricing and systems.
WHAT THAT LOOKS LIKE
A new location starts from a defined operating model, then gets the configuration and readiness checks it needs.
Explore these tools in detail- Central venue switching
- Local hours and closures
- Activities, resources and pricing
- Taxes, terminals and providers
- Local display and venue configuration
- Fleet and integration health
- Launch readiness and rollout controls
09 / Intelligence & AutomationTurn context into the next useful action.
COPA connects live venue state to automation and Wally. Actions stay inside the same pricing, payment and permission rules as the rest of the operation.
WHAT THAT LOOKS LIKE
“Can we stay longer?” becomes an availability check, a real price and a confirmed action—not a guess.
Explore these tools in detail- Contextual guest and operator assistance
- Booking and service context
- Revenue and lifecycle workflows
- Operational signals and analytics
- Capability-based permissions
- Confirmation and audit evidence
- Provider reconciliation and safe fallbacks
CONTEXT THAT DOES THE WORK
Connected where it matters.
Availability and price have one authority.
COPA coordinates availability, temporary holds, membership benefits, credits and booking confirmation. An extension belongs to the same visit, rather than a disconnected transaction.
- Activity-aware booking
- Waitlists and rebooking
- Session extensions
- Pricing and membership context
The tab belongs to the visit.
Connect activity time, in-venue ordering and payment state. Staff can work with the full service context, including split payments, house accounts and exceptions.
- In-session and staff ordering
- Booking-attached tabs
- Kitchen and bar displays
- Refunds, comps and audit records
Authority stays in the platform.
Pricing, permissions and payment state belong to COPA. Staff interfaces, kiosks and Wally use governed capabilities instead of inventing their own rules.
- Role and capability boundaries
- Confirmation for sensitive actions
- Audit evidence
- Reconciliation and safe fallbacks
THIS IS WHAT CONNECTED MEANS
One moment.
The whole venue responds.
The value lives in the handoffs.
See how the pieces work together.
GUEST → BOOKING → ROOM → COMMERCE
“Can we stay another half hour?”
A simple guest question touches more of the venue than it seems.
- 01
Check the space
Live availability accounts for the next booking and the activity resource.
- 02
Apply the right price
Membership benefits and venue pricing determine the offer.
- 03
Confirm the extension
The guest confirms before COPA changes the booking and payment state.
- 04
Keep the room in sync
The session gets the additional time and the team keeps the same visit context.
One extension. One visit. No separate booking to piece back together.
ILLUSTRATIVE WORKFLOWFROM YOUR CURRENT STACK TO COPA
A clear path
to one system.
You don’t have to decide every integration on day one. Start with the operation you want to run, then build a practical transition around it.
Map the stack
Start with your booking, membership, POS, staff and activity workflows. Identify duplicated work, disconnected records and systems you want to keep.
Shape your experience
Define your brand, activities, pricing, memberships and service model. Decide what guests see and how the team operates behind it.
Consolidate and connect
Move agreed workflows into COPA. Connect the specialist providers and equipment that remain. Plan data migration around the records that matter.
Prove it in the venue
Walk through booking, arrival, activity, ordering, payment and recovery with your team. Validate the actual hardware and permissions.
Roll out with a clear plan
Choose the first venue or workflow, train the team and set the go-live checks. Expand from a working operation.
THE QUESTIONS BEHIND THE DECISION
Let’s talk about the practicalities.
Does COPA replace every platform we use?
COPA has native booking, membership, credit and other venue applications that can replace separate products. Guest records, staff tools, leagues and device workflows are scoped to your venue and rollout. Payment rails, retained POS/KDS, activity engines, accounting and message delivery can remain. We confirm replacement coverage and migration before you retire a tool.
Can we keep our POS or activity systems?
That is part of the fit assessment. COPA includes its own commerce capabilities and provider adapters. We confirm the exact provider, hardware and supported workflows before proposing a setup; a provider name alone does not guarantee every feature is supported.
Will it look and feel like our venue?
That is the intent: a guest experience built around your brand, activities, memberships and service. We define the guest-facing surfaces and branding as part of your rollout. COPA is the operating layer behind that experience.
Do we need to replace everything at once?
The transition is planned around your venue. We map dependencies, the records that need to move, the systems that remain and the workflows to validate first. The goal is a controlled change your team can operate, rather than a promise of an instant switch.
Is COPA only for golf venues?
No. COPA was developed in a venue with golf simulators and darts, but its operating model connects guests, resources, activities, service and physical systems. We assess the fit for competitive socializing, racquet venues, bowling, training facilities and hybrid activity-and-hospitality concepts.
Where is COPA today?
COPA powers its original operating venue, Loft 19, and is preparing for broader operator rollouts. We are opening conversations around venue fit and design partnerships. Current availability, branding requirements and integration scope are agreed for each deployment.
YOUR BRAND. YOUR PLATFORM. YOUR CUSTOMERS.
You built the experience.
Keep the relationship.
Run your whole venue while staying unmistakably you. COPA is working with select golf and experience-venue operators as it expands beyond its first live venue.
Request a demoBecome a design partner