← Index of work// Case study 09 / 32
PropTech · Mobile Platform — 2024

Nomad Homes

A native mobile platform for Dubai realtors and their buyers. Listings, enquiries and automatic buyer matching in one app, with $20M in listings under management.

Category
PropTech · Mobile Platform
Year
2024
Result
$20M in listings managed
Stack
Native Mobile · Property Matching · CRM · Push Notifications
Nomad Homes
$20M
Listings under management
Dubai
Primary market
Two sides
Realtor and buyer
Native
Mobile-first build
Contents
StackNative MobileProperty MatchingCRMPush Notifications
01

Dubai property sales run from memory

A well-priced property in the right part of Dubai draws serious enquiries within hours of listing. The realtor's problem is not demand. It is remembering who asked about what, how keen they were, and whether the buyer who enquired last week on one apartment is the right person to call about the villa that came in this morning.

Nomad Homes was founded by people who had sold property in Dubai and lived with that gap. Leads arrived over WhatsApp, enquiries were tracked in spreadsheets, and matching buyers to new listings happened in the realtor's head. At the volume they were operating, memory failed quietly. Buyers who had enquired on one listing were never shown the one that suited them better, and the lead went cold without anyone noticing.

02

A market that lives on the phone

Dubai's buyers, and particularly the international buyers who make up a significant share of the market, engage almost entirely through their phones. So do the realtors serving them. A CRM designed for a desk was never going to be the operating environment. The platform had to work fully on mobile: between viewings, in the car, halfway through a call. Every core action had to be fast and operable one-handed.

That constraint set the interaction model before any feature was designed. Table-heavy admin screens were out. Card-based interactions took their place: a listing is a card, a buyer is a card, and the actions a realtor takes most often sit within thumb reach on each of them.

03

Two sides, one matching engine

The platform has a realtor-facing CRM and a buyer-facing browsing experience sharing one data model. Realtors add listings with photos, price, location and key attributes. When a buyer enquires, either through the app or via a link the realtor has shared on WhatsApp, they are added to the realtor's contact list with the listing tagged to their profile. That tag is the beginning of a buyer profile the system can reason about.

The matching engine runs in the background. When a new listing is added, it checks existing buyer profiles against the property's attributes: price range, location, type, size. Relevant buyers surface automatically in a recommended contacts list for that listing. A buyer who enquired three weeks ago on a similar property appears there without the realtor searching for them, and a message can be sent directly from that view.

Every interaction is logged in a timeline per contact: enquiries, messages, viewings. Looking at a listing, the realtor sees which buyers have been in contact and at what stage. Looking at a buyer, they see every property that buyer has shown interest in. The two views are the same records seen from either end.

04

Why native over a responsive web app

A mobile-responsive web application was the faster build, and the team weighed it seriously. The decision to go native came down to operating conditions. A web app that loads in a browser and scales down from a desktop layout is functionally slower in the hand, and slower is the difference between replying to an enquiry now and replying after the viewing.

Native also gave the platform device features a web app could not match without additional infrastructure. The camera uploads listing photos on site, so a property can go live while the realtor is still standing in it. Push notifications deliver new enquiries the moment they arrive, which matters in a market where the first realtor to respond usually keeps the conversation. The cost was a longer build. The return was an app realtors keep open.

05

A working day inside the app

A realtor's day starts with the enquiry feed. New buyers arrive tagged to the listing that caught their eye, and the realtor replies from the contact's timeline. Between viewings, a new listing goes up from the phone: photos from the camera, price, location, attributes. By the time the realtor is back in the car, the matching engine has compared it against every buyer profile and produced the recommended contacts list.

The follow-up that used to depend on memory now happens by default. Instead of scrolling back through WhatsApp to remember who wanted a waterfront apartment at that price, the realtor opens the listing, sees the matched buyers, and messages them. Viewings are logged to the timeline as they happen. Nothing needs cross-referencing between a buyer spreadsheet and a listings spreadsheet, because there is no longer either.

06

What the platform manages today

Nomad Homes manages $20M in active listings across its realtor network. Buyer interest is logged automatically and matching runs without anyone asking it to. The gap between a first enquiry and a second contact, where most leads previously went cold, is now filled by the engine surfacing the right buyer at the right moment.

The foundation is a single, consistent record of every buyer's interest across every listing. That is what makes the matching reliable, and it is what lets the network grow without each new realtor rebuilding a private system of spreadsheets and chat threads.

Next project
Construct CRM
[ Construction · CRM Platform ] — $4M in managed project pipeline
Read case study →

Start a project.

// Two spots left this quarter
Send a brief

Book a call or send a brief. The engineers who would build it read everything.

Email
hello@drapelo.com
Reply time
Same working day, always a human.
Proposal
Clear scope and timeline in 48 hours.
Book a 30-min call →
drapelo.
© 2026 — Your technical advantage