The CRM Department in Indian Real Estate: What the Post-Sales Team Actually Owns (2026)

Ask a Mumbai developer where the CRM department sits and you will get a puzzled look from the software side of the house. In Indian real estate, the "CRM department" is not a tool. It is the customer relationship team that takes over after the booking amount clears: agreements, demand letters, collections, loans, registration, possession and the long tail of homebuyer queries. Most developers run it as an afterthought, staffed by whoever is free. That is expensive, because collections slippage and unhappy buyers show up as delayed cash flow and RERA complaints.

This guide lays out what a post-sales CRM team actually owns, how to structure it for a one-project builder versus a multi-city developer, and the KPIs worth putting on a wall. It is written for developers restructuring the function and for CRM executives who want a clear scope of work. For the end-to-end process view, read our guide to real estate post-sales management from booking to possession; this post is about the people and the ownership.

What the CRM department is (and is not)

The department owns the customer from the moment a booking is confirmed until the society is handed over and beyond. It is not the presales team that qualifies enquiries, and it is not the sales team that closes bookings. A clean handover between those teams and CRM is the first thing to fix: the sales executive's promises on possession timelines, payment plans and waivers must be visible to the CRM executive on day one, not rediscovered when the buyer complains.

It is also not a call centre. A call centre answers; a CRM department owns outcomes such as demand letters cleared within terms, agreements executed on time, and a possession experience that produces referrals.

The seven things a post-sales CRM team owns

• Booking-to-agreement conversion: documentation checks, KYC, cost sheet confirmation, stamp duty and registration scheduling. Agreement TAT is the single best early indicator of team health.
• Demand letters and collections: raising demands against construction milestones, sending reminders, tracking receipts, and following up on ageing buckets (0-30, 31-60, 61-90, 90+ days).
• Home loan coordination: bank tie-ups, sanction letters, disbursement tracking against milestones, and resolving bank queries before they stall a demand.
• Customer communication: milestone updates, construction photos, payment reminders and grievance handling, increasingly over WhatsApp because that is where buyers actually reply.
• Change requests and documentation: name additions, unit swaps, cancellation and refund processing, NOC and no-dues certificates.
• Registration and possession: final dues, snag lists, possession letters, key handover and the handover checklist that closes the file.
• Post-possession relationship: society formation support, maintenance handover, and referral and resale programmes that feed the next launch.

A practical org structure

Single project or up to 300 units

A lean setup works: one CRM head who also handles escalations, two to three CRM executives split by tower or wing, and a part-time documentation coordinator. Collections follow-up is shared. The risk here is key-person dependency, so keep every buyer's file in the system and not in an executive's Excel sheet.

Multi-project or multi-city developer

Separate the work into three desks under a central CRM head: a documentation and agreements desk, a collections and loans desk, and a customer experience desk covering communication, grievances and possession. Add a project-level CRM lead for each large project who reports into the central head but sits with the site team. A good rule of thumb many developers use is one CRM executive for every 80 to 120 active buyers during peak construction, adjusted for how much of the follow-up is automated.

A simple RACI for the handover

Most post-sales friction comes from unclear ownership. A short RACI, agreed once and shared across teams, removes most of it.

• Sales is accountable for accurate booking data, the agreed payment plan and any commitments made. CRM is responsible for verifying them within 48 hours of booking.
• CRM is accountable for agreement execution and demand raising. Finance is responsible for receipts reconciliation and consulted on waivers.
• Project and construction teams are accountable for milestone certification, because a demand cannot go out until the milestone is certified. CRM is informed the same day.
• Legal is responsible for agreement drafts and RERA-compliant documentation. CRM is informed and owns the buyer-side coordination.

KPIs that matter

Resist a dashboard of twenty metrics. Six are enough to run the department:

• Agreement TAT: days from booking to executed agreement. Aim to cut this steadily quarter on quarter and review every case beyond your set limit.
• Collection efficiency: amount collected versus amount demanded in the period, tracked by project and by ageing bucket.
• Demand-to-receipt cycle: days between a demand letter and the receipt. A lengthening cycle is an early warning before ageing buckets worsen.
• Loan disbursement lag: days from milestone certification to bank disbursement.
• Grievance closure TAT and reopen rate: how fast issues are closed and how many come back.
• Possession NPS: a short survey at key handover. This is the number that predicts referrals and reviews for your next launch.

Hiring and training the team

The best CRM executives are rarely the best closers. Look for people who are comfortable with documents, numbers and difficult conversations. Train them on RERA obligations, payment plan structures, home loan processes and stamp duty basics before they ever speak to a buyer. Pair every new hire with a senior executive for the first two demand cycles. And give them the same access to buyer history that the sales team had, so the relationship does not restart from zero.

Where the system makes or breaks the team

A post-sales team running on spreadsheets and shared inboxes spends most of its day searching for information. The moment you have more than a couple of projects, the cost shows up in missed reminders and reconciliation errors. A CRM built for real estate should hold the booking, payment schedule, demand letters, receipts and communication in one buyer record, trigger reminders against due dates, and show collections ageing without a manual report.

This is the gap Sell.do's post-sales module is designed to close: bookings, agreements, demand letters, collections and possession tracked in the same system where the lead first came in, so the CRM executive sees the original source, the commitments made and the payment status in one view. If you are weighing how software supports this function, our piece on post-sales and CRM in Indian real estate covers what to look for, and how a CRM manages post-sales consumer engagement shows the communication side in practice.

Common mistakes to avoid

• Treating CRM as a cost centre. Every week of delay in a milestone demand is a week of delayed inflow.
• No single owner for collections ageing, so everyone assumes someone else is chasing the 90+ day accounts.
• Letting sales promises live in WhatsApp chats instead of the buyer record.
• Measuring activity (calls made) instead of outcomes (receipts collected, agreements executed).

For a broader checklist on keeping buyers satisfied after booking, see post-sales strategies developers should never ignore.

Related reading

• Real Estate Post-Sales Management in 2026: From Booking to Possession
• Post-Sales and CRM in Indian Real Estate: What Developers Need in 2026
• How CRM Helps Manage Post-Sales Consumer Engagement

See it in your own post-sales workflow

If your CRM team is still stitching together bookings, demand letters and collections across spreadsheets, see the AI-agentic CRM built for Indian real estate. Book a walkthrough at sell.do and we will map your current post-sales process onto bookings, agreements and collections in one view.