INMAA

INMAA

منصة العقارات

Property operations software for Saudi operators, built on one core. Phase 1 puts the maintenance an office already runs onto one record: the tenant raises it, the desk assigns it, the technician closes it.

9:41

New request

2 of 3

Tell us what's wrong

AC
Bedroom AC stopped cooling yesterday and is making a loud noise.
Next
1Fahad reports the AC from the QR code in his lobby.
Office web: Requests

Requests

Quick capture
ProblemStatusTechnician
Bathroom extractor fanAssignedImran K.
Kitchen sink blockedNewUnassigned
AC not coolingOn the wayImran K.
Leaking kitchen tapNewUnassigned
No power in bedroomOn siteRavi S.
Door lock stuckIn progressAbdullah M.
Water heater not heatingPausedImran K.
Washing machine drainCompletedRavi S.
2Noura at the desk sees it and assigns Imran.
9:41

#1042

On site

AC not cooling

Arrival recorded at 10:31
Near the building, inside the 9–12 window
One location stamp, taken now
Location is used only for this arrival record. Missing GPS never blocks the job.
Start work
Pause job
3Imran taps Arrive, fixes it, closes with photos.

One platform, many operators

Every operator gets its own team and its own data. Everyone uses the same apps.

INMAAPowered by NawaahOne codebaseOne databaseHosted in Saudi ArabiaInmaa console
WOperator 1Waha Property Co.
Buildings50
Tenants linked1,180
Office admins2
Desk staff3
Technicians12
GOperator 2Gulf Homes
Buildings18
Tenants linked610
Office admins1
Desk staff2
Technicians6
DOperator 3Dhahran Residences
Buildings7
Tenants linked230
Office admins1
Desk staff1
Technicians3

Shared by every operator

Tenant appOne app. Each tenant sees only the unit their own operator linked to their number.
Technician appOne app. Each technician sees only the jobs their own operator assigned.
Office web appOne app. Each operator's admins and desk sign in to their own space.

Hard wall between operators: no data crosses. Enforced in the database and in the API, and tested before go-live.

See how operators share the platform

Phase 1 platforms

Five surfaces on one core and one database. Open any of them for features, restrictions and mockups.

Later layers

Designed for, not built. Each opens only when its evidence gate is met. See the overview.

Rules every platform follows

These hold across every screen. Speed never overrides them.

One record

Every request lives in one append-only history. WhatsApp can stay a way to call; it stops being the database.

Arabic first

Arabic and English, right to left, are acceptance criteria on every screen, not a theme.

Data stays in Saudi Arabia

Database, files and backups are hosted in the Kingdom. SMS and push vendors are listed openly.

Hard walls between operators

One operator can never see another's data. A penetration test proves it before go-live.

No tracking

Location is taken once, when a technician taps Arrive. No maps, no trails, no pings.

No custom forks

Differences between operators are configuration. Every customer runs the same code.

Roadmap

Each stage is gated on evidence. Nothing is built ahead of proof that it's worth building.

Now

Residential maintenance

With visit scheduling. Paid 90-day pilots with three operators in Khobar and Dammam.

Next

Leasing desk or business tenants

Whichever the pilot evidence supports. Capital follows the stronger lane.

Later

Public listings

After REGA licensing and enough live inventory in one city.

Later

Providers and payments

Only when demand, regulation and a licensed payment partner justify it.

What we are not

  • Not a portal fighting Aqar for traffic
  • Not an Ejar replacement or a rent collector
  • Not the employer of technicians
  • Not a custom development shop
  • Not live tracking or fleet maps
  • Not a holder of customer money