Custom real estate CRM for site visits, unit inventory, and broker lead ownership

Project overview

The client — a growing real estate firm we refer to here under NDA — develops and sells residential projects across Surat and nearby corridors. Their go-to-market mixes direct sales teams, registered channel partners and brokers, digital campaigns, property portals, and walk-in experience centers. Each project carries its own inventory of units with typologies, facing preferences, parking slots, and status transitions from Available through Hold, Booked, and Registered. Speed matters: when inventory is wrong on the sales floor, trust erodes fast; when two brokers claim the same buyer, commissions and morale suffer.

Before Web6, coordinators tracked leads in Excel workbooks per project, supplemented by broker email dumps and screenshots of portal leads. Site visits were scheduled by phone and noted in personal calendars — double bookings happened weekly during launch weekends. WhatsApp groups broadcast “hot leads” without structured ownership, and duplicate entries for the same phone number were discovered only at booking time when finance raised flags. Generic CRM demos looked fine for B2B SaaS but could not express unit-level inventory holds tied to visit outcomes or broker attribution windows without expensive customization.

Web6 engaged for fourteen weeks to build a bespoke property CRM. Laravel powers the REST API and business rules; React delivers the coordinator and sales executive UI used daily on desktops and tablets; a lightweight Next.js admin shell optional for leadership analytics was included for cross-project dashboards and export controls. PostgreSQL stores buyers, leads, projects, towers, units, visits, broker registrations, and WhatsApp metadata. Redis queues notifications, duplicate scans, and PDF brochure generation. Infrastructure runs Docker on AWS ap-south-1 with Cloudflare in front — the same pattern Web6 uses for other Gujarat builder clients who want data under their control.

Four Web6 engineers — backend, frontend, full-stack for Next.js reporting, and QA/DevOps shared — partnered with client sales leadership, two project coordinators, and IT. Success was measured by fewer duplicate records, same-day unit status accuracy on site, and full coordinator adoption — not invented conversion rate lifts or revenue multiples leadership rightly distrusted from vendor slide decks.

Multi-project rollout timing mattered: two experience centers and three active launches overlapped during build. We sequenced inventory module before broker attribution because coordinators said stale unit status caused more floor arguments than commission disputes — a prioritization call that shaped sprint order and earned trust when launch weekend arrived on schedule.

Engagements like this are delivered through Web6 real estate CRM development .

Business and operational challenges

Lead ownership was contested. Direct sales, broker channel partners, and digital inbound each had legitimate claim rules depending on who touched the buyer first, whether the buyer walked into which experience center, and whether a broker registration form was on file. Without a system enforcing attribution windows and audit trails, disputes consumed sales director time every month — and sometimes delayed bookings while arguments continued in WhatsApp groups.

Duplicate leads were structural, not accidental. The same buyer enquired on a property portal, clicked a Facebook lead ad, and visited site with a broker — three rows in three spreadsheets with slightly different name spellings. Coordinators lacked merge tools; executives called the buyer twice in one afternoon. Finance only saw the problem when token amounts linked to conflicting lead IDs.

Unit inventory status was stale. Holds were verbal during busy Sundays; by Monday morning a “available” three BHK on the ground floor might already be verbally committed. Spreadsheet inventory updated end-of-day if at all. Site sales needed live status on a tablet without opening five tabs or shouting across the experience center.

Site visit scheduling was chaotic. Buyers wanted evening and weekend slots; executives overcommitted; brokers sent clients without notifying coordinators. No single calendar showed executive load, project capacity for simultaneous visits, or broker-attributed appointments. Cancellations and no-shows were invisible in reporting.

WhatsApp dominated enquiry capture. Buyers sent location pins, voice notes, and brochure requests on personal sales WhatsApp numbers. None of that was searchable at firm level — when an executive left, their phone history walked out the door. Leadership wanted WhatsApp logging that respected buyer experience and Meta policy, not a blast of automated bot spam.

• ✓ Broker vs direct lead ownership disputes without audit trails
• ✓ Duplicate buyer records across portals, ads, and walk-ins
• ✓ Unit inventory holds not reflected until end-of-day spreadsheets
• ✓ Double-booked site visits during launch weekends
• ✓ WhatsApp enquiries trapped on personal phones
• ✓ Generic CRMs weak on project-unit inventory modeling

Goals and success criteria

