I design infrastructure — the kind where, underneath, there’s real complexity, and on the surface it simply works. I built a system that let two thousand people, spread across a campus, understand one another in six languages at once. The engineering was the straightforward part. The art was making the technology disappear, so the people using it could simply speak, and listen, and be understood. The complexity stayed with me, in the background; what they felt was a clean, human conversation across a language barrier.
I’ve also spent years on the craft side of things. As a photographer, learning how light and color and geometry carry feeling. As a cinematographer and sound designer, learning how a story comes alive — how sound sparks the imagination, how a single frame holds an emotion. And I studied philosophy — the philosophy of mind, how we think and feel and experience the things around us.
So I bring three things to a project that rarely travel together: the technical ability to build it, the creative sensibility to make it feel like something, and the conceptual habit of asking what it means — for the people who’ll use it, for the team that lives inside it, for the business it serves.
Most people bring one. The work worth doing happens where all three meet.
For a long time, building software meant choosing a packaged product and reshaping your business to fit it. You bent your workflow around the tool, made compromises, and called them “how it’s done.”
That’s changing. In 2026, building custom systems is fast, lean, and affordable in a way that would have been unthinkable a few years ago. So now the tool can bend around you — around the way your business already works, around your values, around the direction you’re heading.
That’s the work I do: building systems that reinforce what you’re already trying to build.
When I helped one organization change how their team edited together, the fix itself was straightforward: move the work off a single computer and onto a shared system, so anyone could pick up any part of a project at any time.
What made it matter was human. This team valued collaboration — they wanted people to share the work and build on one another. Their old tools set the terms instead: a project lived on one machine, owned by one person, and handoffs were slow and awkward. Bringing the tools into step with how the team wanted to work changed everything. They produced more, faster, and the work got better, because more people could shape it.
That’s what I pay attention to: how a system makes people feel to use, how it changes the way a team works together, and whether it’s beautiful — whether it lives up to the standard you hold for everything else you make.
A system is something people live inside, every day. It should feel good in there.
I help small and growing businesses build the systems that let them do more with less — automating repetitive work, integrating AI where it earns its place, and shaping custom tools around the way they already work.
Most of the repetitive tasks that eat your week can run on their own now. That gives your team’s time back to the work only they can do: the creative work, the growth, the parts you got into this for.
Imagination is most of the limit now. Building something genuinely worth having still takes someone who can hold all three threads at once — creative, conceptual, and technical.
That’s what I’m for.