Here's a pattern I've watched repeat across project launches. A team signs up for visualization software expecting the technology to be the hard part, and the technology turns out to take an afternoon.
What eats the following three weeks is everything the team was supposed to bring to it. The software vendors rarely warn you, because "you have homework" is a terrible sales pitch. So consider this the warning.
If an interactive stacking plan is going on your project website this quarter, four things need to exist before the kickoff call, and none of them are technical.
A drawing of the building someone can point at
The plan needs a base image: an elevation, a section, or a simple rendering showing the building face with floors distinguishable. Most teams have this buried in the architect's package, but "buried in the architect's package" is not the same as "exported at usable resolution with rights cleared to publish."
Chase this first, because architects answer email on a geological timescale, and every other step can proceed while you wait. If the project has multiple phases or wings, decide now which appear, since adding a wing later is a redesign, not an edit.
Unit data that survives contact with a spreadsheet
Every unit needs a number, a floor, a type, a size, a price and a status, in one file, agreed upon. Simple in theory. In practice this is where launches stall, because the sales director's list disagrees with the architect's numbering, which disagrees with the pro forma, and unit 407 is somehow two different apartments depending on who you ask.
Reconcile it once, brutally, before anything gets imported. A stacking plan built on ambiguous data ships those ambiguities straight to the public.
A pricing sign-off that took actual minutes
Static marketing lets pricing stay vague; an interactive stacking plan puts a number on every block. That precision is the whole appeal, and it forces a conversation some organizations have been avoiding: are these prices approved for publication, all of them, today?
Get the sign-off in writing from whoever owns revenue. The alternative is launching with placeholder prices and a promise to update, which every team makes and roughly none keeps.
One name in the "who updates this" box
Not a department. A name. The plan is only as good as its freshness, and freshness dies of diffusion of responsibility faster than anything else. The person doesn't need technical skills, since maintaining these platforms is dashboard work, but they need to know that when a unit sells on Friday afternoon, flipping its status is their job before the weekend traffic arrives.
Do the homework in this order and the launch itself is genuinely boring, in the good way. Skip it and you'll discover, publicly, that the hard part was never the software. It was agreeing on unit 407.
