Commissioning an immersive property experience is unlike commissioning a set of renders. The result is a visual product, a data product and a hosted service at once, used in front of buyers for as long as the project is on sale. The questions asked before signing matter as much as the creative brief.

The checklist below applies to any supplier, ourselves included.

Model fidelity: built from what, checked against what

Ask which drawings the 3D model will be built from, which revision, and what happens when the design changes during production. A model built from approved architectural drawings and checked against them is a different thing from one built to resemble a concept image.

Then ask where the model stops. Which unit types are modelled in full, which are represented by plans, and which interiors are furnished? Views need particular care. A view from an upper floor is only as reliable as the data behind it, and unless it has been verified with proper survey and geospatial inputs it should be presented as illustrative. Sun and daylight studies are simulations too, and their assumptions should be stated.

Approved data: one source of truth

Every price, area and availability status in the experience should reconcile with one master inventory approved by the developer. Verify who on your side owns that inventory, who is authorized to release updates, and how a change is confirmed once it appears on screen.

Ask how the supplier handles discrepancies. If the area on a floor plan differs from the area in the inventory file, the question should come back to you before anything is published.

Integration: file-based or API

This is where assumptions most often go wrong. There are two broad ways to keep inventory current.

  • File-based exchange: your team exports an approved file in an agreed structure, and the experience is updated from it on an agreed schedule. It is simple, easy to audit and needs no access to your systems.
  • API integration: the experience reads directly from your CRM or inventory system. It removes manual steps, and it requires discovery, development, security review and testing against your specific system.

Neither is automatically better, but the proposal should state plainly which one you are buying. At RUWAA LABS the current baseline is file-based. Live CRM integration is scoped and validated separately for each project, and analytics and reporting on buyer engagement are at pilot or roadmap stage. Any supplier should be able to give an equally direct account of what works today, what is custom and what is planned.

If a capability matters to your launch, ask to see it working, and ask to see it written into the scope.

Hosting and access

An interactive 3D experience can run in different ways: on dedicated hardware in a sales gallery, on a consultant's device, or streamed from cloud servers to a browser. Ask where the experience will be hosted and in which region, what performance to expect on mobile connections, how many people can use a streamed session at once, and what happens when that limit is reached.

General assurances about data location are not enough. Hosting region and streaming capacity depend on technical availability and contract terms, and they should be confirmed through review, in writing, for your project. If your organization has data residency requirements, raise them at the start.

Who can open the experience: sales staff only, brokers, the public? How are accounts issued and withdrawn? If the experience captures enquiries, who holds that data, under which privacy notice, and how is consent recorded?

Support and licensing

The experience has to be maintained for as long as the project is on sale. Verify the support period, hours of cover, response times and the route for urgent issues during a launch. Ask what counts as routine, such as inventory updates, and what counts as a change request, such as a new unit type. Ask who your point of contact is, and whether that contact owns the resolution or passes you to a third party.

On licensing, clarify what you are licensed to use and for how long, whether stills and films can be used freely across your marketing, what the recurring fees cover, and what happens when the term ends. Ask whether the model and content can be handed over, in what form, and whether the experience depends on software licensed from others.

Scope note: capabilities vary by project. Hosting location, streaming capacity, integration method and support terms are confirmed through technical and contractual review, and only the written scope should be relied on.

Put it in writing

A good supplier will welcome these questions, because clear answers at the start protect both sides. The useful output is a short written register: each capability, its status, who is responsible for the inputs it depends on, and how it will be accepted.

An immersive experience exists to make a development easier to understand. The commissioning process should do the same for the experience itself.

Editorial noteThis is an editorial explainer from RUWAA LABS. It contains no market statistics, and the capabilities and integrations it describes depend on the confirmed scope of each project.