INTERACTIVE BUILDING MODEL

Interactive building model: spin the tower, pick a floor, pick a unit, see availability

A single-tower model built from renderings and running in the browser. Buyers spin the tower, tap a floor, pick a unit, and see its floor plan, area, orientation and whether it is still available, right on the project website or a sales center screen.

  • Building spin from renderings, available before construction
  • Unit table linked to the developer's CRM through an API or an admin panel
  • Self-hosted on Lotuz servers, with the server region chosen for your market
01

The base layer, live now: the BTH building spin

An apartment tower in Da Nang, built from 10 renderings before construction. Click the spin, toggle day and night, drag to look around.

This is the spin layer, running on CRM360, the platform we built ourselves. The unit mask and unit table layers are added per project; no delivered build of them is open to the public yet.

Open the tour in a new window →

02

The building model answers three questions: which unit, where, still available

The deciding moment is when a buyer already likes the project and is choosing which unit. A printed floor plan book answers slowly: one page for the location, another for the layout, and nobody knows whether the unit is still available. The building model puts all three answers on one screen.

We build the model as four separate layers: building spin, unit masks, unit table and integration. Separating them means changing one layer never rebuilds another: swapping renderings leaves unit data untouched, and changing prices leaves the imagery untouched. The unit table is the single source of data, and every screen reads from it.

Three places it is used: the project website, embedded in the product page; the sales center, on a large screen where buyers tap through themselves; and sent to buyers, as a link that opens the exact unit under discussion instead of a multi-page PDF.

03

The four layers of the model

Each layer has its own inputs, outputs and acceptance check.

Layer 1 · Building spin

A sequence of renderings around the tower, for example 36 frames at 10° intervals, in day and night versions. Buyers drag to spin and tap a floor to go deeper.

Layer 2 · Unit masks

Every unit has its own mask on every spin frame, exported from the 3D model as SVG. Masks are colored by status and highlight on tap.

Layer 3 · Unit table

Unit ID, floor, type, area in m² and sq ft, orientation, price, status, unit floor plan. One table, imported from Excel or an API.

Layer 4 · Integration

A multi-user admin panel, an API for the developer's CRM, embed code for the project website and links that open a specific unit.

04

Technical Specifications

The numbers we fix in the scope of work before building.

Minimum inputFloor plans and unit type plans (PDF or CAD), elevations or a 3D model, unit table
SpinFrame count agreed per project, usually 24 or 36 per rotation; day and night versions rendered separately
Reference scaleOne tower of 20 to 30 floors, 150 to 200 units. Multi-tower projects need a masterplan layer, see Interactive Masterplan
Unit dataOne table: unit ID, floor, type, area, orientation, price, status. Imported from Excel/CSV at build time, or read from an API
Status updatesThe sales team changes it in the admin panel, or the CRM pushes it through the API. No involvement from us per transaction
Runs on, embedsAny browser on phones, tablets, desktops and sales-center touch screens, no app to install. Iframe embed code for the project website; every unit gets a link that opens it directly
HostingLotuz servers, Singapore by default. Projects in the US or Europe are hosted in that region for fast loading
Languages, analyticsBilingual per project, switched with one button. Analytics on opens, most-viewed units and floors, exported as reports for the sales team
Not includedFree walking in 3D space, measuring in place of the drawings, deposits and contracts
05

Five steps, two approvals

Two approval points so the developer can schedule reviewers in advance.

1

Lock the data and scope

We receive the unit table and drawings, count the floor plan types and fix the number of spin frames. The number of types drives the workload, not the total unit count.

2

Build the model, render the spin

We build the tower and its surroundings from elevations or an existing model, then render the day and night frame sequences.

3

Unit layer

We export each unit's mask on each frame as SVG, add floor hotspots and link them to the unit table.

Approval 1: test build on a private link
4

Unit table, admin panel and branding

We import the unit table, build the admin panel or connect the CRM API, add the floor plan of each unit type, and apply the project's colors and logo.

5

Acceptance and handover

We test on real phones and screens, hand over the embed code, admin accounts and all data, and train the sales team on updates.

Review 2: sign-off on real devices, not on design images
06

What the developer sends, what we deliver

