Brokerage KPIs for Dubai owners: the ten numbers to see every week, and why to set your own baseline

The ten numbers a Dubai brokerage owner should see every week

A dashboard is useful only if each number triggers an action. These numbers are KPIs (key performance indicators, the figures you track to judge performance). These are the ten I would put on one page, with the decision each supports.

1. Leads received, by source (Property Finder and Bayut, the two large UAE property portals, enquiries, calls, WhatsApp clicks, walk-ins, referrals, ads). Shows where volume comes from.
2. Median first response time, by agent, by source and by time of day. Shows whether routing works.
3. Leads with no logged attempt after 24 hours. The number that should be zero.
4. Contact rate: share of leads where a real conversation happened.
5. Qualification rate: share of contacted leads that meet your definition of a buyer or tenant.
6. Viewings booked, and show rate.
7. Offers and win rate.
8. Pipeline value by stage, with time in stage.
9. Cost per closed deal by lead source.
10. Deals and commission per agent, read fairly (see below).

Property Finder (a UAE property portal) publishes a partner guide that lists seven similar funnel metrics, cut by source, agent, listing and community. It is the nearest Dubai-specific source I found, and it frames its service levels as targets, not measured industry averages.

Define the terms first: contacted, qualified, viewing, deal

Most arguments about numbers are arguments about definitions. Write them down.

Term	A definition you might choose
Contacted	A two-way conversation happened, not just a message sent
Qualified	Budget, timing and need confirmed and logged
Viewing	Viewing took place, not merely booked
Deal	Choose one: sale contract signed, transferred, or commission received

The last row matters most. If "deal" means signed in one report and transferred in another, your cost per closed deal changes by a lot. Pick the one that matches when money arrives.

Response time: by agent, by source and by hour of day

Speed to lead is the number every vendor leads with. The Property Finder guide suggests a first reply within 5 minutes in business hours with escalation to a backup agent, a second attempt within 2 hours on a different channel, and no lead left in "New" for over 24 hours without a logged attempt. Qobrix, a CRM (customer database) vendor, suggests under 5 minutes in working hours and under an hour outside them. These are vendor targets. Use the median, not the average, since one forgotten lead distorts an average, and look at the hour of day: Dubai leads arrive at night and at weekends, and a quiet 9pm to 8am is where leads go cold. For the how-to, see speed to lead on WhatsApp.

Pipeline by stage, and the leads nobody has touched

Count leads in each stage and how long they have sat there. A lead in "viewing booked" for three weeks is not a pipeline, it is a note. Show the untouched count at the top of the page, with names, so the owner can reassign the same day. A related number is days since last contact; one US vendor suggests flagging at 14 and 30 days, which you can adopt as a starting guess and adjust.

Conversion and cost per closed deal by lead source

Cost per lead flatters portals, because portal leads are plentiful and cheap per enquiry. Cost per closed deal is the fairer number. Method: take the monthly spend attributed to a source (portal subscription and credits, ad spend, agent time if you count it), divide by the deals closed from that source in the period. Use a rolling quarter, because one month can have zero deals. The hard part is attribution: if the source is lost when a lead moves from the portal to WhatsApp, the number is wrong. See lead source attribution and cost per lead in Dubai.

Deals and revenue per agent, read fairly

Do not rank agents on raw deal counts. Compare agents within the same lead source and area, and note the difference between an agent who received 80 portal leads and one who received 8. Small samples are noise: with under about 20 leads, a conversion rate can swing wildly. Use the agent view to decide where coaching helps, not to name winners. My piece on agent performance tracking covers the motivation side.

What published benchmarks say, and why to set your own baseline

I looked for benchmarks you could trust, and I did not find a Dubai one. There is no independent dataset I could find for response time, conversion, deals per agent or lead cost in Dubai. What circulates is this:

• The much-quoted claims that responding within 5 minutes makes you many times more likely to qualify a lead trace, according to the vendors who quote them, to a 2007 MIT and InsideSales study of web leads in general. It was not about real estate or the UAE.
• A 2011 Harvard Business Review article, "The Short Life of Online Sales Leads", concludes that most companies do not respond nearly fast enough. The specific averages quoted from it by others were not visible on the page I could read, so I do not restate them.
• Conversion rates in blog posts range widely depending on how "lead" and "conversion" are defined, and I could not find an independent source.
• Vendor claims about AI chatbots or voice agents improving response times are self-reported.

So treat any figure as direction, not as a target. Your own baseline is better: run four weeks without changing anything, record the ten numbers, then improve one at a time. Your own data comes from your own market, areas and lead mix.

How software and AI build the dashboard from portal, WhatsApp and CRM data

A dashboard is a view onto data you have captured. The tools that work usually do three things. A CRM (customer database) records each lead with source, owner, timestamps and stage. Connectors bring portal enquiries and WhatsApp conversations into that record, so the first-response clock starts when the lead arrives. A reporting layer (inside the CRM, or a separate one) turns the records into the ten numbers. If your CRM's reporting is thin, a custom KPI dashboard can read the same data; I build these on top of a brokerage's existing records. For the data-flow questions, see lead management software.

Be honest about what remains manual. Calls that agents do not log, WhatsApp chats on personal phones, and walk-ins entered late will not appear, so the dashboard understates activity. Define who enters what, and by when.

AI can do the weekly reading for you. Export the week's numbers and ask Claude, an AI assistant: "Here are this week's brokerage numbers and last month's. Which three changed most, which agents have leads with no logged attempt, and what questions should I ask in Monday's meeting? Do not guess causes; list possible ones." It summarises and drafts follow-ups. A person still judges lead quality, decides how much to spend on a portal, and talks to the agent. If you pay for data, make sure your use of client contact data is consistent with the UAE data protection law (Federal Decree-Law 45 of 2021); see client data and the data protection law.

What the weekly 30-minute review looks like

1. Untouched leads (5 minutes): reassign them.
2. Response time by source and hour (5 minutes): any gap at night or on weekends?
3. Funnel by source (10 minutes): where do leads drop?
4. Cost per closed deal by source, monthly (5 minutes): any portal to question?
5. One action per owner, written down (5 minutes).

What to do when a number is bad

• Slow response: fix routing and cover before buying more leads.
• High viewings, low offers: look at qualification and pricing advice.
• Many leads from one portal, no deals: test the quality of those leads and talk to the portal before renewing a bigger package.
• One agent far behind: check lead mix and sample size first, then coach.

How I would approach this

I would not start by building a dashboard. I would define the four terms, make sure leads from every channel land in one record, measure for four weeks, and only then decide whether the CRM's reports are enough or a custom page earns its cost. The numbers are only as good as the capture underneath them.