How should projects and units be modelled?
Property is a case where the standard CRM objects are not enough on their own. A buyer is interested in a project, then a unit type, then a specific unit. Reporting needs to show demand by project and unit, not just by deal.
HubSpot's custom objects let a business model things the standard objects do not describe well, and associate them with contacts, deals and tickets; HubSpot says they require an Enterprise subscription (HubSpot Knowledge Base). For developers we typically model projects and units as their own objects, linked to buyers and deals, with unit status kept in step with the sales system of record.
Where a group sells across several countries, HubSpot's multiple currencies let deals be recorded in local currency and reported in one (HubSpot Knowledge Base).
Why does WhatsApp decide the enquiry stage?
In much of the region, the first serious conversation with a property buyer happens on WhatsApp. HubSpot connects WhatsApp Business natively to its conversations inbox on Marketing Hub or Service Hub Professional or Enterprise (HubSpot Knowledge Base). That puts every enquiry on the buyer's record, routed to the right sales team, with response time measurable.
Speed matters here more than in most industries, because buyers often enquire about several launches at once. The design questions are routing by project and language, cover outside working hours, and consent for follow-up under each market's data protection law. Our messaging-first service playbook covers the detail.
Where do AI agents help a developer?
Bounded, high-volume steps are the right start:
- First response: answering common questions on location, sizes, launch dates and show gallery hours from approved content, then booking a viewing or handing to sales.
- Qualification: capturing budget, timing and preferences into the record before a salesperson calls.
- Construction updates and handover queries: answering routine questions from a current knowledge base, with defects and complaints going straight to people.
Pricing, availability, financing advice and anything contractual should stay with people, or be answered only from live data the agent can read reliably. A wrong price quoted by an agent is a commercial and legal problem. See Customer Agent in practice for how we set handoff rules.
How do you connect the sales system of record?
Most developers run bookings, contracts and payments in a property sales system or ERP, and should keep doing so. The CRM does not replace it. The two need to agree: unit availability flows to the CRM, booking and sale status flows back to the buyer's record, and nobody re-types data between them. We design this as one integration with a clear owner for each field, not a set of manual exports. See our ERP integration approach.
What should a developer measure?
- Enquiry response time, by channel and project.
- Enquiry to viewing, and viewing to booking, by source.
- Cost per booking by marketing source, using real sale data, not form fills.
- Share of WhatsApp conversations captured in the CRM.
- Referrals and repeat purchases from past buyers.
The last two are where most developers have no number at all, and where the long-term value sits.
How do agents and brokers fit?
Many developers sell through external agents and brokers as well as their own team. That creates two risks: the same buyer registered by several parties, and no visibility of what happens after a lead is passed on. Design for it in the CRM. Record the source and the registering party on the buyer record, agree the rules for duplicate registrations up front, and give partners a simple way to update status. Then reporting can show which partners bring buyers who actually book, not just names.
What about data protection?
Property buyers share sensitive details: identity documents, income, financing. Decide what the CRM needs to hold and what should stay in the sales system. HubSpot hosts customer data in the EU, Canada, Australia and the United States (HubSpot), so for most developers in the region the CRM is a cross-border transfer that needs documenting. Our data protection answer covers Malaysia, Singapore and the Philippines.
Where to start
Map the journey from enquiry to handover for one project. Find where buyers leak and where data is re-typed. Bring WhatsApp enquiries into the CRM first, model projects and units, then connect the sales system. Add agents last.