Developer sends

  • Floor plans and unit type plans, PDF or CAD
  • Elevations, sections or a 3D model of the building
  • Unit table: unit ID, floor, type, area, orientation, price, status
  • Project brand assets; CRM API documentation if we connect to it

Lotuz delivers

  • The building model, running in the browser on phones, tablets and desktops
  • Embed code for the project website and a link for every unit
  • A multi-user admin panel, or an API so your CRM pushes updates
  • The spin renderings, reusable in sales material
  • Admin account and all data after sign-off
07

In scope, and scoped separately

We say this upfront so nobody is surprised at sign-off.

Included in scope

  • Four layers: building spin, unit masks, unit table, integration
  • Day and night versions of the spin
  • Floor plan of each unit type, with interior renderings where available
  • Bilingual interface, set per project
  • First-year hosting, server region chosen for your market

Scoped separately, other services

08

Four 360 tours we operate ourselves, on one platform

These four tours are not interactive building models. Open them to check loading speed, navigation and mobile display, on the same technical platform as the product on this page.

09

Pricing by three components

Send the unit table and drawings and we return a scope with a budget range for internal approval.

ComponentPriced byNotes
Building spin Frames per rotation, day and night versions Lower with an existing 3D model; PDF-only projects add a modeling fee
Unit layer and unit table Number of floor plan types, not number of units A 189-unit tower with 9 floor plan types is priced on 9
Integration and hosting CRM API connection billed once; hosting billed monthly Hosting from year two is stated in the first quote
How we count: Workload is priced by the number of floor plan types. Units of the same type share one built floor plan and differ only by unit ID, floor, orientation and status in the unit table.
  • Contract-based, paid by acceptance milestones. Projects in Vietnam get VAT invoices; projects outside Vietnam are quoted in USD.
10

FAQ

Have you delivered an interactive building model yet?
The spin layer is live in the BTH Building tour above. For the unit mask and unit table layers we have no delivered build that is open to the public yet. If you need a studio that has shipped all four layers many times, we say so plainly.
We only have marketing floor plan PDFs, no CAD or 3D model. Is that enough?
Yes. We build the tower from the floor plans, elevations and existing renderings, with a modeling fee added. Unit floor plans are redrawn to read well on small screens.
How is availability updated?
The sales team changes it in the admin panel, or the developer's CRM pushes it through the API. Unit masks recolor from the unit table without our involvement.
Can it connect to the CRM we already use?
Yes, through a two-way API: the CRM sends status and prices over, and the model sends back which units a buyer viewed. We need the CRM's API documentation when scoping.
Will it load slowly for viewers in the US or Europe?
The server sits in the project's region, frames are compressed for the screen size, and the next frame preloads. US projects run on US servers.
What happens after sell-out, and who keeps the data?
The developer keeps all data and accounts after acceptance. Once sold out, the model can be shut down; only domain and storage fees remain if you want to keep it online.
11

Send your project files, get a scope and budget range

Send it by email, WhatsApp or Zalo. We reply with a scope of work and a budget range, no meeting required first.

Include this information for the fastest reply:
  • Project name, number of floors, units and floor plan types
  • Existing drawings: floor plans, elevations or a 3D model
  • The CRM or project website in use, if we need to connect
  • Target market and planned launch date
Lotuz Architectural Design Consultancy Co., Ltd. · 268 30/4 Street, Hoa Cuong Nam, Hai Chau, Da Nang
12

Three things we build in-house to make the model last longer and cost less

No third-party platform for the core, so we control price, speed and the project's data.

CRM360, our self-hosted tour management system

Built and run by us on our own servers: image upload, scene links, spins, day/night, link sharing, view statistics.

  • The BTH Building spin at the top of this page runs on it

Lotuz.AI

Our AI toolkit inside Photoshop: finishing renderings, relighting, night versions from day shots, sharpening. Used on every frame of the spin. On sale at lotuz.ai.

  • Day and night versions from a single render pass

Lotuz Sync

Our own tool that syncs SketchUp models to 3ds Max and Corona. The architect's model goes straight to the render farm, and the unit masks come from the same model.

  • One model for both the renderings and the unit masks