Product goals centered on one CRM where every buyer enquiry becomes a lead with clear owner, project interest, source, and broker attribution when applicable. Coordinators schedule site visits against executive calendars with conflict detection and SMS or WhatsApp reminders using approved templates. Unit inventory updates propagate to sales floor views within minutes when holds or bookings change.

Duplicate prevention goals combined proactive detection — same phone on same project within attribution window — with merge workflows coordinators could execute without IT tickets. Lost merges should preserve broker attribution history and visit logs from both records.

Broker portal goals were pragmatic: registered partners submit leads via a simple authenticated form or email ingestion; rules assign default ownership and notify the mapped direct sales counterpart for joint visits when configured. We did not build a full partner extranet in phase one; we built attribution integrity.

Reporting goals for leadership used the optional Next.js admin layer: cross-project funnel counts, visit-to-booking directional ratios, broker contribution summaries, and duplicate merge statistics — honest ops metrics, not promised revenue uplift.

Success criteria from discovery: reduce duplicate lead creates by at least seventy percent within sixty days; unit status on sales tablets matches coordinator master by end of each business day; one hundred percent coordinator weekly active usage; median site visit scheduling time under three minutes per booking during UAT scenarios.

Discovery and research

Discovery spanned three days at two experience centers and the firm’s head office in Surat. We observed coordinators processing portal CSV dumps, executives conducting site visits with printed inventory sheets, and a broker dispute meeting that lasted forty minutes — excellent evidence for attribution rules priority. We collected anonymized Excel samples, portal export formats, and broker registration PDFs.

Sales director interviews clarified non-negotiables: never show one unit as available to two executives simultaneously on screen; never delete broker history on merge; never send WhatsApp marketing without opt-in. IT documented email relay, domain SSO preferences, and AWS account boundaries — they wanted Laravel and PostgreSQL skills available locally for maintenance, not a black-box SaaS.

We reviewed off-the-shelf property CRMs. Many assumed a single sales hierarchy or US-style MLS semantics. Unit inventory with hold timers, broker windows, and Gujarati buyer name variants in duplicate detection needed custom logic. Week-one spikes validated PostgreSQL unique partial indexes on normalized phone plus project, calendar conflict queries under load, and WhatsApp webhook mapping to buyer records.

Optional Next.js admin was scoped for leadership only — read-heavy dashboards and CSV exports — keeping daily transactional UX in the React app coordinators already learned during training. This separation reduced permission complexity in the main SPA.

System architecture

The property CRM uses a Laravel 11 API monolith with a React 18 SPA for coordinators and sales executives, plus an optional Next.js 14 admin app for leadership analytics — both front ends consume the same versioned REST API and Sanctum cookie auth with role separation. PostgreSQL models projects, towers, floors, units with status enums, buyers, leads with source and broker attribution, site visits, activities, and WhatsApp message references. Redis handles Laravel queues for duplicate scans after lead create, visit reminder sends, and inventory change broadcast events.

Lead creation runs through a normalization pipeline: phone to E.164 India defaults, name trim and fuzzy match against recent leads, project interest linkage, source attribution from portal codes or UTM fields on website forms. Duplicate candidates surface inline before save when confidence exceeds threshold; coordinators can proceed with override reason when genuine family duplicates exist.

Broker attribution rules live in configurable policy rows: window days from first broker registration, walk-in direct override flags, and joint credit splits for reporting only — not payroll, which finance keeps external. Every ownership change appends audit rows with actor and reason.

Unit inventory uses optimistic locking on status transitions. Hold creation specifies expiry datetime; expired holds release via scheduled jobs unless extended by authorized roles. Sales floor React views subscribe to polling every sixty seconds on launch days — WebSockets documented as phase two — and show color-coded unit grids per tower.

Site visit scheduling stores executive assignments, project location, buyer and broker attendees, vehicle and access notes, and conflict checks against existing visits and blocked personal leave imported from CSV. Reminders queue twenty-four and two hours before via WhatsApp templates where session windows allow, SMS fallback otherwise.

WhatsApp Business API webhooks ingest inbound messages; phone match links to buyer profile and open lead. Outbound template messages limited to visit confirmations and coordinator-initiated follow-ups — no cold promotional blasts in phase one.

Docker images deploy to AWS ECS with RDS PostgreSQL, ElastiCache Redis, S3 for brochures and visit QR sheets. Cloudflare WAF protects public website form endpoints that POST new leads into the API. CI runs Pest tests, React Testing Library smoke tests on critical forms, and Lighthouse checks on Next.js admin pages.

