Blog — 2026-08-06
By Emad Yahya — web developer & IT systems engineer, Dubai
If you run a brokerage here, the question is rarely which CRM to pick. It is whether a system built for you earns its cost at all. The way to answer that is to write down the jobs such a system would have to do, because in Dubai property the list stays short. It has to collect enquiries from the portals, from your own site and from any campaign you are running, and record which of those produced each one. It has to put a fresh enquiry in front of the agent who owns it, inside WhatsApp, within seconds. It has to follow a deal the way property genuinely moves — viewing, then offer, then negotiation, then close — instead of a straight line. It has to work out commission with an approval step behind it. And it has to total all of that per agent, per source and per campaign, so you can see which spend earns back. If a demo impresses you with anything outside those five jobs, treat it as a bonus rather than a reason to sign.
That framing comes out of operations, not a brochure. I work as an IT systems engineer, and four-plus years of that has been spent inside three Dubai real estate companies. The brokerage CRM running one of those firms is something I wrote from nothing, along with the listing engine, the unit-lookup service and the HR platform sitting next to it. What follows is the reasoning under each of those five jobs, what they cost in time, and the cases where paying for Salesforce or Zoho is the better decision and you should not commission a build at all.
In Dubai, a large share of buyer and tenant enquiries typically arrives through the portals — Bayut and Property Finder. Portal leads are expected to be answered in minutes, not hours: the enquirer has usually messaged several listings at once, and the first agent to respond tends to win the conversation. So the first job of a real estate CRM is not storage. It's routing.
In the CRM I built, every portal enquiry arrives already labelled with where it came from. The system knows this lead came from Bayut, that one from a Property Finder listing, another from a website campaign. Without those labels you cannot answer the only marketing question that matters: which channel is producing closed deals — not just enquiries.
Speed is measured, not assumed. New leads carry SLA timers, and response times show up in reporting. If a lead sat unanswered for an hour, management sees it — by agent, by source, by campaign.
Use the list below as a scorecard while you compare your options — my quote, an agency's, or an off-the-shelf product. Everything on it is something a Dubai brokerage genuinely leans on. Whatever a vendor stacks on top of it is a nice-to-have, and you should not pay much for those:
Dubai agents live in WhatsApp; managers live in reports. A CRM that expects agents to sit inside a dashboard all day gets ignored by the very people it depends on — and a CRM agents ignore produces numbers management cannot trust.
So the traffic runs the other way. Seconds after an enquiry arrives, it is sitting in the WhatsApp thread of whichever agent owns it, carrying enough detail to reply straight away. That agent never leaves the app they were in anyway, and the system keeps score in the background — how fast the reply went out, what stage the deal reached, how it ended. Adoption stops being a training problem, because nobody's habits had to change.
Generic CRM pipelines assume a linear sale. Property doesn't move that way — a deal walks through viewings, offers, negotiations and closings, and it can stall or restart at any of them. The pipeline should use your process's real stages, so a manager reading the board sees the truth of the week rather than a rough translation of it.
Commission tracking is where a custom build earns its keep. Splits and approvals follow your rules — not a template's — and the reporting rolls up per agent, per source and per campaign, so the same system that caught the lead also explains the payout.
Because the records carry money and history, the dull safeguards matter most: what each role is allowed to open, a log of who changed what, and a delete that only takes a record out of view. Records get hidden, never destroyed. In four years inside real estate operations, I have never seen a team regret having an audit trail.
My work sits on both sides of this — I build custom systems, and I also work with Salesforce and Zoho — so read what follows as guidance rather than a pitch. Buy the platform when its wider ecosystem is something you genuinely need wired in and you can absorb the license bill plus an administrator to run it. Build when paying per head starts to sting, when your way of working keeps fighting the templates a platform ships with, or when you need the system speaking directly to your website, to WhatsApp and to whatever internal tools you already run.
Time belongs in the comparison too, and these are my own delivery figures rather than industry averages. Getting capture and a working pipeline live runs 3–5 weeks. Put commissions, the approval chain and the reporting layer on top and the whole thing takes 6–10 weeks. Your existing records are not a separate project either: leads, contacts and the history of past deals come across from spreadsheets or from whichever CRM you are on now, and get checked before the system goes live. Day one is not an empty database.
Ownership is worth being precise about. Nothing is charged per seat on a system built for you: it is one build, shaped around the way you already work, and it belongs to you afterwards. If you are weighing this up, send me your headcount and a description of how your deals move, and I will tell you plainly which way to go — including when the honest answer is to buy rather than build.
They arrive on their own. A portal enquiry lands in the system already labelled with the portal it came from, pings the agent it belongs to on WhatsApp within seconds, and turns up afterwards in the response-time reporting. That flow is what the rest of a real estate CRM hangs off.
Capture plus a working pipeline: 3–5 weeks. Add commissions, approvals and the reporting layer and you are looking at 6–10 weeks in total. Those figures come from a system that has been running a brokerage in Dubai, not from an estimate.
It turns on headcount and on how unusual your process is. Take the platform if its ecosystem is something you really need and the license bill plus an administrator is a cost you can absorb. Take the custom route if fit matters more: a workflow that begins in WhatsApp, a total cost that suits a small or mid-sized team, and nothing recurring that grows with every seat you add. Since I work with both kinds of system, the recommendation you get from me is not tied to either.
No, and that is the point. The enquiry reaches whichever agent owns it inside their WhatsApp, seconds after it arrives, with the SLA clock already counting. They carry on in the app they were in anyway, while the system quietly keeps the record: how quickly they replied, which stage the deal reached, what commission it earned.
It moves with you. Contact records, the leads you are working now and the history of deals already closed are brought over from spreadsheets or from whichever CRM you are on, then checked against the originals before the new system goes live. Nobody has to start on an empty screen.
CRM Development in Dubai — full service page · PSQ HR Platform — an operations system built with the same discipline · Real Estate Website Developer in Dubai — the lead-generating front end