About

I don't like handing off the parts I understand best.

Most of what I've built started the same way: a real need, no team assigned to it yet, and a decision to just build the thing rather than write a brief for someone else to build it. That's how Peace Life, Jarvis, W.I.P Services, Qinty, and Once Upon a Princess all started — five different worlds, the same instinct.

I move between product design, front-end and back-end engineering, brand identity, and marketing because in a small venture those aren't separate jobs, they're separate hours of the same day. Designing the onboarding flow for a wellness app, writing the Firebase auth layer under it, and then building the marketing site that sells it are the same project to me, not three handoffs. I've also run the businesses underneath the products: founded and staffed a construction company, founded a CBD company, and now direct an international nonprofit program on the ground in Peru.

That range means I approach a new problem by asking what it actually needs, not what discipline I'd prefer to reach for. Sometimes the answer is an interaction-design problem. Sometimes it's an outright bug in a Unity build-stripping edge case. Sometimes it's realizing a page is about to publish a claim nobody's verified, and the right move is a placeholder, not a guess dressed up as a fact — that discipline runs through the Qinty and Once Upon a Princess builds especially.

I use AI tools heavily in how I build — for prototyping, for code, for content workflows — the same way I'd use any other tool that gets a real product shipped faster without lowering the bar on what ships. The work on this site is the evidence; the tools behind it are just tools.