TL;DR: A VR architectural walkthrough lets a client, buyer or design team stand inside a building before it exists, at real scale, and look around. Whether you need a custom build depends on which of three jobs it does. For internal design review, the real-time plugins that connect to your modelling software are often enough, and a studio should tell you so. A custom app earns its cost when the walkthrough is a sales tool for off-plan property, when buyers need to configure units and finishes, when several people review together, or when it has to run unattended on a headset in a sales gallery. The hard parts are rarely the VR itself: they are turning BIM and CAD into something that runs smoothly, keeping it in sync as the design changes, and matching the expectations a still render has already set.
Architects, developers and property marketers have used rendered stills and flythrough videos for years. They work, but they put the viewer behind a camera someone else chose. A headset puts them in the room. They can turn around, check the view from the kitchen, judge whether a ceiling feels low and walk to the window. That sense of scale is the thing VR does that no other format matches, and it is why the question comes up in almost every conversation about selling or approving a building that is still drawings.
This guide is for practices, developers and marketing teams deciding whether to commission one, and what to expect if they do.
Three different products that share one name
"VR walkthrough" covers projects that have very little in common once you scope them. Name yours first.
Design review
The audience is the design team, consultants and the client, during design. The model changes weekly. What matters is getting the current version into a headset quickly and accurately, catching problems with sightlines, clearances and proportions while they are still cheap to fix. Polish matters less than speed and fidelity to the drawings.
Client and stakeholder presentation
A pitch, a planning consultation, a board approval. One curated experience, shown a handful of times, often guided by someone from the practice. It needs to look good and be reliable on the day, but it has a short life.
Off-plan sales and marketing
The audience is the public: buyers deciding on a home or tenants choosing office space that is not built yet. It runs in a sales gallery for months, often on shared headsets handled by staff who are not technical, and sometimes on buyers' own phones and laptops at home. It has to be polished, robust and easy to start, and it usually needs to show real inventory: which units exist, which are sold, which finishes are offered.
These three differ in audience, lifespan, device and how often the content changes. A quote that does not ask which one you want is guessing.
Buy before you build
Real-time visualization tools that plug into common modelling software can put a design into a headset with very little setup. Plugins and engines such as Enscape, Twinmotion and Unreal Engine are widely used for this, and their feature sets change often, so check what the current versions support for your modelling tool and headset. For many practices doing internal design review, one of these is the right answer, and paying a studio to build a custom viewer would be wasted money.
A custom application starts to make sense when you need things those tools are not designed for:
- A branded sales experience with your development's identity, onboarding and flow, rather than a viewer interface.
- Configuration. Buyers choosing a unit, switching between kitchen finishes or flooring options, seeing their selection in place.
- Live data. Availability, pricing or floor plans pulled from a sales system so the experience never shows a sold unit as available.
- Unattended operation. A headset that boots into the experience, resets between visitors and cannot be wandered out of.
- Multi-user sessions. A sales agent and a buyer, or a remote client and the architect, in the same model at once.
- Reach beyond headsets. The same model on the web for buyers abroad, or as an AR scale model on a tabletop.
If your list has none of these, start with an off-the-shelf tool. If it has two or more, the custom route is usually worth pricing. Our vertical SaaS build vs buy guide walks through the same decision in general terms.
The model is the project
Most buyers arrive with a Revit, ArchiCAD, Rhino or SketchUp model and assume the hard part is done. It is not, and this is where budgets go wrong.
A BIM model is built for coordination and documentation. It carries every duct, pipe, structural member and hidden layer, much of which nobody will ever see in a walkthrough, and its geometry is not organized for real-time rendering. Getting from that to a scene that holds a steady frame rate on a standalone headset means stripping what is not visible, simplifying geometry, rebuilding materials so wood, stone and glass read correctly, and adding the furniture, landscaping and context that the architectural model usually lacks. We cover that workstream in depth in the 3D content pipeline behind an XR app.
Design changes are the hidden cost
Buildings change through design development, and a walkthrough has to follow. If every revision means someone rebuilds the scene by hand, the cost repeats with each change, and the walkthrough falls behind the drawings. The single best investment in an architectural XR project is a repeatable export path: a defined set of steps (partly automated where possible) that takes an updated model and produces an updated build, keeping the hand-made materials and furniture intact. Ask any vendor how a design change flows through their pipeline and how long it takes.
Realism versus frame rate
Clients have usually already seen photoreal still renders. A real-time scene in a headset has to draw the whole room twice, once per eye, many times a second, which leaves far less budget for lighting than an offline render. Precomputed ("baked") lighting can look excellent but has to be recalculated when the design changes. Fully real-time lighting updates instantly but costs performance. Most projects mix the two. Set expectations early by putting a test room on the target headset before agreeing a look, rather than comparing against a render.
Device choice follows the setting
- Standalone headsets suit sales galleries and site visits: no cables, quick to hand to a visitor, but with limited graphics budget, so scenes need careful optimization.
- PC-tethered headsets handle much heavier scenes and suit design review studios with a workstation, at the cost of cables and setup.
- Web and 360 views reach remote buyers on any device without an install, with less immersion. See web AR without an app for what browser-based delivery can do.
- Tablet or phone AR can place a scale model on a table in a meeting or show a building in context on site.
Choosing an XR headset compares the device trade-offs in detail. For a sales gallery running several headsets daily, device management, kiosk mode and hygiene matter as much as the model; enterprise XR rollout covers that operational side.
Comfort and scale
Architecture is one of the kindest XR use cases for comfort, because people mostly stand and look. It still goes wrong in predictable ways. Smooth joystick movement through a large building makes some visitors queasy, so teleporting between points, or walking within a room-sized play space, is the usual default. Scale must be exactly right: a model imported at the wrong unit or with the floor at the wrong height makes ceilings feel wrong, and the experience then misleads the very people it is meant to help. Our VR motion sickness guide and XR interaction design guide cover the design patterns.
First-time users are common in sales settings. The experience should make the first thirty seconds obvious without a staff member explaining controls, and offer a guided mode where a salesperson drives and the buyer only looks around.
Interactivity that earns its place
Every feature costs build time and maintenance. These are the ones that tend to pay off:
- Finish and option switching in place, when buyers choose from defined packages.
- A unit or floor selector linked to real availability.
- Time of day and sun position, when light and views are part of what is being sold.
- Measurement and annotation for design review, so comments land on the exact spot in the model.
- Shared sessions where two or more people see the same model and each other, for remote clients or design teams. Mixed reality collaboration covers what multi-user XR involves.
Resist adding everything. A focused walkthrough that runs smoothly beats a feature-rich one that stutters.
What drives the cost
We do not publish generic price figures, because the spread between projects is wide, but the drivers are consistent:
- How much of the building is explorable, and how many unit types or options exist.
- The state of the source model, and how much furniture, landscaping and context must be created.
- The target device and the visual standard expected.
- Integrations with sales or inventory systems.
- Whether it must run unattended, on many devices, for months.
- How often the design will change during the project.
What an XR app costs explains each driver. For a first build, scoping a single unit type or one floor as an XR proof of concept tests the pipeline, the look on the real device and how buyers react before committing to the whole building.
Where Null Studio fits
We are an AI-native software studio building across AI automation, custom software and XR. Our XR work includes MR Camera, a multiplayer mixed reality environment where several people place and interact with 3D models in the same space, which is the core mechanic of collaborative design review; ERIS XR for ARCortex, an emergency response platform that helps firefighters pre-plan and train by blending digital and physical spaces in real time; Planes XR, location-based AR for ARCortex connected to OpenSky live flight data; and Nystag, clinical VR eye-tracking on the Vive Focus 3.
For architectural projects, we start by asking which of the three jobs you need. If an off-the-shelf plugin will do, we will say so. When a custom build is right, we scope the content pipeline and the update path before anything else, because that is where these projects succeed or stall. If you are comparing studios, our guide to choosing an XR development company lists the checks we would want you to run on us too.
A short checklist before you commission
- Is this for design review, a presentation or public sales?
- Have you tried an off-the-shelf real-time tool with your model?
- Which modelling software and file formats will the source come from?
- How often will the design change during the build, and who triggers an update?
- Which device, in which setting, used by whom?
- Which interactive features are essential, and which are nice to have?
- Does it need live availability or pricing from another system?
- Who owns the source project and optimized 3D assets at the end?
Planning a VR walkthrough for a development, a pitch or a design review? Book a demo and we'll tell you honestly whether you need a custom build, and if so, how we'd scope the first phase. See our XR work: MR Camera shared mixed reality, ERIS XR and Planes XR for ARCortex, and Nystag clinical VR.