Start with the same project, not just the same game name
A buyer looking for interactive game equipment may receive proposals headed LED floor, reaction wall or interactive room. Those labels identify a format, but they do not define the complete venue experience. Before requesting quotes, describe the intended audience, room geometry, proposed game mix and the way staff will run a session. Include the constraints you already know and clearly mark the ones that still need a survey.
Send that same brief to each supplier. If one proposal is for a single focused room and another is for a connected multi-zone concept, the headline amounts are not comparing the same scope. CYDON's Starter, Pro and Flagship descriptions are project-scoping paths, not fixed equipment packages. Use the scope discussion to establish what the proposal is actually intended to deliver.
Break the proposal into scope layers
Create a comparison sheet with a separate row for physical equipment, selected game content, operating software, site preparation, delivery and service. Under each heading, ask the supplier to identify the included items and the responsibility for anything excluded. The purpose is not to make every supplier use identical terminology. It is to prevent a short equipment list from being mistaken for a complete installed project.
For an LED interactive floor, the published CYDON description explains a game surface that gives visible feedback as players move, pursue targets and respond to the selected content. That is a useful starting point for discussing the experience. It does not tell you every item in the final order or establish one universal room requirement. Request the configuration and room plan for your own project rather than copying a catalogue example into a purchase specification.
- Physical scope: named equipment, quantities and the proposed arrangement.
- Content scope: selected games, rules and any configuration work to be confirmed.
- Software scope: the functions and terms included in this proposal.
- Delivery scope: who prepares, installs, commissions and accepts the project.
Ask what the software line actually includes
The word software is too broad to settle a procurement decision. Ask which operating functions are included, which require an additional agreement and which are not being offered. Content configuration, update arrangements, licensing, supported integrations and service responsibilities belong in the scope discussion. Do not assume that a connected-space concept means every possible integration is already part of the quoted system.
CYDON's platform page treats equipment, game content and operation as a connected project and asks buyers to confirm the software and integration scope. Use that boundary when reviewing a proposal. For each function important to your venue, request a description and an appropriate demonstration. An explicit not included is more useful than a broad label that leaves the operating team to discover the limits after installation.
Keep local work and logistics visible
A project comparison should identify who is responsible for room preparation, access, power and network routes, delivery handling, installation and commissioning. Where a task depends on the venue or a local contractor, record that dependency instead of treating it as a supplier omission or assuming it is free. Ask for the site information the supplier needs before it can confirm the installation scope.
The CYDON installation guide separates project planning from a final installation specification. Apply the same discipline to quote review: an example game footprint is not the lease area, a completed layout or an approved capacity calculation. If you need a local compliance assessment or equipment-specific documentation, make that a stated requirement. This guide does not establish a certification or guarantee that a particular installation will meet local rules.
Define acceptance before selecting the final proposal
Write a short acceptance plan around the exact experience you intend to operate. It can describe the selected game, a session start and reset, the operator actions to be demonstrated and the documentation to be delivered. The final criteria should be agreed with the supplier and the people responsible for the venue. This makes acceptance a project discussion rather than an assumption based on an attractive promotional clip.
A gameplay video can help a buyer understand a format, but it does not by itself prove throughput, maintenance requirements, revenue or the complete installation scope. Treat those as separate questions requiring appropriate evidence. Likewise, a game score is not a professional or clinical assessment. Keep promotional impressions, proposed operating methods and verified project commitments in separate columns.
Turn missing answers into a clarification round
After the first comparison, list the unanswered questions and send the same relevant clarification request to each supplier. Ask for a revised scope table, not just a revised total. Keep previous proposals and the agreed changes so your team can see which version it is evaluating. If one supplier changes the game mix or project assumptions, note that change before interpreting the price difference.
For your next CYDON project discussion, share the venue location, available room information, intended audience and preferred game systems. A plan or drawing is more useful than a request for the cheapest room without context. The aim is to reach a proposal that your purchasing, operating and installation teams can all interpret, with the final equipment, software and service commitments stated in the project agreement.
Our planning perspective
Our suggested comparison unit is a playable, supportable experience rather than a box of equipment. A useful quote should connect the selected physical game to its content, operating software, room preparation and acceptance demonstration. A lower equipment line does not establish a lower project cost if another proposal includes work that the first leaves to the venue. This is a procurement framework, not a claim about any supplier's pricing. The practical next step is to place unresolved scope items in a shared clarification list and ask each shortlisted supplier to answer the same questions before comparing the final proposals.
Buyer decision checklist
- Use one venue brief and one proposed game mix for every supplier you compare.
- Mark each line as included, optional, provided by the venue or not yet confirmed.
- Request the named content and software scope instead of relying on a generic software label.
- Separate freight, local preparation, installation, commissioning and service responsibilities.
- Agree a demonstration and acceptance checklist for the exact configuration.
- Keep unresolved items visible; do not turn missing information into an assumed zero cost.
Sources and scope
Source material supports the stated facts, not a guarantee of capacity, revenue, safety certification or project outcomes. Final equipment and software scope require a project review.