I build complex products for businesses with unique problems, and untangle the ones that have been quietly falling apart for years.

My background is in design, but the problems I end up solving are usually bigger than how something looks. I've shipped enterprise platforms, built a defense tech product from the ground up, redesigned billing systems, fixed broken DNS configurations, and written parent communication emails for a daycare owner who just needed someone to make it make sense. The brief rarely covers all of it. That's fine with me.

I don't do corporate theater. I'd rather get everyone in a room, actually hear them out, and start connecting the dots between what the developer thinks is happening and what the customer is experiencing. Some of those problems have been sitting there for years, waiting for someone willing to ask the uncomfortable questions, hold space for every perspective, and make a plan that actually moves things forward.

I do my best work when things are genuinely complicated, the path isn't obvious, and nobody quite agrees on what the problem even is. I've learned that's usually not a failure of the team. It's just a hard problem that needs the right kind of attention.

Outside of work I make soap, bind books, and do ceramics. What I like about all three is the same thing I like about a knotted-up business problem: you need a plan before you touch anything, the steps have to happen in the right order, the math has to work, and you had better know what you are doing when something goes wrong. Because it will.