About

I studied accounting because it's the language of business — the clearest way to understand how a company actually works. I always intended to use it operationally, not as a reporting function.

I started in public audit, moved to Big 4 inside their asset and wealth management practice, with a stint in PE finance. The credential was valuable. The pattern it surfaced was consistent: the numbers existed. The systems to surface them clearly didn't.

When I left New York and stepped back from Big 4, I started taking on work for friends and family — Excel cleanup, financial modeling, basic automation. Better analytics led to better questions. Better questions pushed the limits of the ERP-export-to-Excel cycle and ate into time and accuracy. That gap pushed me into coding and data engineering.

The opportunity was everywhere. Small businesses needed someone who could be the finance and data team simultaneously. Larger companies had both functions but couldn't get them to talk — finance knew what they needed but couldn't articulate technical requirements; IT had the infrastructure but didn't know what the business needed. I sat in the middle.

That's still where I operate: between the numbers and the systems, turning messy business questions into infrastructure that actually works.