Ask a broker in a 5–30 agent office in Dubai where their leads live, and the honest answer is usually "everywhere". Portal enquiries arrive by email and in the portal's own dashboard. Most of the real conversation happens on WhatsApp, on the agent's personal phone. Viewings are in the agent's calendar, or in their head. The owner sees a spreadsheet at the end of the month, and only if someone remembers to fill it in.

So the office decides it needs a CRM. Then it sits through three demos, each one with a long feature list, and picks the one with the nicest dashboard. Six months later the agents are back on WhatsApp and the CRM has stale data.

The problem is usually not the software. It's that nobody wrote down what the office actually needs before the first demo. This guide gives you the questions to answer first, how the main types of tools compare, and when building your own small CRM makes more sense than buying a big one.

First, write down how a lead actually moves in your office

Before you look at any product, spend an hour with two of your best agents and one admin, and map a single lead from first contact to commission:

  1. Where does it arrive? Property portals, your website form, Instagram, walk-ins, referrals, a developer's launch event. Count roughly how many per week come from each. Most offices find that one or two sources bring most of the volume.
  2. Who gets it, and how fast? Round-robin, by area, by language, by listing owner? Is there a rule that someone must reply within 15 minutes? Who checks?
  3. What happens next? Qualification call, WhatsApp follow-up, viewing, offer, contracts and paperwork, transfer, handover.
  4. Where does it get lost? It's almost always one of three places: no reply on the first day, no follow-up after a viewing, or the agent leaving the company and taking the WhatsApp history with them.

That last point is the one that should drive the decision. In a market with high agent turnover, the real job of a brokerage CRM is to make the client relationship belong to the company, not to the phone in one agent's pocket.

The questions to ask any CRM (including one you build)

Take these into every demo. If the answer is "we can customise that", ask to see it done.

1. Does it handle WhatsApp the way your agents actually use it?

If the CRM can't log WhatsApp conversations, your agents won't use the CRM. There are three levels:

  • Click-to-chat only. The CRM opens WhatsApp with the number filled in. Easy, but nothing is recorded.
  • Manual logging. The agent adds a note after each chat. Works only if notes take seconds.
  • WhatsApp Business API integration through a provider. Messages are sent and stored inside the CRM, and conversations stay with the company if the agent leaves. This costs extra (the provider's fee plus Meta's per-conversation pricing) and needs a verified business number.

Decide which level you need. For a 10-agent office, the third level is usually worth it.

2. Can it take leads from the portals you pay for?

Ask exactly which portals it pulls leads from, whether that happens automatically or by email parsing, and how fast. Also ask whether listings flow the other way: can you manage a listing once and publish it to several portals? If your office lives on one or two portals, that integration matters more than any dashboard.

3. Does it keep the paperwork and permits in one place?

Dubai brokerage has paperwork that a generic sales CRM doesn't know about: the agreements with sellers and buyers, the advertising permit number that must appear on a listing, Emirates ID and passport copies, title deed copies, and the documents for each transaction stage. Check the current requirements with the Dubai Land Department and RERA rather than relying on any vendor's description, then ask whether the CRM has a place for each document and a reminder when one is missing or expiring.

4. Arabic, English, and the client's language

Your clients and some of your agents may prefer Arabic, and others Russian, Hindi or English. Check that the CRM can store names in Arabic correctly, that templates can be written in more than one language, and, if clients will ever see a page (a viewing confirmation, a listing page, a document upload), that it displays right-to-left properly.

5. Who owns the data, and can you get it out?

Ask how you export all contacts, deals and notes, in what format, and whether there's a fee. Ask what happens to your data if you stop paying. A CRM you can't leave is a risk for a small office.

6. What will it cost per agent in year two?

Per-seat pricing looks small in the demo and large when you have 25 agents, an admin and a manager. Add the WhatsApp provider, the portal integration fees and any onboarding fee. Ask for a written quote for your actual team size.

7. Will agents use it on their phones, in a car, between viewings?

Give the mobile app to your most impatient agent for a day. If logging a viewing takes more than 30 seconds, it won't get logged.

