About
Operator first. Builder second. On purpose.
about / operations → bookkeeping → systems
I spent years in operations and bookkeeping before I built software. That means I have sat inside the mess: the spreadsheet nobody trusts, the follow-up that never happened, the numbers that arrive too late to matter.
Messy workflows become messy numbers. I learned that from the books, not from a landing page. So when I build now, I do not start with the app; I start with the leak.
I build AI-assisted, which means modern speed with operating discipline. The AI does the typing; the operator's judgment decides what is worth building at all.
Alongside client work I build my own products: FollowUpOS, a follow-up operating system, and DealSharp, a real estate analysis tool. They are my proof that the method produces real systems, practical systems over shiny demos.
Working principles
Map before build
No build starts before the workflow and the leak are on paper.
Smallest useful system
One working slice beats a grand plan that never ships.
Boring is a feature
Systems earn their keep by being used daily, not by demoing well.
Hand off with clarity
You keep the artifacts and the documentation. No hostage systems.
Trust is built like software: one working slice at a time.
Start with a scoped sprint and judge the method by its output.