Sakani
Residential building management platform built for Jordan. One product covers Building Manager, Owner, and Guard with role-aware dashboards, financial tracking with append-only ledgers, maintenance ticketing, guard scheduling, and bilingual AR/EN with full RTL support.
- Industry
- PropTech / Building Management
- Year
- 2026
- Timeline
- 14 weeks
In the product
The challenge
Jordanian residential buildings run on WhatsApp threads, paper ledgers, and unreconciled cash collections. Building Managers chase dues across 40+ units, Owners have no visibility into where their money is going, and Guards work from clipboards. Every stakeholder needs a different view of the same building, in Arabic, on the device they actually use.
We built Sakani as a single platform with three role-aware experiences. Building Manager sees the full financial dashboard with collection rates and dues history. Owner sees a personal credit balance, next payment, and payment history for their unit. Guard sees today's shift tasks. Underneath, an append-only financial ledger with FIFO credit settlement guarantees auditability, while bilingual AR/EN with full RTL ships from day one.
The approach
Role Architecture
Designed a single data model with three role-aware views: Building Manager (full financial control), Owner (personal unit view), Guard (today's shift). One backend, three experiences
Financial Ledger
Built an append-only, idempotent financial ledger with FIFO credit settlement and an automated settlement job. Every dirham is traceable for auditors and owners alike
Maintenance & Guards
Implemented maintenance ticketing with photo attachments and guard task scheduling. Tickets, tasks, and notifications flow into the same role-aware dashboard
Bilingual & Multi-Surface
Shipped Arabic and English with full RTL from day one across web (Next.js), admin (Next.js), and native mobile (React Native via Expo). One source of truth, three surfaces.
What we learned
Role-switching on a single platform was the right call. Building Manager, Owner, and Guard share a building so they share a dataset, only the lens changes
Append-only ledger with auto-settlement removed the entire class of "who paid what when" disputes that plague paper-based building management
Shipping Arabic-first with RTL baked in from day one saved a six-month retrofit later. RTL is an architecture decision, not a CSS layer
The stack
The outcome
role-aware dashboards
Append-only financial ledger
Bilingual AR/EN with RTL
Web + native mobile (iOS/Android)