Property Management Platform

Category: Real Estate
Platform: Web App
Year: 2026; Built
Developer: Jake
Stat: 1,000+; users in production
Stat: 680+; API routes
Stat: 130+; data models

Preview

Web · Desktop & Mobile

Client project under NDA. Real screens, blurred to keep the client's name and data private; the last one shows how it's built.

The operations platform of a property leasing and management company, in production with thousands of users. A public listings site, self-service portals for tenants, unit owners and referral agents, and a staff dashboard that runs leasing, payments, owners, renovations and short-term rentals.

What's Included

Public listings with filters, inquiries and viewing requests
Tenant portal: rent, payments, utilities, concerns and documents
Unit owner portal: units, charges, expenses and statements
Referral agent portal: leads, stats and earnings
Staff dashboard with seven roles and a custom role builder
CRM board with site visits and follow-ups
Contracts, payments, collections and printable receipts
Renovation projects and tasks with photo review
Short-term rental units with owner statements in PDF
Team chat, email center and audit logs

The Problem

A property company leases units, sells them and manages them for their owners, so one unit touches staff, tenants, owners and agents. It needed one system where each of them sees their own side of the same records, and every peso can be traced.

By the Numbers

1,000+
users in production
680+
API routes
130+
data models
25
API modules
380+
API test files

Under the Hood

Highlight 01
Chat from 47 seconds to about one
I built the team chat on Laravel Reverb. Broadcasts first shared a queue with other jobs; giving them their own queue and worker cut delivery from 47 seconds to about one.
Highlight 02
A ledger for every peso
Receipts are a ledger with one row per money movement, so a payment, an advance, a deposit or a reversal can always be traced. Reversals need their own permission.
Highlight 03
Modules that own their domain
The API is split into 25 Laravel modules. I wrote the most code in properties, tenants and contracts, payments, owners, CRM and renovation projects.
Highlight 04
Owners see checked numbers
Unit owners get daily and monthly report emails, and a charge needs a second check before it reaches an owner’s bill.
Highlight 05
Tests in CI
I wrote 380 of the 403 API test files and added them to CI. By then the suite ran 926 tests.
Highlight 06
Releases that switch at once
Each deploy lands in a new release folder over SSH and goes live by swapping a symlink. I added the queue, broadcast, schedule and WebSocket workers under PM2 and made the pipeline survive flaky SSH.

Information