Budget the experience that will actually open
Describe the activation in one paragraph: who participates, what they do, how long the complete cycle is expected to take and what they receive. Then identify the number of independent positions and the required operating hours. These inputs help turn a creative idea into a comparable scope.
A headset rental, an AR application and a staffed XR filming zone are different deliverables. Even within one format, existing content and a new branded world create different preparation work. Compare proposals only after their visitor journeys and responsibilities are clear.
Use budget lines that reveal dependencies
| Component | What to specify | What can change the scope |
|---|---|---|
| Equipment | Complete stations, accessories, power and mounting | Additional positions, computers, tracking or spectator displays |
| Content | Existing material, adaptation or new environments | Product modelling, language versions, animation and revised brand assets |
| Development | Visitor actions, operator controls and recovery | New interactions, integrations and offline behaviour |
| Space and installation | Participation, queue, service and technical areas | Venue access, scenic build, camera distance and installation windows |
| Operation | Staff roles, hours, handovers and technical support | Longer opening, extra sessions or more complex guest assistance |
| Output and reuse | Media delivery, licences, files and future deployment | Hosting, new event adaptations and ongoing maintenance |
Identify client-provided work beside supplier work. If the brand team supplies product models, specify their condition and delivery date. If the venue supplies connectivity, define the required service and test access. Moving a line off one invoice does not remove it from the project.
Worked example: one launch objective, two scopes
Imagine a hypothetical launch intended to explain a product environment and start a sales conversation. Proposal A provides two headset stations using an approved existing experience, with staff introduction and a nearby discussion point. Proposal B provides a camera-based XR scene that produces a short branded clip for each guest.
A needs confirmed content use, device preparation, fitting, session support and equipment reset. B needs scene design, camera and lighting integration, capture, review and a tested media handover. Both need a queue and staff, but the roles and timing differ. Comparing only headset rental with the price of a screen would miss most of the decision.
Suppose the client then adds two languages to A and personalised video delivery to B. Treat those as explicit scope changes. For A, check menus, instructions and any narration. For B, check matching files to guests, the delivery interface and failed transfers. The example shows how small requests can affect several budget lines without assigning invented prices.
Separate content approval from technical readiness
A beautiful concept image does not establish the workload needed to run it live. For virtual production, Epic Games' guidance calls for testing content against the intended stage configuration. Budget prototype and final-system checks as deliverables, with named participants who can approve the result.
For VR and AR, confirm the actual device and application combination, the full scene and the reset procedure. If the proposed content is still being adapted, ask which milestone will demonstrate its event suitability. Include time to act on findings instead of treating rehearsal as a ceremonial last step.
Clarify licences and recurring costs
Ask which software, content, music and asset permissions apply to the intended use. Valve's Steam PC Café Program is one example of a commercial venue route for participating VR content. The appropriate licence and available titles still need confirmation for the specific project.
For repeat events, separate reusable content from recurring hardware, delivery, setup and operation. A new venue can need a revised floor plan or technical configuration even when the scene stays the same. Specify who maintains the application, updates content and checks compatibility before each run.
Ways to simplify while preserving the purpose
Reduce scope by changing optional elements that do not support the main outcome. One well-tested scene may be more useful than several rushed environments. A staff-led handover may avoid a new integration when the process already includes a conversation. A shorter approved interaction may improve the cycle, but its explanation and reset still need time.
Have the supplier show what each alternative changes for visitors and operators. Avoid an unexplained percentage discount that leaves both parties with different assumptions about support, delivery or future use.
Before requesting a final quote
Confirm visitor outcome, format, independent positions and operating hours.
List content status, languages, brand assets and approval owners.
Provide the venue plan, access schedule, power and network assumptions.
Define staff roles, testing, recovery, media delivery and licences.
Ask for initial, recurring and optional work to be shown separately.
Common mistakes are pricing only visible equipment, excluding guest handover and assuming reuse eliminates preparation. Share the complete brief for XR video zones or interactive installations, including the proposed VR and AR equipment where relevant.