A replacement for the embedded third-party map on a client listing — built for how senior
living actually sells, and for the people who actually use it. Four working demos below.
Everything runs on real geometry and a real rent roll.
Available Coming available Waitlist Respite On hold Model suite Occupied
Seven states, not two. A multifamily tool carries vacant and leased because an apartment is
either rentable or it is not — collapsing senior living to that is why families ring up to ask
a question the website should have answered. Each state is a pattern as well as a colour.
Four demos · each opens right here
Verification
62Sync logic assertions
29Map browser checks
35Operator browser checks
30Embed isolation checks
Honest state of play
What is not built yet
Everything above is real and runs. The client side is done; the server side of making this a
standalone platform is not. In the order I would do it:
The public API.blocking
These demos read the map from a static file. The contract is fixed and exercised by the
test suite's mock server, but nothing real serves it yet.
Domain allowlisting.blocking
Without it, anyone can embed a map and any site can generate leads against one. The
refusal path and its wording already exist on the client side.
Platform tenancy. Its own accounts, communities and maps, replacing the coupling to
the Seniors Places listing database.
Lead forwarding. Capture, then deliver on to Seniors Places, an operator's CRM
webhook, or email.
Floorplanner import. You already produce the 3D renderings there, so the geometry
for real communities already exists — importing it removes tracing entirely for those.
Scheduled PMS sync. The adapter and reconciliation are built and tested; the nightly
job and its alarm are not. The alarm matters more than the job: a feed that stops
returning rows looks exactly like success while the map freezes on stale data.