Developers usually meet an interactive sales experience as a finished thing: a tower on a screen, floors that open, homes compared side by side. Behind it sits a production process with a clear order, and several of its steps depend on the developer's own team.
This is how such a project typically moves from plans to presentation, and where the decisions fall.
Intake: drawings first
Everything starts with the approved drawings. They are the source of truth for the whole project, and a complete intake usually includes:
- The site plan and approved architectural plans, sections and elevations
- Floor plans for every unit type
- Facade, material and finish specifications
- Landscape and interior design drawings, where they exist
- The unit inventory: numbers, types, areas, prices and status
- Brand guidelines and approved project facts
Intake is also where gaps and contradictions surface: a floor plan that does not match the elevation, an interior finish that has not been chosen, a unit type still under design. Each open item is logged and returned to the developer as a specific question. Honest questions at this stage prevent rework later.
Intake fixes the baseline too. Both sides agree which drawing revision the experience is built from and how later design changes will be handled.
Building the 3D model
The model is built from the drawings, in layers: first the massing and the site, then the facade with its true proportions, openings and materials, then the floors and unit types, and finally the interiors the scope calls for.
Two decisions shape this stage. The first is level of detail: which spaces are modelled in full, which are shown as plans, and which unit types are furnished. Furnished interiors take the most effort, so choose them deliberately. The second is how to treat what is not yet known. Neighbouring buildings, landscaping still in design and views from upper floors are often indicative, and the finished experience should label them as such.
Quality assurance against the source
QA rests on one principle: the model is checked against the drawings, never against an earlier render. Dimensions, room counts, door and window positions, balcony depths and floor numbering are compared with the approved set, materials with the specification, and Arabic labels with English ones.
Every figure and every wall in the experience should be traceable to a document the developer has approved.
QA covers behaviour as well. Does each unit open the correct plan? Does the experience perform acceptably on the hardware it will actually run on, from a gallery screen to a consultant's tablet? A fault found here is simple to correct. A fault found by a buyer costs more.
Connecting the unit inventory
The inventory is what turns a 3D model into a sales tool. Each unit in the model is matched to a record: its number, type, floor, area, orientation, price and status. The match has to be exact, so consistent unit naming across drawings and spreadsheets matters.
In the current RUWAA baseline, inventory is exchanged through structured files: the developer's team exports an approved file in an agreed format, and the experience is updated from it on an agreed schedule. A live connection to a CRM through an API is a separate piece of work, scoped, tested and validated for each project. The file-based route can serve a launch well, provided someone owns the update routine.
Scope note: analytics and reporting are at pilot or roadmap stage, and any live CRM integration is validated separately. What applies to your project is what the written scope confirms.
Review rounds
A common pattern is three structured rounds: the massing and facade, then the unit plans and interiors, then the complete experience with data in place. Each round has a named approver on the developer's side and a single consolidated list of comments.
Consolidation matters because each team sees the experience differently: marketing looks at mood and brand, sales at how quickly a unit can be found, the project team at accuracy. One list, with conflicts resolved before it is sent, keeps the rounds few and the schedule predictable.
Training the sales team
An experience the sales team is not comfortable with will sit unused in a corner of the gallery. Training is therefore part of delivery. Consultants need to practise the journey: opening with the site, moving to the building, narrowing to the homes that fit a client's brief, comparing two options side by side.
They also need to know the boundaries: which elements are illustrative, how recent the availability data is, and what to do if a figure on screen differs from the latest price list. A short guide, a rehearsal with realistic client scenarios and a named contact for questions are usually enough.
Seen this way, the interactive experience is the visible end of a disciplined chain: approved drawings, a checked model, reconciled data and a prepared team. It is the sequence RUWAA LABS is organized around.
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.