Real Estate Management System
A complete operating system for a real estate agency: properties, leases, receivables, deposits, documents and tenant risk in one auditable place.
- Status
- In production with a real estate agency in Türkiye
- Interface language
- Turkish
- Category
- Property & lease operations platform
What is built
Twenty modules, in daily use
Portfolio
- Properties — rental and sale tabs, parcel details, listing date, sale fields, soft delete
- Parties — owners, tenants and buyers with type tabs and soft delete
- Leases — status synchronised with property occupancy, mandatory document upload
- Deposits — receipt, return and deduction tracking with a supporting document
Money
- Debt items generated from each lease on save
- Collections recorded against debt items with a mandatory bank receipt
- Partial payment handling with computed remaining balance
- Per-currency summaries on every list and on the dashboard
Control
- Approval queue covering eight record types
- Activity log with period tabs and per-role visibility
- Role separation across manager, staff, owner and tenant
- Account creation restricted to the manager; public registration removed
Insight
- Dashboard: portfolio, current month and overdue card groups, all clickable
- Tenant risk report with distribution ring and detail table
- Risk badge and payment history on the party list
- Spreadsheet export on every list, unaffected by pagination
Access
- Owner portal with per-property expandable detail
- Tenant portal with self-service receipt upload
- Document upload from both portals, subject to approval
- Responsive layout with a mobile navigation drawer
Seeing it
The rest is a conversation
The remaining screens, the data model behind them and the codebase itself are covered in a live walkthrough we run with serious enquiries. It is the fastest way to judge whether this fits what you have in mind — and it is not something a set of screenshots can answer.
Technical sheet
What a technical buyer will want to check
- Framework
- Laravel 13 on PHP 8.5
- Database
- SQLite in the current deployment
- Search layer
- Turkish-aware, falls back automatically on other drivers
- Tenancy
- Single-tenant deployment; isolation layer retained in the codebase
- Interface language
- Turkish, with the localisation layer in place
- Documentation
- 35-page end-user manual, HTML and PDF
- Test data
- Generator command for a full realistic dataset
- Access control
- Route-level role middleware, fail-closed tenant scope
Measured, not claimed
- Query counts on the heaviest screens were measured and reduced — the dashboard from 3,479 queries to 26, the party list from 2,027 to 13.
- List screens paginate at 25 rows while exports still return the full filtered set; summary totals are computed from the whole query, not the visible page.
- Page weight was cut by rendering a single edit panel per screen instead of one per row — the documents screen dropped from 19.7 MB to 178 KB.
- Public registration was removed and the tenant scope made fail-closed after a security review of the whole codebase.