IrisVR Prospect is shutting down.

The history of IrisVR and Prospect

IrisVR launched in 2014 and built Prospect into one of the leading VR design-review tools in AEC. Resolve’s founders, Angel Say and Russell Varriale, spent years building in the same category as IrisVR’s Shane Scranton and Nate Beatty.

As two New York-based teams chasing a similar vision, there was plenty of friendly competition and most importantly a shared belief that VR could change how design and construction teams review their work.

The Resolve team has always enjoyed the friendly competition with IrisVR and appreciated having another team pushing the category forward alongside us. However, the end of Prospect does not mean the end of VR for AECO.

Migration plan for Prospect, step by step

Migration takes time. Treat it as a planned project with an owner and a deadline, not a scramble in August. With Resolve's integrations and the outline below you can migrate in less than an hour.

1. Inventory what depends on Prospect

List active projects using it, the people trained on it, and the systems your Prospect issues and annotations feed into.

2. Get your data out

Back up your issues and screenshots per Autodesk's documentation. If you've synced issues to Autodesk Forma, they come into Resolve automatically. Models can't be directly extracted, since Prospect applies a proprietary format on upload. Resolve ingests Revit, Navisworks, and anything viewable on Forma.

3. Consider hardware upgrades

Prospect ran on tethered headsets and dedicated PCs. A wireless headset like the Meta Quest 3 removes that hardware dependency and lowers the barrier for new users. It's much easier to use VR today than it was in 2016.

4. Map out your VR review workflows

Document how teams move from model upload to issue tracking today, so you can replicate it after the migration, not rebuild it from scratch.

5. Evaluate replacements on stability, not just features

• Is BIM review the core product, or one feature in a larger catalog that could get cut?
• Is there an active team still shipping updates?
• Can you export your data again if you ever need to leave?
• Does the workflow span more than a headset, so one platform issue can't strand your team?
• Does it integrate with your existing cloud workflows?
• Can it handle your model types without hours of manual prep?

6. Run a trial before the deadline, not after

Move a real project onto the new tool while Prospect still works as a fallback. Testing now is lower risk than testing under pressure in September.

‍

Resolve as a Prospect replacement

IrisVR built Prospect around tethered PCs driving the headset. Resolve made the opposite bet: a proprietary rendering engine built for standalone headsets from day one so that anyone could get started with VR. That's why full federated models run on a wireless Quest today, with no file trimming and no workstation to manage.

Resolve was also first to connect VR to Autodesk BIM 360, now Forma, so that multiple stakeholders could easily get inside the same model at once. And since then Resolve's support for industry workflows has expanded: data from Autodesk, Procore, Revizto, and Newforma all flows in and out without manual workarounds.

If you're migrating from IrisVR Prospect to Resolve you'll find that Resolve expands the set of functionality your teams are already used to.

Our offer for Prospect customers

IrisVR Prospect is reaching end of life in September 2026, without any further product support or renewals. 

We’re here to make the transition easy for you. From now until September 30, we’re offering former Prospect customers up to 5 free VR headsets when they sign up with a Resolve team package.

For BIM managers, that turns a tooling decision into a planning decision. Now is the time to plan migration to a new system.

‍