Recently VR Vision Group, ArborXR, PICO XR and Enel showed why enterprise VR training often gets stuck before anyone judges the headset properly: finance needs numbers, IT needs answers, and frontline teams need a problem worth solving.
Cover image: VR Vision Group
Part 2: Your VR Training Pilot Won’t Scale If Headsets Are Managed Like Demo Kits
Enterprise VR training doesn’t usually die because someone hated the headset. These things are cool, futuristic and fun to play around with.
It normally dies earlier, somewhere around the VR training budget meeting, the IT review, or the moment a CFO asks what the ROI and payback period is, and everyone suddenly becomes very quiet.
That was the clear message from the webinar on VR training budget approval, featuring Lorne Fade, Co-Founder of VR Vision Group; Matthew Hall, Chief Solutions Officer atArborXR; Dax Leepart, Commercial Director at PICO XR; and Brian Stice, Director of Strategic Operations at Enel.
Fade framed the problem plainly:
“Most VR training proposals never get funded. It’s not because VR doesn’t work. It does and the data is clear. The problem is how they get pitched internally.”
Plenty of enterprise XR still gets sold backwards.
Someone leads with the demo, the device, or the “look how cool this is” moment. The problems start when finance wants a model, safety wants risk reduction, IT wants security answers, and operations wants to know whether the training will make real work easier or create another scheduling headache.
That’s a lot for one headset demo to carry.
Finance Wants More Than A Good Feeling
Fade put it bluntly:
“Finance teams don’t work on hope. They work on models.”
VR training gets into trouble when the proposal compares the cost of VR against the upfront cost of doing nothing. In most organisations, the alternative isn’t free. Training already costs money, but the cost is often scattered across different teams and budgets.
Instructor time sits in one place, travel sits somewhere else, equipment downtime may disappear into operations. Retraining, facility use, admin time, safety incidents and senior staff supervision can all be treated as separate problems, even when they belong to the same training picture.
VR training has a stronger case when the current model gets costed properly. In the webinar’s example, a 500-person training population created around $600,000 in annual training cost once instructor hours, travel, downtime and overhead were pulled together.
The number will change by company, but the point is before a buyer can judge whether VR is expensive, they need to know what traditional training is already costing them.
One Pitch Won’t Work For Everyone
Different teams judge the same proposal through completely different lenses. A CFO wants payback period and cost per learner. A safety leader wants incident reduction. IT wants device management, security, support and update control. Operations wants less disruption. L&D wants better outcomes without creating a circus.
A single pitch deck built around something like “VR is immersive” won’t survive that room for long.
A stronger route starts with the problem each stakeholder already cares about. If the training issue is safety, lead with incident risk and safer rehearsal. If the problem is travel and downtime, show the cost of the current model. If the blocker is IT, bring device management and security into the conversation early.
VR training doesn’t need everyone in the company to like it for the same reason. It needs enough people to see how it solves their version of the problem.
A Buyer’s Perspective
The Enel section of the webinar was especially useful because Brian Stice spoke from the buyer side.
He described how Enel looked at VR training as part of a broader training strategy, covering safety, technical training, cross-training and upskilling. The company examined travel costs, retraining, insourcing opportunities and risky activities where workers needed a safer step between classroom learning and live practical verification.
Stice said:
“What I did was I started at the bottom. I went to talk to SMEs, [to] try to understand their gaps.”
It’s not the glamorous answer, which is exactly why it’s a good one.
A VR training project built around the people doing the work has a better chance of surviving scrutiny. It can point to real gaps, real frustration and real risk. A project that starts with “we should try VR” usually spends the rest of its life trying to prove it wasn’t just a technology idea looking for a home.
Stice’s buyer advice was just as direct:
“Talk to the people that are actually going to use it and understand the true challenges that you are going to be solving with this technology.”
Strong VR training proposals tend to start there: with the messy bit of work that needs better practice.
The First Pilot Should Be Narrow Enough To Measure
The webinar’s pilot advice was refreshingly sensible: don’t try to boil the ocean.
A good first VR training pilot needs a defined use case, a measurable baseline, an executive sponsor and a real operational constraint. Dangerous procedures, recurring onboarding, certification, equipment downtime, expensive travel and rare high-pressure events all give VR a clear job to do.
That fits the same pattern we’re seeing across enterprise XR use cases. The strongest deployments usually have a clear workflow, a defined user and a practical reason immersive technology improves the task.
A narrow pilot also helps buyers avoid the classic trap: proving that VR can work in theory, then failing to show whether it should scale in practice. The first phase should give the organisation enough evidence to decide what comes next, not just enough excitement to book another demo.
The Demo Is Only The Start
The webinar didn’t make VR training sound easy, which is probably why it was useful.
Enterprise adoption doesn’t reward the most impressive demo for very long. A good VR training project still has to explain the current problem, show the cost of doing nothing, bring IT in early, and give frontline teams a reason to care.
Hardware can open the conversation, but the business case, rollout plan and internal ownership decide whether anything survives beyond the pilot.
VR training has plenty of strong use cases, especially in dangerous, expensive or hard-to-repeat work. Getting it funded still takes the less glamorous bits: numbers, stakeholders, baselines, management plans and users who actually want the thing in their day.
The headset gets people’s attention, but the business case gets the purchase order.
