Three questions to settle first
Before entering a proposal process, the answers to these three questions determine how accurate any quote you receive will be.
- What will this twin primarily serve: sales, investor communication, design decisions, or operations?
- Who will operate it: a sales representative, the buyer directly, or a technical team?
- Where will it run: a sales-office screen, a laptop, a browser, or a trade-fair stand?
What actually drives the timeline
Duration is the most common question in digital twin projects — but production speed is not what determines it.
The determining factor is how settled the project decisions are. If façade materials are unselected, floor plans are being revised, or the unit schedule keeps changing, production gets redone. On a project where decisions are settled, delivery proceeds predictably.
The most effective way to accelerate is therefore to freeze architectural and material decisions and finalise the unit schedule before production starts.
Steps to commission a digital twin
These six steps describe the path a typical project twin follows from first conversation to go-live.
01Discovery and objective setting
Establish project type, scale, location, unit count, target audience and commercial goal. The twin's primary purpose — sales, investor communication, design or operations — is settled here.
02Project data collection
Gather architectural drawings (DWG, RVT or IFC), site plan, façade decisions, material and finish selections, and the unit schedule. Missing data is identified and ownership for completing it is assigned.
03Scope and visual quality decision
Agree which areas are modelled (exterior, shared amenities, sample units, surroundings), the visual quality level, interaction scenarios and delivery platform. Scope is documented at this step.
043D production and real-time environment setup
The model is moved into the real-time engine; materials, lighting, environment and interactions are built. Visual sign-off is taken at interim deliveries and corrections applied.
05Integration with sales and data systems
Unit data, pricing and state information are bound. Where MPANDO Sales OS is used, inventory, offer and payment plan flows join the twin in the same ecosystem.
06Enablement and go-live
The sales team is trained on the tool, the presentation scenario is designed together, and the system goes live. An update owner and update cadence are agreed.