Abdul Rehman

What Technical Debt Looks Like in Property Management Technical debt is a term most business owners hear from their IT teams, but rarely get explained in plain language. In property management, it's the cost of shortcuts taken in your software over time, a custom integration that was never updated, a manual workflow that was supposed to be temporary, or a system that was built quickly to meet a deadline and never revisited. The problem isn't the original decision.

Nobody has ever asked you to upstream your dotfiles. For thirty years that was the deal with every tool we touched: if you didn't like it, you changed it, and the change lived with you. Then the tools started writing the code, and the deal quietly ended. This essay is about why the deal is back on the table. Because the thing that used to make forking expensive — the labour — is exactly what agents just made cheap.

I watched an AI agent send 200 emails to the wrong recipients because I forgot one validation check. The emails were well written. The offers were real. The recipients were just... not our leads. That was early. I learned fast. Every agent I build now has three layers of guardrails before it touches a database or an API. Here's exactly what those layers look like and why they're non-negotiable for production.