Agency workspace
Branches, teams, roles, properties, units, agreements, and secure access.
W0-W2 complete · awaiting PM green light
The platform is being built behind the scenes.
Legacy Real Estate is becoming a Kenya-focused property operations platform for agencies, landlords, caretakers, and tenants. The engineering foundation and core rental finance workflows are now in place. The next step is for the PMs to review the completed work and give the green light to proceed. W3 clarification is only needed where a workflow requires a business decision that has not yet been agreed.
Explore the progress First client presentation prototype coming soon
W2 validatedBranch-awareAudited access
Delivery checkpoint
01
Foundation
Scope, API, security, and quality
02
Rental records
Branches, owners, properties, units, tenants
03
Financial workflows
Invoices, payments, arrears, reconciliation
04
Next decision
PM sign-off and W3 planning
What this website is today
This is a presentation homepage, not the finished landlord, caretaker, or tenant portal. Most completed work is backend and infrastructure work that users do not see yet: records, rules, permissions, APIs, payments, audit trails, migrations, tests, and deployment preparation.
The product vision
One connected workspace for property work.
The long-term product brings together agency operations, property records, tenant relationships, bills, payments, maintenance, communication, and owner oversight—while each role sees only what it needs.
Rental finance
Invoices, recurring charges, water billing, payments, credits, deposits, and arrears.
Operational workflows
Maintenance, caretakers, vendors, expenses, approvals, readings, and notifications.
Role-based portals
Focused experiences for landlords, caretakers, tenants, and the agency team.
Completed foundation
W0 and W1 made the system trustworthy.
Before adding finance and operations, the platform needed a reliable vocabulary, secure boundaries, and durable rental records. Those layers are now implemented.
W0Implemented
Scope, architecture, and delivery foundations
The project is structured as a Django and Next.js monorepo with a versioned API contract.
Authentication, MFA foundations, roles, branch-scoped access, immutable audit logging, local PostgreSQL/Redis/MinIO/Mailpit services, quality checks, and the domain dictionary are in place.
W1Implemented
Rental master data and tenancy foundations
The platform can represent the agency, branches, landlords, properties, units, tenants, charges, reservations, and tenancy records.
Records are effective-dated where history matters, access is enforced server-side, move-in workflows are supported, and the property structure is ready for operations and billing.
Wave 2 completed
The financial engine is in place.
Full Django integration suite: 60 tests passed
W2-01 to W2-05Implemented
Invoices, charges, utilities, and monthly billing
Invoices have branch-sequential numbers, immutable issued records, line items, recurring charges, meter-based water charges, and carried balances.
Monthly invoice generation is idempotent, includes configured utilities, validates meter readings, and avoids duplicate billing for the same tenancy and period.
W2-06 to W2-08Implemented
Arrears, payment plans, and payment intake
Arrears ageing, penalties, manager-approved waivers, demand letters, instalment plans, and M-Pesa callback processing are implemented.
Callback payloads are persisted before processing, duplicate transactions are safe to retry, and payment-plan balances, missed instalments, and completion states are tracked.
W2-09 to W2-11Implemented
Allocation, credits, and receipts
Payments allocate transactionally to the oldest outstanding invoices, with overpayments carried as tenant credit.
Unmatched payments are queued for staff review, suggestions remain advisory, matched payments receive immutable receipts, and receipt data is downloadable.
W2-12 to W2-15Implemented
Reconciliation, offline payments, deposits, and reporting
Bank CSV/XLSX imports, manual matching, cash and cheque handling, refundable deposits, top-ups, and daily reconciliation views are available.
Finance actions are authorized and audited. Reports compare received, matched, unmatched, reversed, and allocated totals by date and payment channel.
PostgreSQL-ready migrations
Models, constraints, indexes, and immutable financial records.
Authorization and audit
Finance actions are permissioned, scoped, and traceable.
Reconciliation visibility
Daily totals and channel-level reporting are available.
Delivery and infrastructure
Staging is deliberately simple. Production can scale later.
The accepted architecture decision uses Docker Compose on the prepared single-VPS staging environment. This keeps the current deployment repeatable while the application contracts and workflows stabilize.
Compose for staging
Django, Next.js, PostgreSQL, Redis, MinIO, and Caddy run as a repeatable VM deployment with HTTPS.
K3s and Helm for production
The repository retains Kubernetes infrastructure for the production phase when scale, rollout, isolation, and resilience justify it.
Direct staging deployment
Commit locally and push directly to staging; GitHub Actions builds the archived commit, deploys it, and checks the public health endpoint.
Safe environment boundaries
Staging uses demo data and VM-only secrets; production credentials and live records remain separate.
Architecture decision: Docker Compose on a VM is the right fit for current staging. K3s/Helm remains the intended production direction and can be adopted when production requirements call for multiple nodes, automated rollouts, horizontal scaling, stronger workload isolation, or high availability.
M-Pesa sandbox callback: https://staging.legacyhomes.live/api/v1/payments/mpesa/callback
The next decision
Ready to continue with Wave 3 after PM sign-off.
W3 should connect the trusted backend records to the people and processes that keep properties running. The PMs are being asked to approve the completed W0-W2 foundation and give the green light to proceed. W3 can begin after approval; only unresolved business decisions within specific W3 tasks should pause implementation for clarification.
W3PM approval
Property operations
The next planned wave connects the trusted records to day-to-day property work.
The proposed scope includes maintenance requests, caretaker work queues, quotations, approvals, vendors, expenses, water-reading operations, notifications, and operational dashboards.
W4Next
Role-based portals and polished product UI
Later tasks will turn the platform capabilities into focused experiences for each audience.
The landlord portal will focus on oversight, the caretaker portal on assigned work, and the tenant portal on bills, payments, maintenance requests, notices, and communication.
PM sign-off checkpoint
Review the completed W0-W2 foundation and give the green light to proceed. Any W3-specific business clarification can be handled when that task is reached.
What the first prototype will show
A client-facing view is coming soon.
We are intentionally building the platform behind the scenes first. The first prototype for client presentation will arrive as the workflow and portal tasks mature, giving stakeholders something visual to review without pretending that the finished product is already live.
A clear agency and property operations overview
Early landlord, caretaker, and tenant experience concepts
Representative bills, payment, maintenance, and notification flows
Presentation now, product UI later
Today
Progress dashboard and project story
Next
W3 operational workflow foundations
Later
Interactive role-based portal prototype
Production
Validated product on the appropriate deployment platform