Context
In asset management, capital planning is a coordination problem as much as an analytical one. Across a large multifamily portfolio, projects, budgets, and reporting have to stay aligned without slowing day-to-day decisions.
When the tools around that work were not keeping up, I built internal software to support how the team planned and tracked capital work. This page stays high level on purpose. It is about the role and the problem, not a product teardown.
Role
As Asset Management Analyst I worked across capital planning, market analytics, and portfolio strategy. Alongside that work I designed and shipped internal tools the team used in production.
The useful lesson was practical: when underwriting and operations share the same facts, capital decisions get clearer. Software is one way to keep those facts in one place.
Approach
The build was full-stack and meant for daily use, not a demo. Beyond that, stack choices, workflow maps, integrations, and interface detail stay private to the employer.
Notes
Building inside an operating role changed how I think about real estate systems. Capital planning is not only a model. It is people, budgets, and time. Good tools make constraints visible earlier.
The same habit shows up in my development feasibility work and in Alare: start from the decision, then build only what supports it.
High-level description of professional work during employment (2025-2026). Not an offering or advice. No proprietary portfolio, tenant, vendor, financial, or system detail is disclosed.