I built Propacc because I did this job for eight years.

I spent eight years in property accounting, most of it in multifamily, working in RealPage and Yardi inside a shared-services team. GL reviews, budget reviews, T12 reviews, accruals, reclasses, month-end close. The full cycle, every month, across a lot of properties.

I was also the person the team came to. I trained eight to ten accountants. I was the technical go-to when something broke or when a process needed fixing. So I saw the close from two sides: as the person doing it, and as the person responsible for everyone else doing it well.

Here’s what I kept running into. The accounting was rarely the hard part. The hard part was the manual review around it. The same checks, every property, every month. Footing the GL. Comparing to budget and the T12. Confirming accruals posted. Looking for the one item coded wrong. I got fast at it, then I got tired of it, and then I started building tools to do it for me.

First it was Excel — advanced formulas, VBA, macros. Then Power Automate and proper workflow automation. Dashboards so the team could see workload and catch problems early. The tools worked. They saved real hours, and the people I built them for noticed. Leadership and the finance executives I supported noticed too.

At some point it stopped being a side project. I realized the thing I’d built for one team was the thing every property accounting team needs: a way to take the repetitive review off people and give them a safe place to work. That’s Propacc.

My brother builds the product with me. He handles the engineering, front to back. I handle the part that makes it actually useful: knowing, from having done it, exactly what a property accountant checks, why, and what going wrong looks like.

“That’s the whole pitch, honestly. Propacc isn’t built by people guessing at your workflow. It’s built by someone who lived it, with an engineer who can make it real.”