Spot2 SaaS – Property Management for Real Estate Developers

From my position at Spot2, we identified a structural gap in the commercial real estate ecosystem: large real estate developers do not have a modern tool to manage, publish, or share their space inventory in a standardized way.

 

Today, even companies like Fibra Uno, Parks, or GICSA manage their availability in Excel or PDFs, which is not only inefficient but also limits the speed of commercialization, asset visibility, and data utilization.

 

This was the opportunity to build a SaaS product from scratch, with the objective of:

  • Resolving this critical need for developers
  • Nurturing Spot2 with updated, transactional, and premium inventory
  • Turning Spot2 into the most reliable and complete data provider in the commercial market

Product Thesis

Spot2 remains a marketplace, but by building infrastructure for the professional supply side (developers):

  • We digitize and organize the most valuable supply in the market (Class A)
  • We access real-time data: availability, vacancies, contracts, prices
  • We allow Spot2 to be a stronger bridge to large brands, with verified, organized, and high-ticket supply

Projects Objetives

Strategic Objectives
  • Build the first verticalized SaaS in Mexico for the management of multi-asset real estate portfolios
  • Increase the adoption and retention of developer users with a modular and customizable platform
  • Automate the connection between supply (SaaS) and demand (Spot2 Marketplace) without human intervention
Technical and Design Objectives
  • Design a modular, scalable, and multi-tenant architecture platform from the beginning
  • Allow each organization to configure users, permissions, assets, and processes without technical dependency
  • Design the entire interface: architecture, flows, layout, components, interactions, and visual style

Succes Metrics of the SaaS (North Starts +KPls)

North Star Metric
Coverage rate of available assets connected to Spot2 via SaaS (measures how much of the relevant market inventory we have digitized in real-time)
Key metrics by stage:
Adoption:
  • Average implementation time per organization < 5 days
  • % of spaces loaded in the first week > 80%
Engagement:
  • Weekly active users (WAU) > 60% per organization
  • Modules used per session > 4 of 7 (Dashboard, Assets, Funnel, Prospects…)
Retention:
  • Monthly churn rate < 5%
  • Monthly NPS of administrator users > 8.5
Impact on Marketplace:
  • % of listings on Spot2 connected to SaaS > 40% (goal in 6 months)
  • Match rate with large brands in SaaS spaces x2 vs traditional spaces

Research & Insights

Methodology led by me
  • Interviews with 12 developers with portfolios of more than 10 assets
  • Mapping of current processes: how they publish spaces, how they track prospects, how they manage contracts
  • Concept validation with wireframes in Figma + co-design workshops
  • Benchmark with VTS, Juniper Square, and internal tools of global brokers
Key Findings
  1. There is no tool with access control, hierarchical visibility, or real-time updating.
  2. Developer sales agents lose visibility of the sales funnel once there are 3+ assets.
  3. Many “off-market” spaces never reach the market because there is no central place to share them.
  4. Marketing and sales areas are not coordinated; they use different, incompatible tools.
  5. Everyone wants data, but they don’t know how to generate it without losing control of their information.

Product Desing (UX / UI)

Information Architecture
  • Multi-tenant: each organization manages its assets, users, and processes in isolation
  • Configurable roles and permissions (admin, asset manager, marketing, support)
  • Hierarchical view by complex > asset > space
Key Modules Designed by Me
  • Dashboard (alerts, KPIs, due dates)
  • My Organization (members, roles)
  • Asset Manager (interactive stacking plan, geolocation, documents)
  • Current Tenants (table and file with active contracts)
  • Prospects (enriched database + advanced filters)
  • Projects (Kanban) (CRM-type pipeline with stages and comments)
  • Marketing Tools (landing page creator, forms, chatbot integrated with Vambe)
  • Support Center (ticketing + AI bot for incidents)

Frontend Developement

Technical Stack chosen and executed by me

  • Next.js App Router + Supabase for auth, roles, and data writing
  • Tailwind CSS + shadcn/ui for atomic design and reusable components
  • Modular, scalable architecture per client
  • Use of custom hooks, contexts, and persistence per organization
  • Feature flags to enable modules progressively

Technical Difficulties Solved

  • Granular access control by organization and role
  • Persistence of filters, navigation, and stacking plan in real-time
  • Generation of no-code forms and landing pages for marketing teams

Personal Role

  • I proposed, designed, and am actively building this product
  • I lead UX decisions, visual design, technical structure, and modular experience
  • I participate in validation with clients, assembling pitches, and connecting with commercial strategy

"Shoot for the stars, and you might just land on the moon"

xMcplay - Copyright © 2025 derechos reservados