Finance by profession, builder by temperament. I like taking complicated systems — budgets, operations, infrastructure, automation, even family finances — and making them understandable, reliable, and actually useful.
I'm a finance operator with a builder's brain. My day job lives in budgeting, forecasting, and financial analysis, but I get most energized when I can turn messy systems into something clearer, faster, and more useful.
Most of my professional work has lived in healthcare, banking, and government — environments where details matter, process matters, and bad assumptions get expensive fast. That tends to make you practical, analytical, and pretty hard to impress with buzzwords.
Outside of work, I build the tools I wish already existed: financial dashboards, automation workflows, homelab infrastructure, smart-home systems, and scripts that solve annoyingly specific problems well enough to become permanent fixtures.
I'm based in the Indianapolis area, and when I'm not buried in data or infrastructure, I'm usually tinkering with hardware, self-hosted services, or some new AI workflow that seemed like a good idea at the time.
The short version: I like useful systems, honest data, and tools that pull their own weight.
A mix of financial discipline, operational thinking, and technical curiosity — which is a polite way of saying I automate things when they annoy me.
Mostly personal tools, infrastructure, and experiments that started with: there has to be a better way to do this.
The professional through-line: finance, analysis, operations, and making complicated things behave.




The overlap of finance, technology, self-reliance, and hobbies that probably got a little more serious than they needed to.