I build when the distance between the work and the available software becomes impossible to ignore.
The starting point is not a feature list. It is the repeated breakdown: information dispersed across systems, ownership left unclear, manual work that keeps multiplying, or a tool that technically functions without fitting the people expected to use it.
Observe the friction→Map the real workflow→Build around reality→Test in context
Selected case studies01—05
01 · Private client project
Practice OS
A two-surface financial operating system—a browser dashboard for deep work and a native iPhone companion for the daily glance—built for billing, deposits, expenses, taxes, closeout, and delegated financial access without clinical data.
A connected system spanning an owner dashboard, Hub app, Crew app, and iOS widget for booking readiness, event-day coordination, finance, and decision support.
A Private Planning Hub for a Girls’ Weekend Getaway
A password-protected group planning app for availability, shared decisions, food preferences, activities, and final RSVPs—built to replace scattered group texts and be reused for future gatherings.