Product build · Real estate

Building a Real Estate CRM around the site visit

Property sales has a shape that generic CRMs handle badly. This write-up covers the decisions behind our Real Estate CRM: distribution, the site visit as the central event, and mobile-first design for people who are rarely at a desk.

  • Product
  • Lead distribution
  • Site visits

In this case study

  1. Business context
  2. The problem
  3. The existing process
  4. The challenge
  5. The solution
  6. Technology
  7. Implementation
  8. Workflow
  9. Outcome

TypeOur own product

FocusLead distribution, site visits, pipeline

Primary usersDevelopers, brokers, channel partners

DevicesMobile-first, with a desktop manager view

Business context

Property sales teams work under unusual pressure. Enquiry cost is high, volume spikes around launches, buyers compare several projects at once, and the decisive event — the site visit — happens away from any desk.

The teams we spoke to used a mix of portal dashboards, spreadsheets and WhatsApp, and every one of them described the same thing: leads went missing between the moment of enquiry and the first proper conversation.

The problem

Leads arrive from portals, Meta and Google campaigns, project websites, hoardings, walk-ins and channel partners. Each source has its own inbox, so there is no single queue and no reliable answer to how many enquiries arrived yesterday.

Distribution is informal. Someone forwards leads by WhatsApp to whoever seems available. The result is duplicated calls to the same buyer, or none at all because each agent assumed another had it.

  • No single queue across lead sources
  • Informal, unauditable assignment
  • Site visits recorded in notebooks, if at all
  • No reliable view of which sources produce visits and bookings

The existing process

A typical team collects portal leads by email alert, pastes them into a spreadsheet and messages them to agents. Agents call from personal phones, keep their own notes and report progress verbally. Site visits are arranged by phone call and remembered.

Marketing has little feedback. Budget decisions are made from enquiry counts, because nothing connects a campaign to a booking.

The challenge

Two design constraints dominated. First, the system had to work for agents who spend the day in cars and at sites: fast on a phone, tolerant of weak signal, and quick enough to update between meetings.

Second, it had to hold up during launches. Distribution logic that works for twenty leads a day must still produce fair, auditable assignment at two hundred.

The solution

Every lead enters one queue with its source attached and is checked against existing records by phone number. Distribution is rule-based: round robin, project-wise, team-wise, or by language or availability, with caps and automatic reassignment if a lead is not actioned in time.

The site visit is treated as the central event. It is scheduled from the lead, confirmed and reminded on WhatsApp, checked in on the day, and followed by structured feedback that sets the next action.

For management, the pipeline appears as a kanban board with configurable stages, backed by reports on source performance, response time, visit-to-booking ratio and agent activity.

  • Deduplicated single lead queue
  • Round robin, project and team distribution with caps
  • Site visit scheduling, reminders and feedback capture
  • Kanban pipeline with configurable stages
  • Attendance and activity tracking
  • Limited-access logins for channel partners

Technology

The system is a web application with a mobile-first interface, structured around a relational database and a queue for messaging and reminders.

  • PHP backend with a MySQL database
  • Bootstrap and Tailwind for a responsive interface
  • WhatsApp Business API for confirmations and reminders
  • Role-based access control with audit logging
  • Import tools for portal exports and legacy spreadsheets

Implementation

We began with capture and distribution, because they solved the most visible pain and produced the data everything else depended on. The site visit workflow followed, then the pipeline board, then reporting once there was enough reliable data to report on.

Onboarding a real estate team means importing existing leads, configuring projects and distribution rules, connecting lead sources and WhatsApp, and training agents on a small number of daily screens.

Workflow

A lead arrives and is assigned in seconds; the buyer receives an immediate WhatsApp acknowledgement; the agent makes a qualification call and records requirement and budget; a site visit is booked and reminded; feedback is captured on the day; and negotiation and booking are tracked to completion.

Outcome

The structural change is that every lead has an owner and a next action, every site visit is recorded, and management can see source performance rather than guessing. Response discipline becomes something the system enforces rather than something managers chase.

We do not quote booking or conversion improvements here. Outcomes depend heavily on project, market and team, and we prefer to describe the mechanics accurately.

Related

Services and products involved

CRM for developers, brokers and channel partners

Real Estate CRM

Property sales CRM with lead distribution, site visit tracking, kanban pipeline, attendance, role-based access and WhatsApp integration.

  • Lead distribution
  • Site visits
  • Kanban pipeline
  • Attendance

Real Estate

CRM, lead distribution, site visit workflows, WhatsApp automation and project marketing for developers, brokers and channel partners.

  • Lead distribution
  • Site visits
  • WhatsApp
  • Project marketing

CRM Development

Custom CRM systems with lead capture, assignment rules, pipelines, follow-ups, WhatsApp integration and reporting that reflects reality.

  • Lead management
  • Sales pipeline
  • Assignment rules
  • Follow-ups

WhatsApp Automation

WhatsApp Business API workflows: instant replies, notifications, reminders, nurture sequences and conversations logged in your CRM.

  • WhatsApp Business API
  • Notifications
  • Lead nurturing
  • CRM logging

Next step

Have a similar problem to solve?

Every build starts with the same question: where is time and revenue actually leaking? Tell us about your process and we will suggest where to start.

Start Your Project WhatsApp