The three kinds of tools, compared honestly

Generic CRMs (HubSpot, Zoho CRM, Salesforce, Pipedrive). Mature, good mobile apps, big integration catalogs, and Zoho in particular has a strong presence and partners in the Gulf. The trade-off: they don't know what a listing, a viewing or a portal lead is until someone configures them, and the configuration is where small offices get stuck. Best if you have an admin who enjoys setting things up, or budget for a local implementation partner.

Real-estate CRMs built for the region. They come with listings, portal syndication, viewings and brokerage paperwork already modelled, which saves the most setup time. The trade-offs are usually price per seat, how much you can change, and data export. Best if your process is close to the standard one and you want to be running in a week.

Building your own small CRM. Until recently this meant hiring a developer. Now AI app builders can produce a working CRM from a description, with a real database behind it. Best if your process is unusual (off-plan only, commercial leasing, holiday homes, a mix of brokerage and property management), if you want exactly the screens your agents need and nothing else, or if per-seat pricing doesn't fit your team. The trade-off: you own it, so someone in the office has to look after it, and integrations (portals, WhatsApp API) are extra work you set up yourself.

There's no shame in the first two. If one of them fits your process after the questions above, buy it.

What building your own looks like in Mythex

If you decide to try the third route, here's what a first version looks like in Mythex, an AI app builder: you describe the app in plain language, and it builds it, gives it a Postgres database and file storage, and publishes it. It works fully in Arabic, including right-to-left layouts.

Start with the smallest thing that fixes the leak you found in the mapping exercise. A first prompt might be:

Build a CRM for a 12-agent real estate brokerage in Dubai. Leads have a name, phone, WhatsApp number, source (portal, website, Instagram, referral, walk-in), budget in AED, area, property type, buy or rent, and assigned agent. Stages: New, Contacted, Viewing booked, Viewing done, Offer, Paperwork, Closed won, Lost. Agents see only their own leads; the manager sees all of them. Show leads with no contact in 24 hours in red at the top.

Then add one thing at a time:

Add viewings: each viewing links to a lead and a listing, with date, time and outcome. After a viewing is marked done, create a follow-up task for the next day.

Add a documents section to each deal for the seller and buyer agreements, ID copies and title deed, with a checklist showing what's missing.

Add an Arabic version of every screen with a language switch, right-to-left in Arabic.

Add a WhatsApp button on each lead that opens a chat with a template message in the client's language, and logs the time it was clicked.

That last step is click-to-chat, the first level from question 1. If you later want full WhatsApp Business API logging, that's a separate integration with a provider of your choice, built on top.

Before you show it to the whole office, give it to two agents for a week and watch one number: leads with no contact after 24 hours. If that drops, roll it out. If the agents keep going back to WhatsApp alone, the logging is too slow; cut fields until it isn't.

There's more on this use case on the real estate CRM builder page.

Honest limits of building your own

  • Portal integrations aren't automatic. Pulling portal leads in means using whatever the portal offers (an API, a lead email, a webhook) and testing it. Many offices start by forwarding portal lead emails into the CRM and automate later.
  • WhatsApp API needs a provider and Meta's approval for your business number, and costs per conversation.
  • Someone has to own it. Adding agents, changing stages, fixing a field. Budget an hour a week.
  • Compliance is your responsibility. A CRM stores what you put in it; it doesn't check that your paperwork meets current DLD and RERA rules.
  • Phone apps are web screens. On Pro, Mythex can wrap the app as an Android app or an iPhone app (through TestFlight), but it's your web screens in an app shell, not a fully native app. For logging viewings that's usually fine.

For teams

A brokerage CRM is a team tool: several agents, a manager, an admin, and leads that must stay with the company. On Mythex's Business plan (from $50/month), the office gets a shared workspace, roles, members-only apps that only signed-in colleagues can open, and Google Workspace sign-in with your company domain, so a departing agent loses access the day their account is removed. You can build and test the first version on the Free plan; current prices are on the pricing page.

Whatever you choose, buy or build: map the lead first, find where it gets lost, and pick the tool that fixes that one place. The dashboard can wait.