What a VR Walkthrough Package Includes
A complete VR walkthrough package includes the built environment, a headset application for a named device, a non headset fallback version, defined finish or furniture variants, a stated number of revision rounds, and the delivery files with installation instructions. Frequently excluded and worth asking about explicitly: source files, future update rights, additional device targets, and the cost of a finish change after materials are built. Those exclusions are where quote comparisons go wrong.
Two quotes that look thirty percent apart often describe different products entirely.
The core deliverables
- Built environment covering the agreed spaces at agreed detail
- Headset application compiled for one named device
- A non headset version, whether desktop or tablet, for viewers who decline the headset
- Navigation and interaction system with comfort settings
- Defined variants, such as 2 finish packages or furnished and unfurnished
- A stated number of revision rounds, with what counts as a revision defined
- Delivery files, installation instructions and a device setup guide
What is usually excluded
Source project files, which most studios retain. Additional device builds, since a standalone headset and a tethered system are separate compiles. Ongoing hosting for any web version. Updates after delivery. Hardware itself. None of these are unreasonable exclusions, but discovering them after signing changes the economics of the project substantially.
The variant question
Finish packages, furniture layouts and exterior time of day are the variants that drive sales conversations, and they are priced separately by most studios. Decide which ones you actually need before quoting, because adding a second finish package after materials are built costs meaningfully more than including it in the original scope.
Update rights are the real long term term
Buildings change. Ask what a partial update costs, what a full rebuild costs, and whether the studio commits to availability. A package with no update path becomes a stranded asset the first time the unit mix is revised, which on a multi year development is close to certain.
The non headset version is not optional
A meaningful share of viewers will not wear a headset, and remote stakeholders cannot. A desktop or tablet version built from the same environment reaches them at modest additional cost. Packages sold as headset only quietly lose a large part of the audience they were bought to reach.
Support and setup
Someone has to install the application, configure the device, manage updates and handle the headset that stops working the morning of an event. Ask whether setup support is included and for how long, since a leasing team without that support will stop using the tool rather than troubleshoot it.
How to compare two quotes
Line up the spaces covered, the device targets, the variants, the revision rounds and the update pricing side by side. The cheaper quote is often cheaper because it covers fewer spaces, one device and one variant, which is a legitimate scope but not the same purchase. Timeline assumptions are covered in VR production timelines.
Get the exclusions written down
Ask the studio to list what is not included, in writing, before signing. Studios that answer that question directly are the ones that will handle a mid project change reasonably, and the answer itself is a useful signal about how the rest of the engagement will go.
Our VR services quote with explicit inclusions, exclusions and update pricing. Request a quote with your spaces and device target.