Why your CRM should be personalised to your agency — and what that actually means
No two property businesses sell the same way. A plot dealer in Bathinda and a resale broker in Gurugram need different fields, different stages and different reports. Here is what should be adjustable in a real estate CRM, what it should cost, and how to ask for it.
Most CRM software is built for one imagined customer and everybody else has to bend around it. In Indian real estate that mismatch is severe, because the business varies so much between cities and segments. A builder selling identical 3 BHK flats in one tower needs almost nothing that a plot dealer needs, and a rental agency needs a third thing entirely.
The same CRM, three completely different businesses
| Business | What matters to them | What they never use |
|---|---|---|
| Plot and land dealer, Punjab or Haryana | Gaj, marla and kanal sizes, rate per gaj, PLC for corner and park facing, plot dimensions, different sellers under one project | BHK, furnishing, floor plans, maintenance charges |
| Resale flat broker, metro city | BHK including 3+1 with servant room, furnishing status, floor, society name, owner versus dealer sourcing | Plot dimensions, marla, project area |
| Rental agency | Monthly rent, security deposit, lock-in period, available-from date, tenant preferences | Base price, cheque and cash split, PLC |
| Builder or developer | Unit inventory across towers, booking stage, payment milestones, channel partners | Individual seller records, resale negotiation fields |
A CRM that shows every one of these fields to everyone is not flexible. It is just cluttered.
What should be personalisable in a real estate CRM
When we say we personalise the CRM for a client, this is the actual list. None of it requires you to explain your business twice:
- Fields. Add what your segment needs, hide what it does not. A rental agency should not scroll past a cheque-and-cash split on every form.
- Pipeline stages. The default is new, contacted, qualified, site visit, negotiation, won or lost. If your team works in token, agreement and registry stages instead, the board should say that.
- Property types and sources. Your own list, not a fixed dropdown. If you deal in SCO booths or farmhouse land, those belong in the list.
- Area units. Gaj, sq ft, marla, kanal, acre, sq m and hectare, with the one your city actually uses set as the default.
- PLC structure. Corner, park facing, wider road, floor, main road and green belt, charged as a percentage, per unit area or a flat amount — whichever way you quote it.
- WhatsApp templates. Your wording, your signature, your token order, previewed before every send.
- Dashboard. Every widget can be switched on or off per user, so an owner and a field agent see different opening screens.
- Roles and visibility. Whether an agent sees the whole database or only their own leads, and which sections they can open at all.
- Reports and exports. The CSV columns you actually hand to your accountant.
What personalisation should cost
This is where the industry gets uncomfortable. Enterprise CRM vendors typically treat customisation as a separate revenue line: an implementation fee up front, then a change request for anything you did not think of during onboarding. For a ten-person agency that model is backwards, because you learn what you need in month three, not in week one.
How we do it
Configuration is included. If you need a field, a stage, a template, an area unit or a report that does not exist yet, you ask and we build it into your account. We do not invoice change requests, and we do not require a minimum contract to qualify. The reason is simple: a request from a working broker is usually a gap in the product, so fixing it for you fixes it for everyone.
How to ask for a change so it actually gets built
Vague requests produce vague software. The requests that get built fastest look like this:
- Describe the deal, not the feature. “A client wants a 3 BHK with a servant room, furnished, in Aura Valley, buying within a month” tells us more than “add more fields”.
- Send a real example. An actual listing, an actual WhatsApp message, an actual sheet. Screenshots are ideal.
- Say what breaks today. Whether it is slow, wrong, or simply missing changes how we fix it.
- Tell us who needs it. Owner, admin or field agent — that decides where it goes and who can see it.
Where personalisation should stop
Being honest about limits matters more than saying yes to everything:
- We will not fork your account into separate software. Your configuration is yours, but the underlying product stays one product, so you keep getting every update.
- We will not break the audit trail. Who changed what stays recorded, even if it would be convenient to hide it.
- We will not add a field that duplicates one that exists. Two places to record a phone number guarantees the wrong one gets called.
- We will say no when something will hurt you later. Turning off role restrictions so everyone can see everything is easy on day one and painful when an agent resigns.
The test to apply to any CRM you are evaluating
Before you pay for anything, ask the vendor one question: “I sell plots in gaj with corner PLC charged as a percentage. Show me that on a live screen.” If the answer involves a professional services quote, a six-week implementation or a note field, keep looking. Software that cannot describe your inventory correctly cannot match a buyer to it, price it, or send it to a client on WhatsApp.