How to Use Your Real Estate CRM to Manage Redevelopment Project Leads in India
Redevelopment projects in India have longer pre-sales cycles, more complex buyer types, and more regulatory milestones than new launches — and a CRM is the only way to manage both the existing occupants and new buyers without losing track of either. If you’re handling even one redevelopment project, you already know that a spreadsheet breaks down before the consent phase is complete. A real estate CRM for redevelopment projects in India gives you two separate pipelines, automated construction update broadcasts, and compliance tracking built specifically for the RERA and TDS requirements that come with every redevelopment deal.
This guide walks through exactly how to configure your CRM for redevelopment — from the first occupant consent conversation to the final possession handover.
Why Redevelopment Is Booming in Indian Cities (and Why It’s Operationally Complex)
Redevelopment is no longer a niche segment. Across India’s major metros, aging housing stock, rising FSI allowances, and land scarcity have made redevelopment the primary growth engine for urban real estate developers.
Mumbai is the most active market. SRA (Slum Rehabilitation Authority) projects are underway across Dharavi, Kurla, Ghatkopar, and Mulund. MHADA is redeveloping old colonies in the western and central suburbs. Old chawl reconstruction is happening at scale across the island city and the eastern suburbs. The quantum of units being created through Mumbai redevelopment alone runs into the tens of thousands every year.
Pune has seen a wave of old wadas and pre-2000 residential buildings being redeveloped under PMC and PMRDA jurisdiction. Bangalore is witnessing the systematic redevelopment of old independent houses in Indiranagar, Koramangala, and HSR Layout into multi-storey apartment buildings. Delhi NCR has DDA-led redevelopment schemes alongside organic old colony redevelopment in localities like Rohini, Dwarka, and Vasant Kunj.
Why This Creates an Operational Problem for Agents
Every redevelopment project has two fundamentally different stakeholder groups, and they need completely different management approaches:
- Existing occupants (tenants, flat owners, society members) — these people are giving up their current home in exchange for a new or upgraded unit plus transit rent during construction. They are not buyers. They need consent management, transit rent tracking, and regular project updates.
- New external buyers — these are purchasers of the additional FSI units that the developer sells to fund the project. They are your actual sales pipeline and need a full lead-to-possession journey tracked.
When agents try to manage both groups in the same spreadsheet or the same WhatsApp group, the result is chaos. Occupants receive sales messages meant for buyers. Buyers receive consent-related communications they don’t understand. Follow-up priorities get mixed up. Leads go cold.
RERA adds another layer of complexity. Redevelopment projects that exceed RERA thresholds (plot area above 500 sq mt or more than 8 apartments) must be registered with the relevant state RERA authority. This means the developer needs to disclose all project details to buyers, maintain a buyer register, and adhere to the RERA timeline for delivery. Consent requirements from existing occupants add timeline uncertainty that directly affects what you can promise new buyers about possession dates.
A real estate CRM for redevelopment projects in India is the operational backbone that keeps both pipelines separate, both stakeholder groups informed, and all compliance milestones documented.
The Two Pipelines Every Redevelopment Agent Needs in Their CRM
Pipeline 1 — Existing Occupants (Tenants / Society Members)
Existing occupants are people who already live in or own units in the building being redeveloped. Under the redevelopment arrangement, they get a free new or upgraded flat — plus transit rent paid by the developer while construction is ongoing — in exchange for vacating and signing consent.
Your CRM must track the following for every occupant record:
- Consent status — Pending, Signed, or Disputed. This is the single most important field for the entire project timeline because construction cannot begin without the required consent percentage.
- Transit rent amount and payment history — monthly payments from the developer to the occupant while they’re in alternate accommodation.
- Alternate accommodation address — where the occupant is currently living during construction.
- Expected return date — when their unit in the new building is expected to be ready.
- Communication log — every call, site visit, and message exchanged with the occupant.
These people do not need a sales pipeline. They need a relationship management pipeline. There are no deal stages like “price negotiation” or “home loan processing” — instead, the stages are “initial meeting done,” “consent pending legal review,” “consent signed,” and “transit shift complete.”
Treating occupants like buyers is the most common mistake agents make in redevelopment projects — and it creates confusion in your CRM data and in your messaging.
Pipeline 2 — New External Buyers (Purchasing Additional Units)
The redevelopment project creates additional FSI-permitted units beyond what the existing occupants will receive. The developer sells these units to recover construction costs and generate profit. These are your actual sales leads.
New buyer leads arrive through:
- Portal enquiries from 99acres, MagicBricks, Housing.com, and NoBroker
- WhatsApp referrals from existing buyers and channel partners
- Walk-ins during pre-launch events or site office visits
- Social media campaigns targeting buyers in the locality
The sales pipeline for new buyers follows a standard structure: Enquiry → Site Visit → Price Discussion → Booking → Agreement → Construction Updates → Demand Letters → Possession. The critical difference from a regular new launch is timeline. Redevelopment projects routinely take 3 to 5 years from the pre-launch stage to possession. Leads that express interest today may not be ready to book for 12–18 months. Leads that book today won’t take possession for 3–4 years.
This means your CRM must be capable of nurturing leads and active buyers over years — not months. Automated WhatsApp broadcasts, scheduled follow-up sequences, and buyer portal access are not optional features in a redevelopment project. They are the difference between buyers who stay engaged and buyers who cancel or dispute.
Redevelopment Project Milestones Your CRM Must Track
Every redevelopment project moves through a series of milestones that affect both occupant management and new buyer communication. Your CRM should have a structured way to record each milestone and trigger communications automatically.
| Stage | Milestone | What Your CRM Should Record |
|---|---|---|
| Pre-demolition | Building survey complete | Survey documents, contractor notes, RERA application status |
| Consent phase | % of occupant consent signed | Names, consent status, disputed cases, legal notices sent |
| RERA registration | Registration number obtained | RERA project ID, registered date, registration expiry |
| Demolition / start | Demolition complete | Date of completion, site photos, buyer notification log |
| Construction — floors | Foundation, plinth, structural floors | Construction update log, auto-WhatsApp sent to all buyers |
| Demand letters | Payment milestone demands to buyers | Amount due, due date, payment received/pending, TDS tracked |
| Possession | Possession schedule | Occupant return date, buyer handover date, snagging checklist |
Every time you update a construction milestone in your CRM, the system should automatically broadcast a WhatsApp update to all registered buyers. This is not a nice-to-have. Over a 4-year construction cycle, buyers who don’t receive regular updates become anxious, generate support calls, and sometimes file RERA complaints. Consistent, automated milestone communication eliminates the vast majority of buyer anxiety at zero additional effort from your team.
How to Set Up Your CRM for a Redevelopment Project (Step by Step)
Configuring Realatic for a redevelopment project takes 1 to 2 days. Here is the exact setup sequence:
-
Create a project record in Realatic with the redevelopment project name, RERA registration number, site address, and expected possession date. This becomes the anchor record for all occupant and buyer data.
-
Create two pipeline tracks within the project: “Existing Occupants” and “New Buyers.” These are separate pipelines with different stage definitions and different automation rules. Never merge them.
-
Import existing occupant details with consent status as a custom field. Set the consent field as a dropdown with three values: Pending, Signed, Disputed. Add fields for transit rent amount, alternate address, and expected return date.
-
Configure automated construction update messages. In Realatic, when you advance a project milestone, all contacts tagged to that project — both occupants and buyers — receive a WhatsApp message automatically. Set the message templates up before the project goes live.
-
Set up demand letter tracking. When a payment milestone is due, the system creates a task for the assigned agent and sends an automated WhatsApp reminder to the buyer. Track the payment received date and the TDS amount for every demand letter.
-
Tag new buyer leads from portal integrations with the redevelopment project tag. Realatic integrates natively with 99acres, MagicBricks, Housing.com, and NoBroker — leads from these portals arrive automatically. Tag them to the correct project at the routing stage.
-
Use AI lead scoring to prioritise new buyer enquiries during the pre-launch window. Realatic’s AI scoring auto-qualifies incoming enquiries based on engagement signals and assigns them a priority score, so your sales team works the highest-intent leads first.
-
Set reminder sequences for occupants who haven’t signed consent. Create a weekly check-in task for the relationship manager assigned to each pending-consent occupant. These are not sales follow-ups — they are structured relationship management touchpoints to address objections and provide project clarity.
Managing the Pre-Launch Window for New Unit Sales
Most redevelopment projects begin taking new buyer expressions of interest during the consent phase or demolition stage — often 12 to 24 months before construction actually begins. This is a critical window that most agents mismanage.
Early-mover buyers are attracted by pre-launch pricing, which can be 10–20% below the post-launch price. They’re also taking on more timeline risk — they’re buying into a project that may not have RERA registration yet and certainly doesn’t have a completed structure.
Your CRM approach for the pre-launch window:
- Create a “Pre-Launch Waitlist” stage at the top of your new buyer pipeline. This is not a committed booking — it’s a structured interest record with token amount collected (if any) and communication preferences recorded.
- Log every pre-launch enquiry in Realatic, not in WhatsApp. Pre-launch interest expressed via WhatsApp and stored only there is lost interest. When the actual launch happens 18 months later, you have no way to reconnect with those prospects.
- Send regular construction updates via Realatic’s WhatsApp broadcast to the entire pre-launch list. Every milestone — RERA registration obtained, demolition complete, foundation work started — is an opportunity to re-engage waitlist leads and move them closer to booking.
- Use AI lead scoring to identify which waitlist leads are most likely to convert when the actual launch happens. By the time you go live, some leads on your list will have gone cold, bought elsewhere, or increased their budget. AI scoring helps you prioritise outreach on the highest-probability leads instead of treating everyone equally.
Realatic’s WhatsApp inbox is included free on all plans, which means you can maintain pre-launch communication with hundreds of prospects at zero additional cost. For a project with an 18–36 month pre-launch cycle, this compounds into a significant advantage over agents managing pre-launch lists manually.
Mumbai-Specific Context: SRA and MHADA Redevelopment
Mumbai deserves its own section because the SRA and MHADA frameworks create occupant management complexity that no other Indian city matches.
SRA (Slum Rehabilitation Authority) projects involve existing slum residents — classified as PAPs (Project Affected Persons) — who are entitled to free 300 sq ft or 269 sq ft carpet area flats in the new building. The developer simultaneously constructs market-rate “free sale” units to cross-subsidise the project. For agents working on SRA projects, the CRM must handle:
- PAP tracking with separate contact records distinct from market buyers
- Transit rent payment status for each PAP family
- SRA approval timeline milestones (which can span years)
- The distinction between free-sale inventory and PAP component inventory to prevent any unit from being double-promised
MHADA redevelopment involves existing MHADA colony residents getting upgraded units — typically from older, smaller flats to modern larger ones — while the developer sells additional units created through increased FSI. The occupant management complexity here is similar to SRA but with MHADA Board approvals in the critical path.
Society self-redevelopment is a growing model where the housing society itself appoints a PMC (Project Management Consultant) or architect and manages the redevelopment without a private developer. The agent’s role in self-redevelopment is different — the sales focus is entirely on the additional units being created, and the occupant relationship is managed by the society committee, not the developer. Realatic handles this through flexible project configuration that doesn’t mandate a developer counterparty.
Common Mistakes Agents Make with Redevelopment Leads
These are the mistakes that consistently cause revenue loss and relationship damage in redevelopment projects.
Treating occupants like buyers. Existing occupants don’t have a budget, a choice of unit configuration, or a payment plan to negotiate. Sending them price sheets and sales messaging creates distrust and friction. They need project updates, transit rent confirmations, and consent-related communications — nothing else.
Losing track of pre-launch interest in WhatsApp. Hundreds of buyers express pre-launch interest over WhatsApp and get added to a group. Eighteen months later, the launch happens, and there’s no structured way to identify who’s still interested, who bought elsewhere, and who increased their budget. All that early-stage interest is wasted. Every pre-launch enquiry must be logged in the CRM at the point of first contact.
Not sending regular construction updates. A buyer who books a flat in a redevelopment project and then hears nothing for 6 months becomes a problem buyer. They call the office repeatedly, escalate to RERA, and in some cases attempt to cancel. Automated WhatsApp milestone updates sent through Realatic eliminate this problem systematically. The buyer feels informed; your team handles zero inbound anxiety calls.
Missing demand letter follow-up. Payment milestone demand letters in redevelopment projects follow a construction-linked plan. When a milestone is hit, the demand letter goes out, and the buyer has a deadline to pay. Missing the follow-up on unpaid demands leads to cash flow gaps for the developer and disputes with buyers. Manual tracking of this across 50–100 buyers across multiple projects is not viable. It must be CRM-automated.
Using a one-size-fits-all pipeline. Agents who force both occupants and new buyers into a single sales pipeline end up with meaningless conversion metrics and wrong follow-up priorities. The system assigns “sales stages” to occupants who are not buying anything, which distorts pipeline reporting and leads to incorrect outreach.
How Realatic Handles Redevelopment Projects
Realatic is built on 12 real estate modules covering lead-to-possession management. For redevelopment projects specifically, the relevant capabilities are:
Multi-project management. Run the occupant pipeline and the new buyer pipeline simultaneously across multiple redevelopment projects in a single CRM instance. Agents assigned to Project A see only Project A’s data; managers see across all projects.
WhatsApp broadcast. When you update a construction milestone in Realatic, all registered contacts for that project — buyers and occupants — receive a WhatsApp message automatically via the built-in WhatsApp inbox. No manual broadcasting. No missed contacts.
TDS tracking. Demand letter payments in redevelopment projects attract TDS under Section 194-IA where applicable. Realatic’s TDS compliance tools track the deductible amount, the payment date, and the certificate status for every demand letter payment.
RERA compliance. Store the RERA project registration number, registration date, and expiry within the project record. Log all required buyer disclosures. Maintain the buyer register in a format that supports RERA audit requirements.
Inventory management. As additional FSI units are created and sold, Realatic’s inventory module tracks unit status — available, reserved, booked, registered — and prevents any unit from being double-sold or double-promised. This is critical in redevelopment projects where the unit count may evolve during the project lifecycle.
Buyer portal. Every buyer in Realatic gets access to a self-service buyer portal where they can view their payment schedule, download demand letters, check construction progress updates, and access their agreement and other documents. This reduces inbound support calls to your office by eliminating the most common reason buyers call: “What is the status of my payment / my unit / my possession date?”
Native portal integration. New buyer enquiries from 99acres, MagicBricks, Housing.com, and NoBroker flow directly into Realatic without manual data entry. Leads are tagged, scored, and assigned automatically.
Explore all Realatic features →
Frequently Asked Questions
Can I manage both occupant consent and new buyer sales in the same CRM?
Yes — and this is exactly how Realatic is designed to be used for redevelopment projects. You create two separate pipeline tracks within the same project record: one for existing occupants (with consent status, transit rent, and relationship management stages) and one for new buyers (with a full sales pipeline). Both pipelines share the same project milestone data, so when you update a construction stage, both occupants and buyers receive the relevant WhatsApp notification. The data stays separate; the project communication is unified.
How does Realatic handle the long 3–5 year timeline for redevelopment projects?
Realatic’s automated follow-up sequences and WhatsApp broadcast capabilities are designed specifically for long-cycle real estate sales. You configure milestone-based communication templates once — at project setup — and the system sends them automatically every time a milestone is updated. For buyers who haven’t yet booked (pre-launch waitlist), you can set up periodic broadcast sequences to keep them engaged over 18–36 months. AI lead scoring re-ranks your pre-launch list continuously so your sales team always knows which leads have the highest current intent.
Does Realatic support TDS tracking on demand letters?
Yes. Realatic’s TDS compliance tools track TDS deductions on property payments, including construction-linked demand letter collections. For each payment received, you can record the gross amount, the TDS deducted, the net amount received, and the TDS certificate status. This data is available at both the individual buyer level and the project aggregate level for compliance reporting.
Can I use Realatic for society self-redevelopment projects?
Yes. Society self-redevelopment projects don’t follow the standard developer-led model, but the CRM requirements are similar: occupant management, new unit sales, milestone tracking, and construction updates. Realatic’s project configuration is flexible enough to handle self-redevelopment — you can omit developer-specific fields and configure the occupant pipeline to reflect the society committee’s communication requirements. The new unit sales pipeline works identically to any other redevelopment project.
How do I handle pre-launch interest before RERA registration?
Before RERA registration, developers legally cannot accept bookings for units in redevelopment projects above the RERA threshold. However, agents can maintain a structured interest register — essentially a pre-launch waitlist — where prospects record their interest without making a committed financial commitment. In Realatic, create a “Pre-Launch Interest” stage at the top of your new buyer pipeline. Log every enquiry, token amount (if any), preferred unit type, and budget. Set up automated WhatsApp sequences to keep this list warm. Once RERA registration is obtained, you have a prioritised, structured list to convert into bookings — rather than a disorganised WhatsApp group from 18 months ago.
Start Managing Your Redevelopment Projects in Realatic Today
Redevelopment is one of the most operationally demanding segments in Indian real estate — long timelines, multiple stakeholder types, RERA compliance requirements, and TDS tracking on every demand letter. Agents who manage this in spreadsheets or WhatsApp groups consistently lose leads, miss follow-ups, and frustrate both occupants and buyers.
Realatic’s free plan includes 3 users, 100 leads per month, and 1 project — with no credit card required. That’s enough to set up your first redevelopment project, configure both pipelines, and test the WhatsApp broadcast system before committing to anything. When you’re ready to scale across multiple projects and larger teams, the Growth plan starts at ₹499 per user per month and the Pro plan at ₹1,199 per user per month.
Setup takes 1 to 2 days. Your occupant consent tracking, new buyer pipeline, and automated construction update broadcasts can all be live before the week is out.