• ✓ Laravel REST API — leads, units, visits, broker rules
• ✓ React SPA — coordinator and executive daily workflows
• ✓ Next.js admin — optional leadership dashboards and exports
• ✓ PostgreSQL — unit inventory with hold expiry and audit
• ✓ Redis — duplicate scans, reminders, notification queues
• ✓ AWS + Docker + Cloudflare — production deployment pattern

User experience for sales and coordinators

Coordinators live in the lead queue and visit calendar. Lead queue supports filters by project, source, owner, duplicate flag, and overdue follow-up. Inline duplicate warnings show side-by-side field comparison before merge. Visit calendar offers day and week views with executive columns, drag reschedule with conflict toasts, and print-friendly run sheets for security gates.

Sales executives use a tablet-optimized project view: unit grid with typology filters, tap to hold with timer picker, link hold to active lead, and log visit outcomes — interested, revisit, not interested — that drive pipeline stages. Broker-attributed leads show partner name and registration ID prominently to reduce floor disputes.

Buyers never log into the CRM; public touchpoints stay minimal. Website enquiry forms on the client’s marketing site post to the API with honeypot and rate limits. Brochure download triggers lead create with source tag — coordinated with custom website development already maintained by Web6 for the firm’s project landing pages.

Next.js admin for leadership is read-mostly: cross-project charts, broker tables, visit counts, duplicate merge stats, and CSV exports with watermarking. Access limited to half a dozen users; no reason to burden executives with analytics chrome in their daily SPA.

Delivery process

Weeks 1–2: discovery, data model, project-unit import, auth roles. Weeks 3–5: lead intake, duplicate engine, broker attribution. Weeks 6–8: unit inventory UI, holds, visit scheduling. Weeks 9–10: WhatsApp logging, reminders, Next.js admin dashboards. Weeks 11–12: UAT at one launch project, training. Weeks 13–14: second project rollout, hypercare.

Fortnightly demos with sales director and coordinators. Pilot at the firm’s highest-traffic experience center during a weekend launch; hypercare staff on-call via Slack channel shared with IT. Excel retirement ceremony was informal but effective — director disabled old shared links in front of the team.

Portal CSV import mappers saved coordinator hours each Monday — previously manual copy-paste from three portal formats. Training included a launch Sunday simulation: import fifty leads, merge twelve duplicates, book twenty visits, place eight holds — timed exercise; coordinators who finished under ninety minutes certified for production credentials. Sales executives joined a shorter tablet-only module focused on unit grid and hold timers.

SEO and discoverability

CRM delivery was internal; marketing SEO focused on project landing pages that feed the CRM — a coordination point Web6 handled alongside custom website development already in flight. Enquiry forms on those pages POST to the CRM API with hidden UTM fields so digital leads arrive with attribution intact. Page titles and meta descriptions follow project-location intent (“2 BHK in Vesu Surat”) rather than generic builder branding alone — practical lead capture SEO, not vanity traffic.

Structured data on public project pages uses RealEstateListing-oriented JSON-LD where content genuinely supports it — price range, address, number of bedrooms — without fake aggregate ratings. Canonical tags point to primary domains; staging CRM and admin hosts sit behind noindex and robots disallow.

This case study page on web6.in uses BreadcrumbList and Organization schema in the site template so the story is internally findable and correctly categorized as a Web6 case study — lightweight schema for the case study document itself, not keyword stuffing in the CRM app.

Internal search in the CRM indexes buyer phone tails, lead IDs, broker names, and unit numbers so coordinators find records faster than site: search — a form of operational discoverability marketing sites cannot replace.

Performance and reliability

Unit grid queries paginate by tower and typology; indexed status columns keep tablet views under two second load on 4G during UAT. Hold expiry jobs batch every five minutes — sufficient precision without overloading RDS on Sunday peaks.

Duplicate scan jobs run asynchronously on lead create so coordinators are not blocked on fuzzy match computation. Redis-backed rate limits protect public enquiry endpoints from portal scraper spikes.

Next.js admin dashboards cache aggregate queries five minutes — leadership accepts slight lag for stable page loads. Cloudflare caches static assets for both SPAs; API routes uncached with appropriate headers.

