Industry guide · Updated August 2026
Every builder we've worked with had a CRM and a spreadsheet running beside it. The spreadsheet is always doing the same job — working out what channel partners are owed. That gap is the whole story.
The mismatch
These aren't preferences. They're structural differences between selling a subscription and selling a flat, and no amount of custom fields fixes them properly.
A channel partner registers a client, your in-house team also has them from a hoarding enquiry. Generic CRMs treat this as a duplicate. In real estate it's a commission dispute worth lakhs, and it needs a lead-attribution rule with a validity window — not a merge button.
You're not selling 500 identical units. You're selling C-704 specifically, and once it's blocked nobody else can. A CRM without live unit-level inventory means two sales heads confirm the same flat, and somebody makes an apology call.
Slab-based rates, tiered brokers, payments released against collection milestones rather than booking, TDS. Most teams end up running this in a spreadsheet beside the CRM — which is the clearest signal that the CRM doesn't fit.
In residential sales, site visit to booking is the conversion that matters. Scheduling, reminders, no-show follow-up and per-executive visit conversion are core reporting — not something to approximate with a task field.
Requirements
Bring this list to any CRM demo. Ask the vendor to show each one working rather than describe it — the first four are where ready products usually fall short.
| Module | Priority | What it has to do |
|---|---|---|
| Unit inventory board | Must have | Live tower–floor–unit grid with available, blocked, booked and registered states. One source of truth every sales head sees. |
| Channel partner portal | Must have | Partners register leads themselves, see their own pipeline and commission status. Removes the daily WhatsApp reconciliation entirely. |
| Lead attribution rules | Must have | First-registration wins, with a configurable validity period. Decides commission disputes by policy rather than by argument. |
| Site visit scheduling | Must have | Booking, reminders, no-show handling, and visit-to-booking conversion by executive and by source. |
| Payment & demand schedule | Must have | Construction-linked plans, demand letter generation, receipts, and an ageing view of what's overdue. |
| Document vault | High value | Allotment letters, agreements, KYC and RERA records against each booking, retrievable during an audit without a phone call. |
| Post-booking handover | High value | Possession milestones, snag lists and customer updates. Where most builders lose goodwill they spent crores earning. |
| Source-level ROI | High value | Cost per booking by portal, hoarding, partner and referral. Almost nobody tracks this properly, and it usually reallocates budget on day one. |
What it costs
Most developers should start with a ready product. The custom case only opens up at a certain scale and a certain kind of complexity.
| Route | Typical cost | Right for |
|---|---|---|
| Off-the-shelf real estate CRM | ₹1,200–₹4,000 / user / month | One or two projects, standard sales process, small in-house team. Fastest route — live in weeks. |
| Configured generic CRM | ₹80,000–₹3,00,000 setup + seats | Works if your channel partner network is small. The commission logic is where this approach usually breaks. |
| Custom builder CRM | ₹10,00,000–₹35,00,000 build | Multiple projects, large partner network, unusual commission structures, or an ERP it has to talk to. |
Planning ranges from Indian market pricing, not quotes. The custom figure assumes inventory, partner portal, commissions and collections in one system, and excludes the 15–20% annual maintenance every custom build carries. Read the full comparison in our custom CRM vs Zoho vs Salesforce breakdown.
Don't build if
We build custom CRMs and we still send most single-project developers to a ready product. A build you don't need is the most expensive thing on this page.
Questions
Not covered here? Ask us directly — we answer scoping questions without putting you into a sales sequence.
Four reasons specific to the industry. Leads can be claimed by both a channel partner and your in-house team, which is a commission dispute rather than a duplicate record. Inventory is unit-level and exclusive — once C-704 is blocked, nobody else can sell it. Commission calculations involve slabs, tiers and collection-linked release. And the site visit, not the call, is the pipeline stage that predicts a booking. Generic CRMs handle none of these natively.
Off-the-shelf real estate CRMs run ₹1,200 to ₹4,000 per user per month. Configuring a generic CRM like Zoho for property sales costs ₹80,000 to ₹3,00,000 upfront plus seat fees. A custom builder CRM covering inventory, channel partners, commissions and collections costs ₹10,00,000 to ₹35,00,000 depending on project count and integrations, plus roughly 15 to 20 percent annually for maintenance.
When two things are true together: a channel partner network large enough that commission reconciliation takes real staff time every week, and a commission structure that doesn't fit a simple percentage. A single-project developer with a small in-house team should use a ready product. A developer running four projects across two cities with 200 registered partners will save more than the build costs within two years.
Zoho works reasonably for smaller developers with a straightforward sales process, especially with a real-estate-specific configuration. It struggles with unit-level exclusive inventory and complex partner commissions. Salesforce handles both with enough customisation, but the implementation and admin cost is rarely justified below a large sales organisation. Most mid-size Indian builders end up either on a specialist product or building their own.
Running commission calculation in a spreadsheet next to the CRM. It always starts as a temporary workaround and becomes permanent, and it means your CRM reporting and your actual payouts disagree. If your finance team maintains a parallel sheet to work out what partners are owed, that sheet is the specification for whatever you build next.
Four to eight months for a production system covering inventory, leads, site visits, bookings, commissions and collections. The first usable module — usually inventory plus lead capture — can be live in eight to ten weeks if it's built in phases, which is how we'd recommend doing it. Building everything before anyone uses any of it is how these projects go wrong.
Whatever your finance team maintains by hand is the specification. Send it across and we'll tell you whether it's a configuration problem, an integration problem, or a genuine case for building.
Book a process review
