
Once or twice a year, a developer client slides a competitor's website across the table. There's a building on it, clickable, units lighting up, prices appearing. "We want this. Can you build it?" And the honest answer, which took me far too many projects to start giving, is that I can, and they shouldn't let me.
The clickable building itself — the SVG map with hover states — is the fun weekend part. Any competent front-end developer can produce it, which is exactly why agencies keep saying yes.
What the quote quietly balloons around is everything behind the picture. You need an admin dashboard so the marketing coordinator can change a price at 9 p.m. before a launch without calling me. Availability states have to sync somewhere instead of living in hardcoded JSON. There are user permissions to sort out, because the intern shouldn't have the same access as the VP. Mobile behaviour is its own small nightmare for dense floor diagrams. And then someone has to maintain all of it, indefinitely, because buildings keep leasing long after the invoices get paid.
Skip any of those and you get the standard failure: a gorgeous custom visualization that's accurate on launch day and fiction by Thanksgiving. I've built two of these. Both are dead now — not broken exactly, just abandoned, still confidently displaying the availability of March.
Somewhere in there I realized multifamily unit visualization software had become a real category, and that it exists precisely because the problem is identical for every building. The visualization, the dashboard, the sync, the permissions, the mobile handling — someone has already packaged all of it behind an embed code.
So these days when a client asks, I reach for something like Planpoint's viewer instead. On WordPress it's a Custom HTML block, nothing more. The client's team manages units, pricing and availability from a dashboard they actually understand, and my agency stops being the bottleneck between a leased unit and an updated website. There are other platforms in the category too, and I'd point you at any of them before a custom build.
In fairness to my past self, there are exceptions. If you're marketing a flagship tower with a seven-figure budget and a retainer that covers ongoing development, a bespoke experience can earn its keep. Same goes for a one-off physical installation with unusual requirements. That's maybe one project in fifty.
For the other forty-nine, the awkward truth of my trade is that the best thing I can hand you is sometimes an embed. That admission gets a little easier every year, mostly because the client's availability data is still accurate in November.