about

i spent seven years building enterprise budgeting systems for dhs and dod. onestream implementations — cube structures, calculation engines, congressional justification books, position management. the kind of work where you learn exactly how large organizations make resource decisions. and exactly how slowly.

i left that world because i realized the bottleneck isn't technology. it's methodology. the way we build software — and the way organizations operate — hasn't caught up to what's possible when ai is a first-class participant in the process, not a bolted-on assistant.

now i build systems that run themselves. not prototypes, not demos — production systems where ai handles the volume and the human handles the judgment. the thesis is simple: leverage comes from systems, not hours. one person with the right system beats a team without one.

what i believe

systems over effort. working harder doesn't scale. building a system that compounds does. every hour should make the next hour more productive, not equally productive.

ai changes the kind, not the degree. the interesting question isn't "how do i use ai to code faster." it's "what can i build now that was structurally impossible before." a solo operator running a pipeline that processes thousands of leads per month — that's a different kind of thing.

taste is the moat. ai can generate. ai can evaluate. what it can't do yet is want the right things. knowing what's worth building, what's worth saying, what standard to hold — that's the human layer. everything else is delegation.

compound or die. if today's work doesn't make tomorrow's work easier, something is wrong. every project should feed the next one. every decision should be captured, not forgotten. entropy is the default. compounding is the discipline.

what i'm building

a portfolio of ai-operated systems across land acquisition, personal finance, music production, and government technology. each one proves the methodology in a different domain. each one makes the next one faster to build.

the long game is a practice — not a company, not a product. a way of building that compounds indefinitely. the projects are the proof. the methodology is the thing.