Property Tour
An embeddable property presentation workflow that turns parcel data, overlays, media, and 3D map context into a shareable buyer-facing tour.
Property Tour is a Land id product for turning a property into a guided, buyer-facing presentation. It combines map context, parcel boundaries, data overlays, media, and the property story into an experience agents can share, text, email, or embed.
As web lead, I was involved from planning and architecture through implementation, launch support, and cleanup. The work sat at the intersection of product UX, frontend architecture, cross-team coordination, and a public web surface that had to be credible on its own.
What it does
- Creates a tap-through property story from parcel boundaries, acreage, map layers, media, and surrounding context.
- Gives agents a single shareable link that works across mobile and browser contexts.
- Supports embedding tours and maps on websites or listing pages with iframe URLs and embed code.
- Keeps the presentation live, so updates can flow through the same shared or embedded experience.
My role
- Led the web side from early planning and technical architecture through implementation.
- Helped carry the feature through launch and the current cleanup phase, tightening integration details and quality after real usage.
Why it mattered
This was less about building another page and more about changing how a dense mapping product meets buyers. The project had to make property data feel narrative and usable without flattening the map, overlays, and media that make Land id valuable.
Challenges
- Designing a tour experience that could package dense land data into a guided presentation without making users learn a mapping tool first.
- Supporting share, mobile, and embed contexts with responsive behavior and a reliable viewer experience.
- Keeping the implementation flexible enough for launch needs while leaving room for cleanup and iteration after release.
What I Learned
- Mapping products need opinionated storytelling flows when the audience is a buyer, not a power user.
- Embeds are product surfaces, not just distribution mechanics; they need predictable sizing, loading, and context around them.
- The highest leverage frontend work often happens across planning, architecture, implementation, and post-launch refinement instead of one isolated feature pass.