Manage and maintain, one account

JD Property OS — property and maintenance software for Dubai

The only platform that knows the lease and the leak.

JD Property OS — Overview
Overview
JD Property OS — Dispatch
Dispatch
JD Property OS — Escalation
Escalation

What it is

Everyone else picks a side: tenancy software treats maintenance as a ticket queue, maintenance software has never heard of a lease. Property OS holds both against one site — and decides. It reads an inbound WhatsApp message, picks the trade, freezes the SLA clock, scores every technician and shows you exactly why it chose that one.

The numbers

Decision engines
7 pure modules
Assertions on the operation
63
JS shipped per screen
< 200 B
Surfaces
Desk · Field · Map · Wall · Portal

What is inside

In more detail

What happens to a job request in the first minute

Triage is the moment the job is created: the message is read, the trade and priority come out of it, and the deadline is frozen against the cover on that site's contract. It is set once and never recalculated later, so everything that follows — the choice of technician, the escalation, the wall display — is measured against the same deadline.

How a technician is chosen, and why the choice is auditable

The dispatch does not just name a winner: it puts every technician in one table with the trade, distance, workload, shift and certification points that produced the total, so a supervisor can argue with the choice. That scoring is one of seven pure decision modules — the same inputs give the same answer every time — and 63 assertions run over the operation, so the behaviour is pinned down rather than described.

Escalation, and the repair-or-replace decision

Escalation is five rules that fire on their own — supervisor, then manager, then everybody — so nobody has to remember to chase. Repair-or-replace weighs the signals on an asset and lets warranty override all of them, so an asset still under warranty is never written off by a score.

Desk, field, map, wall and portal — five surfaces, one system

The desk, the field app, the map, the wall display and the tenant portal are five views of the same records, not five systems kept in step with each other. Each screen ships under 200 bytes of JavaScript, so the field view opens on whatever phone a technician already carries.

Built with

Next.js 15 React 19 TypeScript strict Prisma WhatsApp templates
Open the live demo Talk to us on WhatsApp

It boots in your browser and runs the real logic — no form, no sales call.

Common questions

Is JD Property OS in use by a client?

No — it is a working demo, not a deployed system. It runs the real decision logic in your browser against sample data, so you can triage an inbound message, watch the deadline freeze and see why one technician was chosen, before anyone commissions a build. Nothing on this page is a client result.

Can tenants report faults on WhatsApp?

Yes — the demo starts from an inbound WhatsApp message and triages it into a trade, a priority and a deadline. WhatsApp templates are part of the build, and the reply goes out from the change of state rather than from somebody on the desk remembering to send it.

Do we still need separate tenancy and maintenance software?

No — that split is the problem it is built to remove. Tenancy software treats maintenance as a ticket queue and maintenance software knows nothing about leases. Property OS holds both against the same site, so the lease and the work on the unit sit in one place instead of two.

How do we get a figure for our portfolio?

Scope decides the figure, so it is quoted per project in writing after a call. What moves it is how many departments share one data model, whether field staff need their own app, whether owners get a portal, and how much history has to be migrated.

Related reading

More of the work

JD Software Solutions — a four-person software studio in the United Arab Emirates. We build the system, hand over the code, and stay on to run it.

All of the work