Do you connect to developer broker portals?

Where a developer offers a feed or API to its agencies, yes. Most send sheets and PDFs, which we import with their date. We never scrape a developer’s portal.

What commission rate do you set up?

None by default. Each developer’s rate and trigger are entered from its agreement with you, because they differ by developer, project and launch.

What do the rules require before we market a project?

DLD’s Practice Guide asks brokers to check the project is registered with RERA and has an escrow account, to tell buyers to pay only into escrow, and to have a marketing contract with the developer.

An off-plan desk at dusk: an agent at a large monitor, a tower model and brochures on the desk, cranes over the skyline.

Real estate CRM for brokers · off-plan

Fourteen developers, fourteen price lists. Which one is from this week?

Off-plan commission comes from the developer, on that developer’s terms, months after the booking. Meanwhile stock changes daily and every buyer must be registered with the right developer before another agency does it. We set up Salesforce so each developer, project, price list, buyer registration and commission due is on one record.

Get the written assessment See the whole journey

Salesforce consulting partner since 2010 · MVP Hall of Fame · 200+ agents in production · UAE, India and US desks

The problem

Where off-plan commission leaks.

The process map

One off-plan booking, from the price sheet to the payment.

The same investor books a 1-bed in a launch by Example Developer A.

01Off-plan deskImports the price listThe developer’s sheet, version and date; units marked free, held or sold.On: Salesforce developers
02Buyer’s agentRegisters the buyerRegistered in the developer’s broker portal; the reference, date and expiry are stored.On: Salesforce developers
03BuyerBooks the unitBooking form and payment go to the developer and escrow; the booking is logged on the deal.On: Developer portal
04CRMWatches the triggerThe trigger written in that developer’s agreement, tracked until it is met.On: Salesforce report
05FinanceInvoices the developerOn the day the trigger is met, with the agreement reference.On: Salesforce report
06FinanceRecords receipt or clawbackReceived, or clawed back with the agent’s payout adjusted.On: Salesforce report

Who does what, and on which screen. Your steps and names replace ours during setup.

Get the written assessment

The screens

Developers, stock and money due.

Example developers and figures. Your terms come from your own agreements.

A Salesforce page listing 14 developers with active agreements, 37 projects, 1,286 units and 3 price sheets older than seven days; a table of projects with agreement status, units free, price list version and date, commission terms as per agreement and buyers tagged; and buyer tags confirmed, awaiting the developer or expiring.

A Salesforce report: commission by developer split into earned, due, invoiced and received, and a table of off-plan deals with unit price, commission, the trigger reference from each agency agreement, whether it was met, the invoice and a clawback on a cancelled booking.

Every use case

Every off-plan use case we set up.

Pick the ones you need. Most teams start with three or four.

01Developer agreementsEach developer’s agreement, renewal date, documents and contacts.

02Price list importSheets imported with version and date; a warning when a sheet is older than a week.

03Inventory by projectUnits free, held and sold per project, across every developer.

04Buyer registration with each developerPortal reference, date, expiry and proof, per buyer per developer.

05Registration expiry alertsThe agent and team lead are told before a registration runs out.

06Commission terms as receivedEach developer’s rate and trigger entered from its agreement, never a default.

07Commission receivableEarned, due, invoiced and received by developer.

08ClawbacksA cancelled booking reverses the receivable and adjusts the agent’s payout.

09Launch eventsBuyers invited, attended and booked per launch, with the launch permit noted.

10Project checksRERA registration and escrow account noted on the project before it is marketed.

Before and after

What changes for the team.

Example
Off-plan director at a brokerage selling 20 developers
Today: Agents send last week’s price sheets and lose buyers to agencies that registered them first.
After: Sheets carry their date, buyers are registered from the record and expiries are watched.
Example
Finance head waiting on developer payments
Today: Commission due is in a sheet updated monthly; invoices go out weeks after the trigger.
After: The report shows each trigger met and invoices the same day.

Examples of the work, not client stories.

Around this stage

The next stage, and what plugs in.

Licences come from Salesforce today. We help you pick the plan and work with your Salesforce account team.

FAQ

What teams ask first.

Do you connect to developer broker portals?: Where a developer offers a feed or API to its agencies, yes. Most send sheets and PDFs, which we import with their date. We never scrape a developer’s portal.
What commission rate do you set up?: None by default. Each developer’s rate and trigger are entered from its agreement with you, because they differ by developer, project and launch.
What do the rules require before we market a project?: DLD’s Practice Guide asks brokers to check the project is registered with RERA and has an escrow account, to tell buyers to pay only into escrow, and to have a marketing contract with the developer.

The brief · one email

Tell us how this stage runs today.

The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.