Why developers commission digital twins

In residential and mixed-use development, most units are sold before the building is finished. At that point the buyer has only static assets: renders, floor plans and a scale model. None of them let a buyer experience their own apartment — the view from their floor, the daylight, the distance to shared amenities.

A digital twin replaces all three with a single real-time environment. The buyer sees the project from outside, walks in, goes up to their floor and looks out of their own window. The sales team uses the same environment as a presentation tool, turning an abstract pitch into a concrete experience.

The commercial effect shows up in two places. Decision cycles shorten because the buyer resolves uncertainty faster. And remote selling becomes viable: an overseas investor can evaluate the project without travelling to the site.

  • Makes an unbuilt project explorable
  • Turns floor, aspect and view differences into something buyers can judge
  • Enables remote evaluation without a site visit
  • Gives the sales team one consistent presentation tool
  • Reuses the same asset for investor decks, trade fairs and digital campaigns

How a digital twin differs from renders and virtual tours

These three are routinely conflated. They are technically different, and so are their costs and use cases.

A render is a fixed image from one camera position. It can be beautiful, but it is not interactive — you cannot move. A 360° virtual tour moves you between pre-captured or pre-rendered points; the points are fixed and the space between them is not real.

A digital twin is a continuous 3D environment computed in real time. You go where you want, lighting responds to time of day, and — most importantly — the twin can be bound to data. When a unit sells, its state changes inside the twin. Renders and virtual tours cannot do that.

  • Render: fixed image, no interaction, no data binding
  • 360° tour: fixed waypoints, limited interaction, no data binding
  • Digital twin: free navigation, real-time lighting, live data binding

How MPANDO delivers: MTWIN and Sales OS

MPANDO's product in this space is MTWIN. It produces a photoreal project twin running on Unreal Engine 5 and joins it with MPANDO Sales OS in one ecosystem.

MTWIN is the experience layer: exterior, surroundings, shared amenities, interiors and unit selection. It can be configured for a sales-office screen, a representative's laptop, a trade-fair stand or browser delivery.

Sales OS is the operations layer: project inventory, customer records, reservations, offers, approval flows, payment plans, presentation history, reporting and commissions. Because the two are connected, a representative shows the project and starts the transaction on the same screen.

In practice this means you can scope either layer independently. If you only need the visual experience, MTWIN stands alone. If you want your sales operation on the same infrastructure, both layers go live together.

What project data is required

Twin production is built entirely from your existing project data. The list below reflects the typical inputs requested during discovery. Not every item must be complete — gaps are resolved as scope decisions.

  • Architectural drawings: floor plans and elevations in DWG, RVT or IFC
  • Site plan and plot boundaries; surrounding building masses where available
  • Unit schedule: block, floor, unit number, type, gross and net area
  • Material and finish decisions: façade cladding, joinery, interior packages
  • Existing renders, model photography and brand assets, if any
  • Sales process detail: price list, payment plan rules, roles and authority

Which project scales justify a twin

The threshold at which a digital twin becomes economically sensible depends less on project size than on sales value and sales duration.

A project with few but high-value units — villas or a boutique residence — benefits because each individual sale is large and buyer expectations are detailed. Large residential schemes with many repeating units benefit through scale instead: the same twin is used across hundreds of conversations.

Mixed-use developments, tourism investments and urban regeneration areas also fit well, because decision-making is multi-stakeholder and a shared visual language matters more.

Common mistakes

Where digital twin projects disappoint, the cause is usually scoping rather than technology.

  • Optimising only for visual quality and never connecting to the sales flow
  • Not assigning an owner for keeping unit data current
  • Skipping the enablement step that gets the sales team fluent with the tool
  • Starting production before design and material decisions are frozen
  • Building it for one launch event and never updating it afterwards