One system of record. Eight ways to work with it.
Each module below would be a separate purchase elsewhere, with an integration project between them. Here they are views onto the same data, sharing the same permissions and posting to the same ledger.
Property & leasing
The record everything else hangs off.
Portfolios, buildings, units, owners, tenants and leases in one hierarchy. A lease carries its own revenue schedule, its Ejari reference, its deposit liability and its renewal window — so occupancy, arrears and expiry exposure are properties of the data, not a report someone assembles.
- Unit-level hierarchy with areas, fit-out state and service-charge apportionment
- Quotation, offer, negotiation, approval and e-signature in one flow
- Revenue schedule created at signature, not at first invoice
- Renewals proposed against market comparables and payment history
- Handover, snagging, meter readings and key custody
- Termination, notice periods and deposit release with the accounting attached
Finance & accounting
A real general ledger, not a reporting layer.
Double-entry from the ground up: chart of accounts, journals, control accounts, period close, year-end. Every other module posts through the same engine, which is why the trial balance has never needed reconciling to a second system. AR, AP, PDCs, VAT returns and owner distributions are sub-ledgers of it, not separate products.
- Receivables with ageing, allocation and control-account integrity
- Payables with banded approvals and enforced segregation of duties
- Post-dated cheque register with banking, clearing and bounce handling
- UAE VAT with return preparation from the ledger, not a spreadsheet
- Owner distributions as a controlled sub-ledger, reconciled to the GL
- Immutable journal lines, soft and hard close, auditable year-end roll
Facilities & maintenance
Every job carries its cost into the ledger.
Assets with service history, PPM schedules that generate their own work orders, SLAs measured rather than aspired to, and vendors with rate cards the invoice is matched against. A completed job posts its labour, parts and vendor cost to the right account and the right property, without anyone re-entering it.
- Asset register with warranty, service history and failure patterns
- Planned preventive maintenance on calendar, runtime or condition triggers
- Reactive requests from tenant, portal, WhatsApp or call, triaged by AI
- SLA clocks with escalation and breach reporting
- Inspections and snagging on mobile, fully offline
- Vendor rate cards, purchase orders and three-way invoice matching
CRM & brokerage
One pipeline, every channel.
Enquiries from portals, WhatsApp, the website and inbound calls land in the same queue, deduplicated against existing contacts and matched to available units. Deals close against the unit record that finance already bills, and commission calculates from the same numbers.
- Lead capture and deduplication across every channel
- Viewing scheduling with agent availability and access arrangements
- Offer, counter-offer and approval trail
- Listing management with portal syndication
- Agent, team and split commission structures
- Commission settlement posted through the ledger
Owner & tenant portals
Self-service that removes work rather than moving it.
Owners see occupancy, income, expenses and statements in real time. Tenants pay rent, raise requests, renew and download invoices. Both see the same records staff see, filtered by permission — there is no separate portal database to fall out of sync.
- Live portfolio performance and downloadable owner statements
- Expense approval thresholds owners set themselves
- Online rent payment with automatic allocation and receipting
- Maintenance requests with photos and live status
- Renewal offers accepted and signed in the portal
- Document vault with every contract, invoice and certificate
Mobile apps
Built for the plant room, not the boardroom.
Native apps for technicians, inspectors, agents and tenants. Full offline capture with conflict-safe sync, because the basement of a tower has never had signal and a job sheet that fails to save is worse than no app at all.
- Offline work orders, checklists, photos and signatures
- Barcode and QR asset identification
- Inspection templates configured by your team
- Agent viewing schedule with route order
- Push notifications with quiet hours honoured
- Biometric login, remote wipe, device-level policy
Documents & AI
The filing cabinet that reads.
Title deeds, contracts, cheques, invoices and Emirates IDs are read on upload — fields extracted, validated against the record and filed. Versioning keeps every amendment, so you can always see what was signed and when.
- 31 document types recognised on upload
- Field extraction with confidence scores and human review queue
- Version history with immutable originals
- Full-text and semantic search across the whole vault
- Retention and disposal policies by document class
- Signed URLs with per-document access control
Analytics
The number on the chart is the number in the accounts.
Portfolio, asset and unit performance computed from the general ledger at read time. No overnight warehouse, no T+1, no quiet divergence between what operations sees and what finance reports.
- NOI, yield and cost per unit by property, class and owner
- Occupancy, churn and renewal rate with cohort views
- Collections, DSO and arrears ageing
- Maintenance cost, SLA attainment and first-time fix
- Budget versus actual against the same ledger
- Scheduled board and owner packs with AI-written commentary
Eight screens that would each be a separate product elsewhere.
Same records, same permissions, same ledger. Switch between them without switching systems.
What an owner sees when they log in: income, occupancy, collections and this month's statement — from the live ledger, not a nightly export.
A single asset, floor by floor. Occupancy, expiries, service-charge recovery and compliance status in one view.
The dispatch board. AI classifies each request by trade and urgency, then assigns the technician who is closest, qualified and free.
Ask a question in a sentence. The answer comes from your own records, with the sources cited and any action held for approval.
Portfolio performance computed from the general ledger, so the number on the chart is the number in the accounts.
Every enquiry from every channel in one pipeline, qualified and matched to available units before an agent opens the file.
Terms to signature to Ejari to revenue schedule. Eight stages, one record, no re-keying between them.
Native apps for technicians, inspectors and agents. Full offline capture, because the plant room has never had signal.
The things that decide whether it survives procurement.
Every item here exists because a real customer's security review, finance policy or auditor asked for it.
Granular permissions
Roles down to the field. A junior accountant can post a receipt and never see a salary line.
Workflow automation
Any event can trigger any action. Build the approval chain your finance policy already describes.
Custom forms
Inspection templates, snagging lists, onboarding checklists — built by your team, not by a change request.
Approval matrices
Banded thresholds with real segregation of duties. The person who raises it cannot be the person who approves it.
Document versioning
Every contract, addendum and drawing keeps its history. You can always see what was signed and when.
Notifications
Email, SMS, WhatsApp and in-app, per user, per event, with quiet hours that are actually respected.
Immutable audit logs
Who did what, from where, to which record, with the before and after value. Append-only.
Open REST API
Every object in the platform is addressable. The UI uses the same API you do.
Webhooks
Subscribe to any event with signed, retried delivery and a replayable log.
AI search
Ask for it in a sentence. Across leases, invoices, work orders, documents and messages at once.
The difference isn't features. It's architecture.
Everyone's feature list looks similar on a slide. What separates them is whether the modules share a database or just an export button.
System of record
- Traditional stack
- One per department, reconciled monthly
- AQARI ONE
- One, shared by every module
Accounting
- Traditional stack
- A separate package, synced nightly
- AQARI ONE
- A native double-entry ledger every module posts to
Data entry
- Traditional stack
- The same lease keyed into three systems
- AQARI ONE
- Entered once, or extracted from the document
AI
- Traditional stack
- A chatbot bolted onto the help centre
- AQARI ONE
- Ten agents with permissioned access to real records
Government filing
- Traditional stack
- Export, log in elsewhere, re-key, upload
- AQARI ONE
- Filed from inside the workflow that created it
Reporting
- Traditional stack
- Overnight warehouse, T+1 at best
- AQARI ONE
- Live, from the ledger, with the entries behind it
Mobile
- Traditional stack
- A cut-down viewer
- AQARI ONE
- Native apps with full offline capture
Extensibility
- Traditional stack
- A change request and a quote
- AQARI ONE
- Open API, webhooks and a workflow builder
Audit
- Traditional stack
- Application logs, if enabled
- AQARI ONE
- Append-only trail on every record, always on
Implementation
- Traditional stack
- Typically 12–18 months, phased by module
- AQARI ONE
- Weeks — the modules were never separate
See it running on your own portfolio.
A 45-minute session with an engineer who knows the domain, not a slide deck. Bring a real lease, a real invoice and your hardest question.
No sales sequence. One engineer, 45 minutes, your data model on screen.