One connected ecosystem, not six separate apps
Six role-based apps, one AI Command Centre, one set of shared engines, one database and a defined set of external interfaces. Nothing is a silo: a spoken request from an owner, a material indent from procurement and an executive KPI are all the same record moving through the same ecosystem.
Master Workflow Engine
Entity → classification (AI + rules) → assignment → approval → SLA → execution → evidence → validation → closure → audit. Every process — complaint, task, modification, payment, booking, incident — runs on this one engine.
Owner → Category → Request Engine
From a single request the system derives applicable SOW, technical department, required approvals, estimated cost, required documents, responsible employee, SLA, risk and the execution task. Prevents a pile of disconnected forms.
SLA Engine
Every process carries an SLA. Timers automatically produce reminder → escalation → management alert for complaints, approvals, tasks, modifications, maintenance, security incidents, medical and material requests.
Escalation Engine
Configurable Level 0 (assigned team) → 1 Supervisor → 2 Department Head → 3 Project Manager → 4 Management → 5 Executive/Promoter, triggered by SLA breach, priority, safety, financial impact, delay, repeat complaint, approval delay or risk threshold.
Risk & Prediction Engine
Villa, project and task level risk scores across construction, payment, approval, material, complaint and handover — each with a written explanation. No mysterious AI numbers.
Notification Engine
Push, in-app, email, SMS, WhatsApp and voice for critical events, prioritised P0 emergency → P1 security/major risk → P2 payment/approval/SLA → P3 announcements.
Audit & Evidence Engine
Every material event stores WHO, WHAT, WHEN, WHERE, BEFORE, AFTER, APPROVAL, EVIDENCE, RESULT as immutable history.
Booking Engine
One engine, three layers of rules: internal facilities, external experiences and community events.
How the ecosystem is wired
Read it top to bottom: people speak or tap in Layer 1, AI structures it in Layer 2, the shared engines govern it in Layer 3, departments execute it in Layer 4, everything is recorded in Layer 5, and Layer 6 connects the outside world.
Where people talk to the system — voice-first on mobile, full web consoles for departments and executives.
Turns speech and text into a structured, confirmed instruction — and turns platform data back into plain answers.
Every department reuses the same engines, so behaviour, ageing and escalation are identical everywhere.
Each department owns its modules and its data rows, while sharing the same customer, villa and task objects.
One schema, 34 core entities. A field update is visible to management the moment it is saved.
Everything outside the platform connects through published, versioned interfaces — never point-to-point hacks.
Every interface in the ecosystem, named
These are the only ways data enters or leaves the platform. Each one is versioned, authenticated, logged and testable.
All 21 applications use one authenticated API with role-scoped responses. Realtime channels push task, approval and alert updates instantly.
Audio streams to speech-to-text, returns a transcript with intent, department, priority and suggested ETA for human confirmation.
AI can only propose. The workflow engine validates the proposal against rules and roles before a task is created or closed.
Booking, milestone and maintenance collections with reconciliation callbacks, receipts and ledger posting.
One notification engine, four channels, template-governed. Delivery status is written back to the record.
Invoices, receipts, purchase orders, GRNs and vendor bills exported in the format your finance team already uses.
Visitor passes, ANPR, face/RFID events and alarms arrive as events; the escalation engine treats them like any other task.
Smart meters, STP/DG sensors, EV chargers and villa automation publish readings and receive commands.
SOS events push villa, route and medical context to empanelled hospitals and ambulance partners (future version).
One identity per person, many roles. Every API call is filtered by role claims before data leaves the server.