KEY OUTCOME
Lead cold rate: 38% → 7%. Management reporting time: 4 hrs/week → real-time. Lead-to-site-visit conversion: 12% → 21%.
THE PROBLEM
The developer had four active residential projects across Pune — a 2 and 3 BHK high-rise in Wakad, a premium 3 and 4 BHK tower in Baner, a plotted development in Talegaon, and a newly launched affordable project in Undri. The sales team numbered 20 field executives plus two senior closers. In a good month, the company received 500 to 600 leads across all four projects from MagicBricks, 99acres, Facebook ads, walk-ins, and channel partners. The company was spending ₹1.8 lakh per month on marketing. Nobody in the company could say which of that spend was working.
The lead management process had grown organically over six years and had never been formally designed. Leads from MagicBricks arrived as email notifications to a shared Gmail inbox. The sales manager's assistant — a CRM executive in title, though the company had no actual CRM — read the emails and forwarded them to individual reps by WhatsApp message. Leads from the company website arrived through a contact form that sent an email to the same inbox. Walk-in leads were written in a paper register at the site office and later entered into the CRM executive's master Excel sheet. Channel partners submitted leads by calling or WhatsApp-messaging the CP manager, who forwarded them verbally or by text to the appropriate sales rep.
Each sales rep maintained their own lead list. Some used Excel. Some used the Notes app on their phone. Two of the senior reps — both handling premium-project enquiries — kept leads only in their phone contacts, with the buyer's name followed by the project name in brackets: 'Vikram Nair (Baner 4BHK)'. Follow-ups happened from memory. There was no standardised follow-up cadence. A rep with 70 active leads might call the ten most promising ones repeatedly while forty others went weeks without contact. The company had no visibility into which leads were being worked and which were going cold.
The resignation incident in March was the precipitating event that pushed the Sales Head to commission the CRM. When the senior rep gave notice, the Sales Head asked for his lead list. The rep shared a partial Excel file with 40 names. When the Sales Head began making calls to introduce a replacement rep, buyers he had never heard of mentioned previous conversations — about floor plans, price negotiations, a specific unit on the fourteenth floor. None of it was in any company record. The rep's personal phone, which he took with him, contained 180 active leads he had been nurturing. The company's legal position was that those conversations had never happened.
Duplicate leads were a persistent friction point between the sales team and the channel partner network. A buyer might enquire on 99acres on Monday, be assigned to Rep A, and then have their broker submit the same lead to the CP manager on Wednesday. The CP manager, unaware of the existing assignment, would forward it to Rep B. Both reps would call the same buyer. The buyer — already annoyed by receiving six calls from competing developers — now received two calls from the same company within an hour. The CP would claim commission on booking; Rep A would claim the lead was already in the system. Disputes consumed hours of management time monthly.
Site visit double-booking was a variation of the same problem. Without a shared scheduling system, two reps could independently book the same buyer for a site visit on the same day, or book different buyers for the same unit walkthrough slot with the same site sales manager. The Baner site office had four such incidents in Q1 — buyers arriving to find the site manager already occupied with another group, or two sets of prospects encountering each other in the sample flat and comparing notes on the price they had been quoted.
The Sales Head's weekly reporting exercise had become a standing Monday morning ritual that nobody enjoyed. By 9 a.m. he had WhatsApped all twenty reps asking for their pipeline update. By noon he had received twelve replies in varying formats. By 2 p.m. he had collated them into a master sheet. By 4 p.m. he had prepared a slide with four numbers — total leads, site visits done, bookings this month, and leads in negotiation — for the Director's review meeting at 5 p.m. The numbers were, at best, as of the previous Friday. Two of the twenty reps consistently sent their update on Tuesday. The Director had stopped trusting the numbers.
“Our senior-most sales rep resigned in March. He had 180 prospects in his personal phone — buyers he had been nurturing for months. When he left, we had no record of those conversations. I called twenty of them myself. Half had already booked with competitors. Those were ₹30–50 lakh commissions we will never recover.”
BEFORE
38%
Of leads went cold with no follow-up contact — reps managing 60+ prospects from memory across personal phones and individual Excel files
4 hrs
Every week the sales head spent compiling pipeline numbers from 20 individual rep Excel sheets — and the output was still a week stale by the time it was reviewed
180
Active lead records lost when a senior sales rep resigned — all stored in his personal phone, no copy in any company system
0
Visibility into which portal or campaign generated each lead — no source tracking meant no basis for deciding where to spend the ₹1.8L monthly marketing budget
PLATFORM WORKFLOW
Click any module to explore what was built
Leads flow in from MagicBricks, 99acres, Facebook Lead Ads, the company website, manual walk-in entry, and the channel partner portal — all into one unified queue. Every lead is matched against existing records by phone number before entering the system. Duplicates are merged, not created. Assignment from the unassigned queue takes one drag-and-drop.
THE SYSTEM
I built a purpose-built real estate CRM tailored to the company's four-project structure, sales team hierarchy, and the specific failure modes that had accumulated over six years of spreadsheet-based pipeline management. The system replaced the shared Gmail inbox, the individual Excel files, the paper register at the Talegaon site, the WhatsApp assignment chain, and the Monday morning reporting exercise — in one go.
**Multi-source lead capture with deduplication:** MagicBricks and 99acres send lead notification emails — the CRM connects to the shared Gmail inbox and parses these emails automatically, extracting name, phone, email, configuration interest, and the source portal. Facebook Lead Ads are connected via the Meta API — leads from Facebook campaigns flow in within 60 seconds of submission. The website enquiry form posts directly to the CRM API. Walk-in leads are entered through a mobile-optimised manual entry form that the site office receptionist opens on a tablet — no more paper register and no transcription delay. Channel partners submit leads through the partner portal built in the earlier engagement, and those flow directly into the CRM as CP-sourced leads with the partner's name attached. Every incoming lead, regardless of source, is matched against existing records by phone number before it reaches any rep's queue. If the phone number already exists in the system, the new information is merged onto the existing record and a note is added. No duplicate is created. No double assignment.
**Pipeline Kanban with configurable stages:** The pipeline is a Kanban board with six stages configured for the company's actual sales process: New → Contacted → Site Visit Scheduled → Site Visit Done → Negotiation → Booked. A seventh stage, Registered, is used after possession. Each stage has a card count and a value sum — the manager sees at a glance that there are 42 leads in Negotiation across the four projects with a combined potential booking value of ₹19.4 crore. Leads are assigned to reps from the New stage by the sales manager or the CRM executive. Every stage transition is logged with a timestamp and the user who made it. A lead cannot skip from Contacted directly to Negotiation without passing through site visit stages — the pipeline enforces the process, not the manager's memory.
**Follow-up reminder engine:** Every lead in the system has a Next Follow-Up Date field. When a rep logs a call or sends a WhatsApp from the CRM, they set the next follow-up date before closing the interaction. If they do not, the system sets a default of three days. When the next follow-up date passes without any logged activity on the lead, the rep receives a WhatsApp notification. If the lead remains untouched 72 hours after the overdue notification, it escalates to the sales manager. The manager's dashboard shows escalated leads with the rep name, lead name, project, stage, and days since last contact. The manager can reassign, call the rep, or note that the buyer was unreachable. Nothing falls through.
**Site visit scheduling with double-booking prevention:** Reps book site visits from the lead record by selecting a project, a date, and an available time slot. The site visit availability calendar is configured per project — the Wakad high-rise has four slots per day with a maximum of two groups per slot; the Baner tower has three slots. When a rep selects a slot, the system checks availability in real time. If the slot is full, the rep sees the next available option. Once booked, the buyer receives a WhatsApp confirmation and a 24-hour reminder. Post-visit, the rep is prompted to log visit notes — buyer objections, preferred unit, stated timeline. These notes are visible to the sales manager before the next follow-up call, enabling coaching without a meeting.
**Booking form generator and demand letter tracker:** When a lead moves to Booked, the rep selects the unit — tower, floor, flat number, configuration, total consideration — and the system generates a booking form PDF pre-filled with buyer details, unit details, booking amount, and the project's payment schedule. Once confirmed, the payment tracker activates: each instalment milestone from the payment schedule is entered, and the buyer's payment against each milestone is logged as it comes in. When an instalment is due and unpaid, the system generates a demand letter PDF ready to print or email — no CRM executive typing from a template each time.
**Team performance dashboard:** The sales head opens a single dashboard — on mobile or desktop — showing the current pipeline without asking anyone. At the top: total active leads, site visits scheduled this week, bookings this month, and revenue in negotiation. Below: a per-rep leaderboard by leads contacted in the last 7 days, site visits done this month, and booking conversion rate. A source attribution panel shows lead volume by source with site visit conversion rate per source. Portal spend entered monthly is divided by attributed leads to compute cost-per-lead per source. The Director asks for a pipeline update on a Tuesday at 5 p.m. — the Sales Head opens the dashboard on his phone at 4:58 p.m. and has every number in under 30 seconds.
**Lost lead analysis and re-engagement:** Leads marked as Lost require a loss reason from a configured list: budget not aligned, timeline not ready, booked with competitor, no response after five attempts, project not preferred. The loss reason is stored on the lead record. The sales head can filter by loss reason — if 30% of lost leads this month are tagged 'booked with competitor' for the same micro-market project, that is a signal for a pricing or positioning review. Lost leads tagged 'timeline not ready' or 'budget not aligned' are available for re-engagement: when a project reaches possession or announces a revised payment scheme, the marketing team exports those leads and runs a WhatsApp broadcast. Several buyers who had been cold for months re-entered the pipeline and converted.
**Role-based access:** Sales executives see only their own assigned leads. Team leads see their team's leads and performance. The sales head and CRM executive see all four projects. The Director sees the executive dashboard only — pipeline value, bookings, and source ROI — without access to individual lead records. Channel partners log in to their own partner portal and their submitted leads appear in the CRM automatically, tagged with the CP's name. When a booking is confirmed against a CP-sourced lead, the commission entitlement is calculated — visible to the CP on their portal without a phone call to ask about referral status.
Leads flow in automatically from MagicBricks and 99acres email notifications, the company website, Facebook Lead Ads, and manual entry for walk-ins. Every incoming lead is matched against existing records by phone number before assignment — a lead already in the system from the website does not create a duplicate when the same buyer enquires on a portal the following day.
Every lead in the pipeline has a next follow-up date. When that date passes without a logged call or note, the system flags the lead as overdue and sends the rep a WhatsApp reminder. If the lead remains untouched for 72 hours after the overdue flag, it escalates to the sales manager — who sees the lead, the rep, and the number of days since last contact, without asking for a status update.
The sales head opens a live dashboard: pipeline by stage and by project, team leaderboard by leads contacted and site visits done, conversion rate at each stage, and lead volume and quality by source. Portal spend entered monthly is divided by attributed leads to show cost-per-lead and cost-per-site-visit per source — the first time the company could see which ₹ of marketing spend was generating which quality of prospect.
THE OUTCOME
The most immediate visible change was in follow-up discipline. In the first week after the system went live, the sales head received 23 escalation notifications — leads that had gone overdue and past the 72-hour re-notification window without rep action. That number represented the baseline of how many leads were being systematically ignored in the previous system. By week three, the weekly escalation count was down to four. By month two, it was averaging one per week. The reps had internalised the cadence because the system made ignoring a lead impossible to do quietly. Cold rate — leads untouched for seven or more days — dropped from 38% to 7% within six weeks of launch.
The management reporting change was felt immediately. The Monday morning WhatsApp round-robin stopped on day one. The Director called the Sales Head the first Monday after launch and said: 'I can see the numbers myself — why are we having the 5 p.m. meeting?' The meeting still happens, but its character changed. Instead of spending 45 minutes establishing what the numbers were, the team now spends 45 minutes discussing what the numbers mean and what to do about them. The Sales Head estimates he recovers four working hours per week — time previously spent compiling data that is now compiled automatically.
Duplicate lead incidents dropped to zero within the first month. The deduplication engine matched 38 incoming leads in the first month against existing records — leads that would previously have been assigned to a second rep and generated a duplicate-assignment dispute. The channel partner commission dispute rate fell correspondingly. The CP manager noted that the disputes that used to consume a full day of negotiation each quarter had simply stopped occurring — the system's timestamp record settled any ambiguity before it became a dispute.
Lead-to-site-visit conversion improved from 12% to 21% over the first quarter. The sales head's analysis pointed to two causes. First, the reminder engine ensured that every lead in the Contacted stage was followed up within three days — previously, a rep with a full load might not call a prospect for ten days, by which time the buyer had either lost interest or booked elsewhere. Second, the pipeline's stage discipline meant reps could not park leads in Contacted indefinitely without logging activity — the system surfaced stale leads to the manager, who pushed for closure or reassignment.
Site-visit-to-booking conversion improved from 8% to 14%. The post-visit notes feature was the mechanism. When a rep entered visit notes — the buyer liked the fourth-floor view, objected to the parking allocation, asked about the builder-buyer agreement timeline — the sales manager reviewed those notes before the rep's next call. The manager could coach the rep on how to handle the specific objection, suggest what document to share, or join the next call. Previously, a post-visit debrief happened informally if at all. The system made it structural.
The data ownership problem — the incident that had initiated the project — was resolved structurally. When a rep resigned in month four, the handover took 20 minutes. The manager opened the departing rep's lead list in the CRM, reassigned all 54 leads to two other reps with a note on each lead's last interaction, and drafted a message to each buyer introducing the new rep. The company lost no lead data. Three of those 54 leads converted to bookings in the following two months — bookings that, under the previous system, would have walked out the door with the departing rep's phone.
Lead cold rate (leads untouched for 7+ days)
Management pipeline reporting time
Duplicate lead assignments per month
Lead-to-site-visit conversion rate
Site-visit-to-booking conversion rate
Lead data loss on rep exit
Want a system like this for your real-estate organisation?
Get a quote for Real Estate CRM & Sales Pipeline