Property management software built around how rent moves in Kenya

Start with the monthly rent cycle

Map the work from billing day to reconciliation. The system should show what was invoiced, what arrived, which unit it belongs to, what remains overdue and which receipt was issued. A dashboard is only useful when the underlying trail agrees.

• — Invoices tied to a tenant and unit
• — M-Pesa confirmation handled as a payment event
• — Receipts that preserve the transaction reference
• — Arrears based on the ledger—not memory

Give every role less, but better, access

Owners need portfolio decisions. Managers need today’s exceptions. Tenants need a clear balance and payment route. Maintenance and gate staff need narrow operational tools. Shared passwords and all-access accounts are a warning sign, not a shortcut.

• — Organization and building boundaries
• — Role-specific work queues
• — Audit history for important actions
• — Tenant privacy by default

Check what happens after payment

Collection is the beginning of the record, not the end. Ask how the platform handles callbacks, duplicated confirmations, failed prompts, receipts, reversals and month-end reporting. If the answer is ‘export everything and clean it later’, the operational cost has merely moved.

Evaluate with one real building

Run a controlled first month with one building. Load genuine units, invite a small group of tenants, collect rent, close two maintenance tickets and reconcile the ledger. Measure exceptions and staff time before expanding the rollout.

• — Name a rollout owner
• — Document the old baseline
• — Train by role
• — Review the first month before adding buildings