HomeTHE FOUNDATION

Hardware is the touchpoint
Software connects the experience

Plan content, game sessions and venue operation as a connected system. Confirm the exact software, integration and service scope for your project.

Content and connected terminals

Interactive hardware is the physical touchpoint. Game content defines the challenge. The software scope determines how sessions start, reset and record results. Confirm which content and controls are included in each selected system.

Venue operations

Our product handbook describes integrated venue functions including booking, payment and session records. Availability, payment providers, supported languages and integration responsibilities must be confirmed for the destination market and project.

A defined software and service scope

Ask for an itemised software brief: permissions, content updates, connectivity, data handling, integrations, licence terms, training and support. Bespoke analytics or AI features are separate requirements, not assumed standard capabilities.

A game quotation needs a software brief

The CYDON handbook describes an integrated software platform and software/content maintenance. Those descriptions are a starting point for a project discussion. Ask for the current quoted version, demonstrated functions and written licence and service scope; a handbook feature is not a promise that every destination or equipment combination includes it.

1. Record the games, modes and versions

For each selected room, list the hardware model, game modes, software version, interface languages and licence scope. For the illustrated GRID floor, the handbook shows safe green tiles, blue targets and red hazards. Use the proposed mode to demonstrate how a session begins, registers a target, ends and resets. Ask which controls are available to staff; do not infer them from the floor photograph.

2. Demonstrate operation and connectivity

Use a witnessed demo to define session start, stop and reset, staff permissions, displayed scores and any session records included in the quotation. Agree how each selected function behaves when the venue network or internet is unavailable and how it recovers. Record the test result and any function that requires connectivity. This checklist does not establish offline operation, shared control across rooms or a guaranteed recovery time.

3. Separate booking, payment and data responsibilities

The handbook describes booking, payment and session-related records. For your destination, ask which functions and providers are supported in the proposed version, who performs any integration and who is responsible for accounts, refunds and fault handling. Request a sample using demonstration data, plus the proposed storage, access, retention and export scope. Do not assume a third-party payment service, customer database or bespoke analytics is included.

4. Agree on updates, licensing and support

Request the delivered content list, licence duration and permitted use, update responsibilities, release procedure and any recurring charges or renewal conditions. Where branded content is proposed, ask for the relevant authorisation. Confirm how staff report faults, what remote access is permitted and which training and documentation are included. Neither a stated update practice nor a product photo establishes free future content, ownership of source code, an AI feature or a fixed support response time.

5. Make acceptance observable

Give each requested function a status: demonstrated and included; optional and separately scoped; or not confirmed. Attach the selected mode/version and the witnessed test result to the proposal. Specify who confirms unresolved items before ordering and which tests are repeated at handover. A useful acceptance record names the actual configuration and responsibility; it does not substitute for the local safety or installation review.

Handbook context: pages 4–5 and the GRID example on page 9. This is a buyer demonstration brief, not a confirmed specification or service agreement.

Software questions before you buy

Can the selected games run without internet?

Confirm this for the exact hardware, mode and software version. Ask for a demo with connectivity unavailable and record which session, booking, payment or update functions depend on it. The handbook and this page do not establish a universal offline capability.

Are content updates and future games included?

The handbook describes software/content maintenance, but the current proposal must state the delivered list, licence, update policy and any charges. Confirm these terms in writing; do not assume unlimited content or free future updates.

Does the software include local booking or payment integration?

These functions appear in the handbook. Ask which providers, languages and destination requirements are supported in the quoted version, and identify the integration owner. A listed function is not evidence that a particular payment provider is already connected.

What should I send for a software-scope proposal?

Share the country/city, venue type, selected games, project stage, opening target and the session, booking, payment or reporting requirements you want to discuss. Mark unknown items as unconfirmed. Download the brief below and add its summary to the existing project inquiry; agree with the team how to exchange files.

Bring a written software brief

Edit this checklist locally and mark each requirement as demonstrated, optional or unconfirmed. Downloading it does not submit an inquiry or send contact details.