Most Virtual Reality Budget Is Training Budget, Not Marketing Budget
Virtual reality projects that survive past their first year almost always have an operational job. Induction for a site where mistakes are dangerous. Emergency drills that cannot be rehearsed at full scale. Equipment maintenance procedures on machinery that cannot be taken offline for a class. Clinical and hospitality service scenarios where the point is behaviour under pressure rather than knowledge. Sales environments where the asset is unbuilt or too large to show.
That matters for procurement because a training commission is judged against a course it replaces, with a defined audience, a repeat cycle and an owner in the operations or learning function. A marketing commission is judged against an event and disappears afterwards. Decide which one you are buying, and put the owner's name on the project before the first workshop, because unowned headset programmes stop being used within months of the launch photographs.
You Are Buying a Programme to Operate, Not a File to Play
The virtual reality software is one line in a longer bill. Headsets have to be bought, configured, enrolled in a management system, charged, cleaned, updated, stored securely and replaced when they are dropped. Somebody has to hand them out, start sessions, help the person who has never worn one, and collect the results. Without that person, the kit sits in a cupboard.
Ask every candidate to quote the operating side explicitly: device provisioning and enrolment, the tool used to push new builds, a spare unit allowance, consumables such as hygiene liners, and either training for your staff or a rate for an operator. A proposal that covers only content development is not cheaper, it is incomplete, and the gap lands on whoever inherits the project.
Write the Learning Outcome Into the Contract
A virtual reality scenario that impresses visitors and teaches nothing is easy to build. Guard against it by specifying what the trainee must be able to do afterwards, how the simulation will assess that, and where the result goes. Scores, completion records and error events should export to the learning system you already run rather than living in a supplier dashboard nobody logs into.
Insist that subject matter experts from your own side shape the scenario and sign off the content, and schedule their time in the project plan, since their availability is the usual cause of delay. Agree what counts as a pass, how retakes work, and whether the record has any compliance weight. If it does, the audit trail has to be designed in from the start rather than added once an inspector asks.
Virtual Reality Hardware Locks You In for Years
Standalone headsets are the practical default for anything that has to travel around a site or between offices, and they set a ceiling on visual fidelity. Tethered systems driven by a workstation give you far more detail and tie the experience to a room, a power supply and a technician. Enterprise device management, account provisioning without personal sign ins, and a supply of identical units matter more than raw specification once you go past a handful of users.
Confirm which platform the content is being built for and what porting to another would cost, because that answer is your exit price. Check availability and support locally, plan for import and clearance time rather than assuming next day delivery, and buy spares in the first order. Ask whether the build depends on features unique to one manufacturer's runtime.
Exhibitions and Attractions in Dubai Are a Different Purchase
Public facing installations at trade events, malls and visitor attractions are judged on throughput, not depth. A session has to be short enough that a queue keeps moving, self explanatory enough that a stranger succeeds without a briefing, and safe enough that a person wearing a headset in a crowded hall cannot walk into anything. Staffing, a defined stand footprint, cleaning between users and insurance are part of the specification, not extras.
Ask for a session length target and a realistic figure for people handled per hour, then check whether the content design matches it. Seated experiences move faster and fail less. Multi user sessions look impressive and halve your throughput. If the installation runs across several days, agree who is on site each day and what happens if a unit fails at the busiest hour.
Comfort and Accessibility Are Design Constraints
Motion discomfort ends virtual reality sessions and damages the internal reputation of the whole programme. It is mostly a design problem: artificial movement the user did not initiate, low frame rates and long sessions are the main causes, and teleport style movement, stable horizons and short scenes largely solve it. Ask candidates how they handle it rather than whether they do.
Fit and audio matter as much. Headwear, prescription glasses, hearing requirements and left handed users all need accommodation, as do people who simply do not want to put a device over their face, which is why a screen mirror and a flat alternative version are worth having. Content should exist in Arabic and English with audio and subtitles, and the interface labels need the same treatment as the narration.
Ask How the Content Gets Updated
Procedures change, branding changes, and the runtime engine the experience was built in ships breaking updates. A scenario that cannot be edited without the original team is a depreciating asset with a hard stop. Require the source project, the asset library, documentation of the build process and clarity on any engine or middleware licence that sits between you and a rebuild.
If you expect frequent changes, ask whether the scenario can be driven by a configuration file or an editor so that your own team can adjust steps, text and thresholds without a developer. That capability costs more at the start and is usually the difference between a programme that lasts and one that is quietly retired.
Comparing Proposals Fairly
Send one document containing the audience, the session length, the platform, the number of users at peak, the assessment requirement, the languages and the update expectation. Score the replies on the operating plan and the update path as heavily as on the visuals, and ask for a reference site where the programme is still in weekly use rather than a launch case study.
If the requirement is really an overlay on the physical world rather than a replacement for it, compare with augmented reality teams, and if the story can be told linearly, a filmed or animated production will reach more people for less. Where the simulation has to talk to your existing systems, involve enterprise software developers early. Verified profiles and client references for virtual reality agencies are on Edvido, and one brief sent to several of them will tell you quickly which have run a programme rather than a pilot.