A CRM for real estate: why the standard object model does not fit
Builders and brokers sell units in projects, not opportunities. What a property CRM needs that a generic one lacks, and how to model it without a migration.
Every CRM demo shows Leads, Contacts, Accounts and Opportunities, and explains that this is how selling works. Then a property developer tries to record that a couple is interested in unit 804 in Phase 2, needs a home loan, visited on Saturday, and has paid a booking amount against a payment schedule tied to construction milestones.
None of that is an opportunity. So it goes into a custom field called something like Custom_Field_14, and the rest goes into a spreadsheet — which is where the truth then lives, making the CRM decoration.
What a property business actually has
Properties, as objects
A unit exists before anyone enquires and after the sale closes. It has a configuration, a floor, a facing, a carpet area, a rate per square foot and a possession date. Several deals may reference the same unit over time.
The important part is reference, not copy. If each deal holds its own copy of the price, a revision updates nothing, and somebody quotes last quarter's rate to a buyer. A deal pointing at a property means one change updates everywhere.
Site visits
The conversion event in residential sales is not a call, it is a visit. It needs a date, a slot, an owner, and an outcome — and it needs to be bookable without a phone call, because most enquiries arrive outside office hours.
Two ways of selling, at least
Direct and through channel partners. Different stages, different required fields, different commission conversations. Those are two pipelines, not one pipeline with extra stages, and a CRM that only offers one will have you faking it within a fortnight.
How to model it without a project
In TicAte CRM you create whole objects, not just extra fields on somebody else's object. A Properties module with its own fields, its own sections and its own relationships to deals and contacts is defined in the interface in minutes — no release, no quotation from a consultant. Modules you define yourself covers the difference between a field and a module, and the test for which one you need.
Add a pipeline per way of selling, a layout per team so accounts and sales see the fields that concern them, and stage automations that raise the follow-up task nobody remembers.
The half that lives on WhatsApp
Property enquiries arrive on WhatsApp and go cold there. A couple messages at 10:47pm asking the price; by morning they have messaged four other projects and two replied overnight.
If that conversation lives on one person's phone, the CRM is missing the half of the sale where the selling happens. With TicAte WhatsApp on the same account it is the same customer record — message from the deal, and the reply lands back on it. What to automate on a property enquiry goes through the 10:47pm problem in detail.
The measure worth tracking
Not leads. Site visits booked from enquiries that arrived outside office hours — the ones your current process cannot reach at all. That number is the gap between what you are paying for in advertising and what you are collecting.
