The core loop, in four steps.
No agent involvement. No waiting. The prospect leaves your marketing surface with a real matched report in hand. Your broker is notified of every field they answered and every property they saw.
A short question set
Ten to fifteen questions on your landing page: budget band, cash or finance, end-use, location cluster, unit type, target handover, timeline, family size, current residency status. Your questions, your branding, your language — English first, Arabic RTL when ready.
Deterministic matching
The answers pass through your firm's inventory: off-plan projects with milestone payment plans and real handover dates, resale units with current listing terms. Rules match on budget, cluster, unit type, handover window and use-case. Every match carries an audit trace of which rule fired and why.
A branded report in seconds
Five to eight matched properties. Structured payment plans as milestone rows. Handover dates as real dates. Match rationale phrased in the prospect's language. Area price trend context. Delivered as a linked report and a PDF, in your firm's brand, from your firm's domain.
Your broker sees everything
The head of sales and the assigned agent are notified with the full question set, the report contents, and the consent record. The prospect is invited to book an appointment on the broker's calendar; a friendly reminder follows if they do not. The broker can also reach out from their side — with the report in front of them.
What is deterministic and what is generative.
The distinction matters for both audit and quality. We are explicit about both.
Deterministic
Everything that decides a result is a readable rule. Rules can be reviewed, tested, versioned and reproduced. Two prospects with the same answers see the same matches, in the same order, at the same time.
Matching engine
Budget band, cluster, unit type, handover window, use-case fit. No model in the decision path.
Payment plan modelling
Structured milestone rows: percentage, trigger, date. Handovers as real dates. Never free text.
Consent and compliance rules
Cabinet 56/2024 calling window and DNCR suppression, PDPL consent capture. Enforced in the workflow.
Generative
A language model is used only to phrase the match rationale in the prospect's language, from the deterministic result. It never decides which properties appear and never reorders them.
Match rationale
Two to three lines per property, translated into the prospect's chosen language, drawn from the structured match data.
Report cover copy
The personalised salutation and summary paragraph, in your firm's voice and versioned per language.
See the loop with your inventory.
Send us a sample of your projects and a real question set. We will run a prospect through it and show you the report they would receive.
Book a walkthrough