Turning architectural plans into a 3D model that doubles as a sales tool is a five-stage production process, and for a browser-based interactive platform it runs 3 to 10 weeks from files received to a live link. The inputs are the documents a developer already has: floor plans, elevations, and sections in CAD or PDF, plus any renders, a material schedule, and a BIM file if one exists. Those become a clean 3D model, get optimized to load in a browser, gain interactivity like floor selection and finish swaps, and ship as a shareable link with no app to download. I lead the engineering team at R2U, a Brazilian proptech company with the most Apple Vision Pro real estate deployments globally. Our 3 to 10 week figure is for the interactive 3D Sales Platform. The same source files driving an Apple Vision Pro experience run 4 to 14 weeks. For context, a physical scale model takes 2 to 5 months and costs from $9,000 into the six figures. This guide walks the pipeline stage by stage and explains what actually moves the timeline.
What “Architectural Plans to 3D Model” Means for Sales
Converting architectural plans to a 3D model means rebuilding a development from its design documents as accurate 3D geometry, then turning that geometry into something a buyer can explore and a sales team can share. The plans define the shape. The sales tool adds the experience. This guide covers the production process. For what the finished tool actually does for a sales team, see our guide to the 3D sales platform. This is different from a 3D tour of a finished home captured with a laser scanner, because nothing has been built yet, so the model is authored from drawings rather than scanned from reality.
The starting point is the document set every developer already produces during design. Floor plans give the layout and unit boundaries, elevations and sections give heights and facade detail, and a material schedule lists the finishes a buyer will later swap. Renders, when they exist, lock the intended look so the model matches the marketing. The format matters too: CAD files carry precise 2D dimensions but no volume, while a BIM file, short for Building Information Modeling, already holds 3D geometry. Most pre-construction projects we receive in the US arrive as CAD plus PDF renders.
The result of this work is not a sales tool yet. It is a faithful digital copy of the building, and the R2U 3D Sales Platform is built on top of it. Every later stage inherits its accuracy, so a wall in the wrong place here becomes a wrong floor plan in the live tool.
Stage 1: Files In, Reference Locked
The first stage collects the source files and locks the references, and it sets the schedule for everything after it. The deliverable is a confirmed input package: drawings, renders, material schedule, and any BIM file, with open questions answered before modeling starts.
Speed here depends almost entirely on the developer. A complete, current set of plans with a clear material schedule lets modeling begin immediately. A set missing the latest revision, or with finishes still undecided, stalls before any 3D work happens. The most common delay we see is not technical. It is waiting on the final plan revision or a material list that keeps changing.
R2U runs a short kickoff to lock these inputs, because this stage protects the timeline. We confirm which units are in scope, which finishes buyers can swap, and what the view looks like from each floor level, since real view by floor has to be planned, not added later. Locking scope early is what keeps a 200-unit launch on the 3 to 10 week track instead of drifting.
Stage 2: Modeling the Building From the Plans
Modeling is where drawings become 3D geometry, and it is the longest single stage for a complex development. The deliverable is a complete, watertight model of the building and its units, accurate to the plans and matched to the reference renders. For a BIM file, this stage starts from existing geometry and focuses on cleanup. For CAD and PDF, it builds the volume from scratch.
The modeler reconstructs the structure in order: shell and slabs first, then interior walls and unit divisions, then window and door openings, then the finishes that make a unit read as a real apartment. Accuracy is the whole point. The dimensions come straight from the plans, so a buyer comparing two units in the live tool sees the true difference in size and layout.
A BIM file speeds this up but rarely skips it. BIM models carry structural and mechanical detail that no buyer needs to see, like ductwork and rebar. That geometry gets stripped to what matters for sales and rebuilt where the source is too heavy or messy to render. The IFC format, the open BIM standard published as ISO 16739-1:2024 by buildingSMART, makes it possible to read a BIM file regardless of which software the architect used. That is why a vendor-neutral pipeline can ingest models from Revit, ArchiCAD, or anything else.
This is the stage where R2U’s universal platform features get built into the geometry: unit selection and comparison, real view by floor, and the rooms that buyers will later customize. The same model serves the browser platform and, for projects that go further, the Apple Vision Pro experience, which is why the source has to be authored once and authored well.
Stage 3: Optimization for the Browser
Optimization is the stage that makes a heavy 3D model load in a web browser on a phone, and it is the step most teams underestimate. The deliverable is a compressed, web-ready model that opens in seconds over a normal connection, with no app and no download. A raw architectural model is far too large to stream to a buyer’s phone, and optimization is what closes that gap.
Two technical pieces do most of the work. The model is exported to glTF, the royalty-free 3D format from the Khronos Group that the organization calls “the JPEG of 3D” and that became the ISO/IEC 12113:2022 standard for runtime 3D. Then the geometry is compressed with Draco, the open-source mesh compression from Google. Cesium and Khronos document Draco reducing file size by up to 95% on geometry-heavy models with no visible change in quality. Textures get resized, duplicate materials get merged, and parts the buyer never sees get removed.
The reason this matters for sales is distribution. A 3D Sales Platform shared over WhatsApp or email is only useful if it opens fast on the buyer’s phone, on the spot. If the model takes 30 seconds to load or crashes a mobile browser, the buyer closes the tab. Browser-based delivery with no app is one of R2U’s core differentiators, and it only works because optimization gets the model down to a size a phone can handle.
For an Apple Vision Pro build, the optimization target is different. The headset renders at real scale in the room, so the geometry budget and texture detail are tuned for spatial computing rather than a mobile browser. That is part of why the Apple Vision Pro timeline runs longer, at 4 to 14 weeks.
Stage 4: Adding Interactivity and Finishes
Interactivity is the stage that turns a 3D model into a sales tool, and it is what separates this from a static render or a fixed 360 tour. The deliverable is a working experience: a buyer can pick a unit, walk through it, swap finishes, see the real view from that floor, and watch sunlight move across the rooms by time of day.
Finish customization is the feature that does the most selling. The material schedule from Stage 1 becomes a live menu, so a buyer changes floors, countertops, and fixtures in real time and sees the result instantly, on whatever the developer chooses to let them customize. This is the difference between showing a buyer one decorated version and letting them build the version they would actually buy.
Three more features get wired in at this stage, and all four ship in every R2U project regardless of segment. Unit selection and comparison lets a buyer hold two floor plans side by side. Real view by floor shows the actual outlook from a given unit, not a generic render, since a 9th-floor view and a 30th-floor view are different products. Sunlight simulation runs the light across the day so a buyer can see morning versus afternoon in a specific room. None of these can be faked after the fact, which is why the model had to be accurate in Stage 2.
R2U also wires in analytics here, so the developer sees which units buyers explore, which finishes they pick, and where attention concentrates. That behavioral data is something a physical model unit, however expensive, cannot produce.
Stage 5: Hosting, Sharing, and Updates
The final stage puts the tool online, makes it shareable, and keeps it current as the project changes. The deliverable is a live link and, where the project calls for it, a published Apple Vision Pro app. The browser platform needs no installation. The sales team shares a URL by WhatsApp or email, and the buyer keeps exploring from home after the gallery visit.
Hosting is not a one-time handoff. Pre-construction projects change: finishes get added, a unit type gets revised, a phase releases. Because the platform is browser-based, an update goes live for everyone the moment it ships, with no app-store review and nothing for the buyer to reinstall. The link a sales agent sent last month shows this month’s information.
This is where building from plans pulls ahead of a physical model. A physical scale model is fixed the day it is built, and a physical model unit cannot change once it is decorated, no matter what the budget was. The model authored from plans updates with a deploy. The case for it is not only the faster timeline. It is a sales tool that stays accurate for the life of the campaign, on the browser platform and on Apple Vision Pro alike.
What Actually Moves the Timeline
The 3 to 10 week range is real, and where a given project lands inside it comes down to four things, not one. The single biggest factor is the input package. Complete, final plans with a settled material schedule push a project toward the fast end. Missing revisions and undecided finishes push it toward the slow end, or past it.
Scope is the second factor. One tower with a handful of unit types models faster than a multi-phase development with a dozen layouts, an amenity deck, and landscaped grounds. At that size the model often becomes an interactive masterplan covering the whole site. The third is the level of finish customization: swapping two flooring options is quick, while a full menu across every room takes longer to author and test. The fourth is the target platform, since an Apple Vision Pro build runs 4 to 14 weeks against the browser platform’s 3 to 10.
What does not move the timeline much is whether the source is CAD or BIM. A clean BIM file helps in Stage 2, but a messy one can cost as much cleanup as building from plans. Most pre-construction launches we deliver in the US start from CAD drawings and renders anyway. The practical lever a developer controls is the input package. Hand over a complete, current set of files with finishes decided, and the project runs fast. That is the one variable worth managing before the pipeline even starts.
If you have plans for a development in the pipeline, book a demo and we will walk you through what your files can become and how fast.
FAQ
How long does it take to turn architectural plans into an interactive 3D model?
A browser-based interactive 3D Sales Platform takes 3 to 10 weeks from files received to a live link, per R2U’s verified production timeline. The same source files driving an Apple Vision Pro experience run 4 to 14 weeks. A physical scale model, by comparison, takes 2 to 5 months. Where a project lands in the range depends mostly on whether the plans and material schedule are final.
Do you need a BIM file to build a 3D sales tool?
No. A 3D sales tool can be built from standard architectural plans in CAD or PDF format, which is how most pre-construction projects start. A BIM file gives the modeler a head start on geometry, but it is not required, and a messy BIM file can cost as much cleanup as building from plans. R2U builds from whatever the developer has: plans, renders, and a material schedule.
What file formats do you need to start?
The core inputs are floor plans, elevations, and sections in DWG or PDF, plus a material schedule listing the finishes buyers will swap. Renders help lock the intended look, and a BIM file in the open IFC format is useful if it exists. Locking these inputs early is the single biggest thing that keeps the project on the 3 to 10 week timeline.
How is this different from a Matterport 3D tour?
A Matterport-style 3D tour is scanned from a finished space with a laser scanner, so it cannot exist before construction. An interactive 3D model built from architectural plans is authored from drawings, which is why it works for pre-construction. Properties marketed with immersive 3D tours sell 31% faster, per a Matterport study of 143,000 listings (Matterport, 2019), and building from plans extends that advantage to units that are not built yet.
Why does the 3D model need optimization for the browser?
A raw architectural model is far too large to load in a web browser on a phone. Optimization exports the model to glTF, the Khronos web 3D standard, then compresses the geometry with Google’s Draco. That cuts file size by up to 95% on heavy models with no visible quality loss (Cesium, Khronos). It lets a sales agent share a link over WhatsApp and have it open in seconds on a buyer’s phone, with no app.
Can the 3D model be updated after it goes live?
Yes. Because the R2U 3D Sales Platform is browser-based, an update goes live for everyone the moment it ships, with no app-store review and nothing for the buyer to reinstall. When a finish gets added or a unit type is revised mid-campaign, the link a sales agent already sent shows the current information. A physical scale model, by contrast, is fixed the day it is built.
Can the same 3D model run on Apple Vision Pro?
Yes. The model authored from the plans serves both the browser-based 3D Sales Platform and an Apple Vision Pro experience, which renders the development at real scale in the room. The Apple Vision Pro build is optimized differently for spatial computing and runs 4 to 14 weeks against the browser platform’s 3 to 10. R2U has delivered more Apple Vision Pro real estate projects than any company globally.
Written by
Giovanni Abeni
CTO — R2U
Giovanni Abeni has been CTO of R2U since the company's early years. A graduate of Escola Politécnica at USP, he worked at Espresso Labs and Converge before taking technical leadership at R2U. He owns the architecture of the platform that runs interactive models in the browser (WebGL), virtual staging in augmented reality, and spatial computing experiences with Apple Vision Pro. Under his technical leadership, R2U has delivered projects for companies including Mobly (+82% conversion), Tegra, Coelho da Fonseca, and Portobello.
LinkedIn →
