Buildings Run Shifts Too

A tenant's ceiling starts leaking at eleven at night. They don't open a portal. They send a WhatsApp message to whoever they dealt with last.

That message lands on somebody's personal phone. It is unstructured. It is outside every system the company runs. By morning it is a memory rather than a record — and whether it gets fixed depends entirely on whether one person remembered.

I have spent thirteen years watching the industrial version of exactly this. On a plant floor it's a radio call: keep an eye on number three, it's been behaving strangely all night. Same shape. Real operational knowledge, generated at the worst possible hour, in a form no system can hold. I call it the capture layer — and the argument that plants have a capture problem rather than a data problem turns out not to be about plants at all.

Property management runs shifts. It just doesn't call them that.

Nights, weekends, handovers between staff, an on-call contractor, a portfolio that has to survive somebody's annual leave. Every property company already has somewhere the record lives — a management system, a spreadsheet, a folder of tenancy contracts. What almost none of them have is a structured way to catch the message at the moment a tenant sends it, at the hour they send it, in the app they already use.

01What a building's capture layer has to carry

The same four things a shift handover has to move, translated:

• The request, the moment it's made. Not "a tenant called about the AC sometime yesterday" — a referenced ticket, timestamped, with the unit attached, routed to whoever is actually on call for that tower.
• The half-finished work. Not "the plumber went out" — what was found, what was done, what still isn't fixed, and who is waiting on whom.
• The dates that expire quietly. Tenancy contracts, Tawtheeq and Ejari, insurance, ID expiries. Nothing fails on the day it expires; it fails ninety days later when nobody noticed.
• The judgement. The part that never survives a staff change: that unit's owner wants to be called, not emailed. The lift in Tower B has done this before.

02What I built

A WhatsApp concierge that sits in front of whatever a company already runs — it replaces nothing, and there is nothing for a tenant to install. It answers instantly in English and Arabic, turns each request into a referenced and routed ticket, tracks renewal and document dates, and closes the loop when a contractor marks work done and the tenant confirms it.

03Tested, not promised

I don't think anyone should take an operator's word that software works, so here is what it has actually been put through. A full simulated day across a two-tower, 250-unit portfolio — every request captured, both on-call teams routed correctly. A sustained load run of 1,072 requests with zero errors and no lost or duplicated records. Hostile inputs stored as plain text with the data intact. Three hundred and six automated tests, green on every release.

And the honest limits, because they matter more than the numbers: each client runs on a dedicated number and an isolated database. Document dates are tracked; ID images are not stored. It is PDPL-aligned by design, not certified. Arabic works in text, which is where property conversations actually happen — I make no claim about voice.

04Why an operator built this

Because the failure is the same one I've watched on plant floors for thirteen years, and the fix is the same too. Not a bigger system. Not another portal nobody logs into. Just catching what people already know at the moment they know it, in the place they already are.

The floor has the edge — in a refinery and in a building. The people closest to the problem hold the information nobody ever wrote down. Everything else is a question of whether anyone bothered to catch it.