Most real estate CRMs ship with standard sales fields built for generic deals. A Dubai brokerage runs on units, off-plan payment plans, portal leads, commission splits and RERA-form documents. No-code customisation lets you change fields, stages, templates and automations without a developer. This guide covers what to build and how to test it.
Why Dubai brokerages need more than standard sales fields
Generic sales CRMs track a lead through stages such as "new", "contacted" and "qualified". Dubai property deals move through a different sequence: an enquiry from Bayut or Property Finder, a viewing booked at a specific unit, an offer, a Form F, Oqood for off-plan or Ejari for rentals, and a handover. Those stages need fields a standard CRM does not ship: unit reference, project name, developer, RERA permit, commission split and co-broke agent. When teams force these into free-text notes, reporting and automation break. More on the structural mismatch in why generic CRMs fail in the UAE.
The five customisations every brokerage needs
Before you evaluate any platform, make a list of the fields and statuses your team already uses in spreadsheets and WhatsApp. The five that matter most for a Dubai brokerage:
-
Custom fields for property and lead context. Furnishing, view, floor, number of cheques, landlord details, plot size, building amenities. These should be select lists, not free text, so they can filter reports and trigger automation.
-
Pipeline stages that match Dubai's deal flow. Stages such as Viewing booked, Offer submitted, Form F signed, Oqood issued, Handover. You should be able to rename or reorder them without contacting support.
-
Commission splits and fee structures. Record the listing agent, closing agent, split percentages and co-broke share per deal. That data feeds payroll and prevents disputes. See our commission tracking guide for the full detail.
-
Document and email templates with merge fields. Offer letters, Form A and B, payment reminders, and agency agreements should pull client names, unit references and amounts from the record, not from a secretary's memory.
-
Saved views and reports by team, project or portal source. A manager should be able to ask "which off-plan project has the most leads over 30 days old?" and get a list in one click, not an export to Excel.
What can you actually customise without code?
In most real estate CRMs, an admin can add custom fields, change pipeline stages, edit templates, create saved views and set simple automation rules (for example, assign leads from a specific project to a named agent). You cannot usually create a completely new module or integrate with an unsupported system without developer help. Test the admin screen before you buy.
Off-plan fields Dubai needs: payment plans, unit types and developers
Off-plan resale and primary sales add a layer of data that generic CRMs ignore. A unit is not just a product: it belongs to a developer project, has a unit type and size, a list price per square foot, a payment plan with dated milestones, and an Oqood registration. Your CRM should store:
- developer and project master data
- unit reference, floor, view, size and price per square foot
- payment plan milestones with dates and percentages
- availability status (available, reserved, sold)
- Oqood and handover dates
Spreadsheets break at this scale. Our guide on tracking off-plan payment plans lists the fields a system must hold per unit and a worked example. See also WIYO's off-plan CRM page for how project information, buyer requirements and reservation progress fit together.
How to test a CRM's no-code flexibility in a demo
A polished demo shows pre-built dashboards. Ask the vendor to do the following live, with your own field names, during the demo:
| Test | What to ask | Why it matters |
|---|---|---|
| Add a custom field | Create a field called "Cheque count" on the property record | Shows whether fields are truly user-defined or only via support tickets |
| Add a pipeline stage | Add a stage "Offer accepted" between existing stages and drag it | Shows whether your process maps without compromise |
| Build a filtered view | Show all off-plan leads from Project X not contacted in 14 days | Shows whether reporting answers real questions |
| Edit a document template | Insert merge fields for unit reference and agent name into a blank offer letter | Shows whether templates actually merge data |
| Set a simple automation | Assign any new WhatsApp lead from a specific portal campaign to Agent A | Shows whether task routing works without code |
If the vendor cannot do these live in the demo, assume they will take a support ticket later. A CRM that forces you to request every field change from the vendor is not really configurable.
When you need a developer (and when you don't)
No-code customisation covers fields, stages, templates, views and simple rules. You need a developer when:
- you need an integration with a system that has no native connector, such as a bespoke accounting package or an internal ERP
- you need complex logic, such as automatic clawback calculations across multiple contracts and agents
- you are migrating from a legacy system with unusual data structures
- you want a customer-facing portal or external workflows
If you expect to need those, evaluate the platform's API before buying. Our open API buyer's guide covers what to ask. For most day-to-day brokerage operations, no-code is enough.
WIYO's approach: UAE property fields out of the box
Full disclosure: WIYO is the publisher of this guide and sells the CRM described below. We use the same evaluation checklist in this article.
WIYO is a web-based real estate CRM built for Dubai brokerages. Its Complete Real Estate Operating System includes unlimited leads, listings and inventory, all UAE and international portal integrations, UAE off-plan workflows with project information, buyer requirements, availability and reservation progress, one WhatsApp Pro account for the company, AI Co-pilot and AI listing support, complete listing management, and property management. WIYO publishes its price: USD 99 per user per month (minimum USD 80 a month), with 30% off with one-year prepayment (35% for two years); see WIYO pricing.
The point for this article: the UAE property model is already in the product, so brokerages spend less time building fields and more time running viewings. You do not start from a blank sales object and rebuild Dubai's deal flow.
Who this is for
WIYO fits a Dubai brokerage that works across resale and off-plan, receives portal and WhatsApp leads, and wants the UAE property structure already in place. A solo agent who only needs a contact list may be over-served; see our guide for solo agents. A large enterprise already committed to Salesforce with in-house developers may prefer to build the UAE layer themselves, even though that takes longer. If you handle long-term rentals and property management alongside sales, the category distinction matters: a CRM and a property management system do different jobs.
Frequently asked questions
Can I customise a real estate CRM without code?
Yes. Most modern real estate CRMs let an admin add custom fields, change pipeline stages, create saved views and edit document templates from a settings screen. The limit is usually logic: you cannot create entirely new modules or integrate with unsupported systems without code. Always test this in a demo before committing.
What are the most important custom fields for Dubai property?
For resale: unit reference, project and developer, property type, furnishing, RERA permit or Trakheesi number, portal source, list price, and commission split. For off-plan, add payment plan milestones, Oqood registration and handover date. Start with fields tied to your reporting and portal export, not vanity fields.
Does WIYO support off-plan payment plan fields?
Yes. WIYO's off-plan module holds UAE projects with their developers, payment plans and availability, and Deal Maker turns a buyer brief into a ranked shortlist. For the detail, see WIYO's off-plan CRM and the guide on tracking off-plan payment plans.
How long does no-code customisation take?
Field and stage changes take minutes. Building saved views, templates and basic automation takes an afternoon. A full brokerage rollout with data migration, user training and adoption takes days to weeks, depending on data quality and team size. Ask the vendor to show the admin screen in the demo.
When should I choose a developer-built CRM instead?
If you need a proprietary workflow that no-code cannot express, a direct integration to an unsupported portal or ERP, or complex calculations beyond standard formula fields, choose a platform with an open API and in-house developer resource. Evaluate the API before buying using a buyer's guide.
Sources
- Why generic CRMs fail in the UAE — explains the structural mismatch between generic sales pipelines and UAE property workflows.
- Off-plan payment plans tracking — lists the fields a system must hold per unit.
- WIYO's off-plan CRM page — describes WIYO's off-plan project, buyer and reservation workflows.
- Real Estate CRM Dubai — WIYO's Dubai brokerage CRM page.
- WIYO pricing — WIYO's published pricing and plan inclusions.
- Real estate CRM for solo agents — guidance for independent agents choosing a CRM.
Written by
Shaffay Bajwa
Founder & CTO at WIYO · Software engineer, 5 years building in the UAE real estate market.
Want to see WIYO live?
30-minute personalised demo with live data from your existing portals.