Visit reminder jobs batch SMS fallback when WhatsApp session windows expired — common for buyers who enquired Friday and visit Sunday. Coordinator dashboard shows delivery status per reminder so they know when to phone manually; reducing no-shows was operational goal, not a revenue claim, but visit completion rate improved directionally in director's weekly notes.

Security and compliance

Buyer PII — phone, email, government ID references collected at booking — requires role-scoped access and encrypted backups. Broker desk users see only their attributed leads, not firm-wide buyer lists. Audit logs capture unit status changes and ownership overrides for commission dispute review.

Public form endpoints use honeypots, Cloudflare rate limits, and Laravel throttle middleware. WhatsApp webhook signatures verified before processing. S3 brochures served via short-lived presigned URLs.

MFA required for admin and director roles; session timeout aligned with shared tablet usage policies on sales floor devices — coordinators re-auth before sensitive exports.

• ✓ Territory and project-scoped authorization policies
• ✓ MFA for leadership and admin roles
• ✓ WhatsApp webhook verification and template-only outbound where required
• ✓ Rate-limited public lead capture endpoints
• ✓ Audit trails for ownership and unit status changes
• ✓ Encrypted RDS backups and S3 at rest

Testing and quality assurance

Automated tests cover duplicate detection edge cases — same phone different project allowed, same phone same project blocked, merge preserves broker fields — visit conflict rules, hold expiry transitions, and attribution window boundaries at midnight IST.

UAT scripts enacted coordinator day-in-life: portal import, duplicate merge, visit book, WhatsApp log, hold with expiry, booking lock. Sales director sign-off on broker dispute simulation using audit export alone.

Tablet testing on Android devices used on the actual sales floor; print layouts verified for gate passes at experience center printers.

Measured outcomes

Duplicate lead record creation — counting new leads flagged and merged or prevented at entry — fell eighty-two percent in the first sixty days compared to the prior sixty-day baseline from portal and ad imports. Coordinators reported the inline warning at create time mattered more than batch cleanup jobs after the fact.

Unit availability on sales tablets matched coordinator master status by end of each business day throughout hypercare — verified by daily spot checks during a launch weekend. Verbal-only holds decreased because executives could place timed holds in-system from the floor; stale “available” labels were the complaint leadership wanted gone, and same-day sync achieved that operational bar.

Sales coordinator weekly active usage reached one hundred percent within four weeks of training — every coordinator logged in and processed at least one lead, visit, or merge weekly. Executives adopted unit grid holds more slowly but reached steady use by week six when director made holds mandatory before verbal promises.

We did not publish revenue or conversion rate percentages. Directional improvements leadership cited included fewer commission disputes requiring director arbitration, faster visit scheduling during peak hours, and searchable WhatsApp history when executives rotated between projects — ops outcomes tied to the metrics above.

Lessons learned

Real estate CRM success is inventory and attribution first, pipeline aesthetics second. Unit holds with expiry and broker audit trails solved more floor pain than fancy funnel charts on day one.

Duplicate prevention at create beats monthly cleanup — coordinators have no time for forensic merges during launch Sundays.

Optional Next.js admin separated leadership analytics from daily SPA complexity — worth the small extra surface area for read-only reporting.

WhatsApp logging must respect buyer trust — templates for confirmations, not promotional spam — or coordinators disable the integration.

Pilot one busy experience center; stress-test visit calendar before rolling to quieter projects.

“We stopped fighting over who owned which buyer and which unit was actually free. Coordinators schedule visits in one calendar, brokers see attribution on screen, and WhatsApp is not lost when an executive changes projects. It is not magic — it is finally one system.”

Suggested project visuals

• Sales floor tablet view with color-coded unit status and timed holds replaces end-of-day spreadsheet updates.

  File: real-estate-crm-unit-inventory-grid.webp

  ALT: Real estate CRM unit grid showing availability and hold status by tower

• Coordinators book visits with conflict checks and broker attendee fields — no double-booked launch weekends.

  File: real-estate-crm-site-visit-calendar.webp

  ALT: Site visit scheduling calendar with executive columns and conflict detection

• Inline duplicate detection and merge workflows reduce portal and ad import clutter before booking.

  File: real-estate-crm-duplicate-lead-merge.webp

  ALT: Duplicate lead merge screen preserving broker attribution history

• WhatsApp Business API messages log to buyer profiles so history survives executive project rotations.

  File: real-estate-crm-whatsapp-buyer-timeline.webp

  ALT: Buyer CRM timeline with WhatsApp enquiry messages and visit events