One client. One property. One deal. One system.
DealPilot is being built around connected contacts, properties and deals, not six separate tools. The journey starts with DealCRM's relationship record, while connections between workflows expand during alpha.
Invite-only alpha. The property, valuation and deal examples below illustrate the intended connections; not every module event is added automatically to the contact timeline today.
- Client
- Omar Al-Mansoor
- WhatsApp · budget AED 3.5M cash
- Property
- 2BR Waterfront
- Dubai Marina · indicative CMA ~AED 3,420,000
- Deal
- DL-2026-0008
- Secondary sale · Form F & 10% deposit
From inquiry to audit trail, without copies.
An illustrative connected working day, in the broker's order. Linking some module results to the contact timeline is still in progress.
- Step 01
Contact
An inquiry arrives; the contact is created once
From WhatsApp, a portal or a referral. DealCRM records the contact with its source, budget and preferred language, and the conversation starts on the timeline — not on someone's phone.
- Step 02
Property
The property in question is linked
The unit the client is asking about is attached to the contact, so every later step — valuation, listing, viewing — already knows which property is in play.
- Step 03
DealCRM
DealCRM holds the context
Notes, consent, follow-up dates and NurtureBot-to-broker handoffs stay on the same record — visible to the responsible agent, and to brokerage managers by role.
- Step 04
Specialized workflows
Specialized workflows do their part
PriceIQ provides indicative pricing analysis, ListingAI drafts English and Arabic copy, and NurtureBot prepares follow-ups for broker review. Connecting every result to the contact timeline is still in progress.
- Step 05
Transaction
The deal moves under one number
DealFlow opens the deal — say DL-2026-0008 — tracks milestones and documents, and stays linked to the contact and listing it began with.
- Step 06
Audit trail
The audit trail is already written
ComplianceShield checks and every deal transition land in the audit log as they happen — no reconstructing the story from screenshots and exported chats.
Six modules around the same relationship.
Each module has a specialized role. DealCRM records conversations and notes; pricing analyses and listing packages appear in the activity feed. Automatic contact-timeline connections expand during alpha.
DealCRM
The relationship record for connected workflows
Role in the workflow: Contacts, conversations and notes on one timeline, with links to properties and deals.
Explore DealCRMListingAI
Bilingual listing copy, broker-reviewed
Role in the workflow: English and Arabic portal drafts for the same linked property.
Explore ListingAIPriceIQ
Indicative comparative market analysis
Role in the workflow: A price range from recent closed sales, attached to the property.
Explore PriceIQNurtureBot
Follow-ups drafted, broker-approved
Role in the workflow: Follow-up drafts on the contact timeline; nothing sends without approval.
Explore NurtureBotDealFlow
Deal milestones and documents in one place
Role in the workflow: One deal number, with milestones and documents linked to the contact and listing.
Explore DealFlowComplianceShield
Compliance checks logged as they happen
Role in the workflow: AML and sanctions-screening results on the audit trail of the same deal.
Explore ComplianceShield
Same deal. Six vantage points.
An illustrative walkthrough bringing module outcomes around deal DL-2026-0008. This is not a demonstration of complete automatic integration across all modules today.
- DealCRM
- The contact, the linked listing and the whole timeline — from the 09:14 WhatsApp inquiry to today's viewing note.
- PriceIQ
- An indicative analysis around AED 3,420,000 from 8 recent closed sales, attached to the property.
- ListingAI
- English and Arabic portal copy for the same unit, held for broker review before publishing.
- NurtureBot
- A follow-up draft referencing the price analysis, waiting for a broker to approve or edit — nothing sends on its own.
- DealFlow
- Deal DL-2026-0008 · secondary sale · Form F and 10% deposit milestone · documents in one place.
- ComplianceShield
- AML check and sanctions screening completed and logged against the same deal.
The problem isn't too few tools. It's that they don't share the record.
A fragmented stack
- Client details re-typed into a CRM, a spreadsheet, a chat thread and a compliance form.
- The valuation is a PDF somewhere in WhatsApp.
- Conversation history lives on one agent's phone.
- Compliance files are assembled the week before transfer.
- Nobody is sure which version is current.
DealPilot, connected
- One contact record, with linked listings and deals instead of re-typed identities.
- Pricing analysis is saved, with PriceIQ activity visible in the DealCRM dashboard.
- WhatsApp messages and consent changes on a shared, append-only timeline.
- Compliance checks logged as they happen, against the deal number.
- One deal number — DL-2026-0008 — that everyone refers to.
Built for the Dubai market, in both its languages, with controls you can inspect.
Built for Dubai
AED throughout. DealFlow milestones follow the Dubai secondary-sale path — Form F, deposit, developer NOC, Trustee transfer — and PriceIQ works from recent closed transactions, not asking prices.
Arabic and English, natively
A right-to-left interface, Arabic and English on every screen, and ListingAI drafting bilingual portal copy for broker review. A client's preferred language is a field on their record, not an assumption.
Trust you can inspect
Tenant isolation with Postgres row-level security, roles for owner, admin, manager and agent, personal-data encryption at rest (AES-256) and in transit (TLS), hosted on Google Cloud europe-west1. Timeline and audit-log entries are append-only during normal use.
Start with one deal.
DealPilot is in an invite-only alpha with design-partner brokerages in Dubai. It's AED 0 during alpha; commercial pricing is published separately.