// Work
Where I operate.
My work runs across three operating contexts and a rotating set of advisory engagements. The common thread is a single set of questions. How does media infrastructure change when software and machines become collaborators? What do the teams building inside that change need from the people advising them?
This page is the map.
// Operating Contexts
Founded · 2024
Alchemy Creations
My consultancy and venture studio, founded with Joseph Hopkins. We work with media and AI companies navigating the intersection of creative production and technical transformation. The brief is strategic advisory, but we operate more like part of the team than a vendor, embedded in the work for the duration of a problem rather than producing artifacts and stepping back.
Interim CTO
Secret Level
I serve as interim CTO at an AI-native production studio building generative storytelling infrastructure. The work sits at the boundary of creative production and machine intelligence, helping a team that's both shipping product and shaping what production looks like when machines become collaborators. External details are intentionally minimal.
Venture Partner
Hallstone Ventures
A seed-stage fund focused on AI and media technology, founded by Seth Hallen. My work there is sourcing and evaluating investments, helping portfolio companies on technical and strategic questions, and contributing to the fund's thesis on where media infrastructure is headed over the next decade.
Hallstone Ventures →
// Selected Collaborations
// How I Work
01 /
I show up across the layers.
Most advisors stay at one layer. I write, I advise, I sometimes operate inside companies. The problems in media right now want all three. Infrastructure teams often don't know what editorial actually needs. Creators often don't know what the platforms can do. I try to sit between those conversations.
02 /
I think in systems, not features.
Most product decisions in media get framed as "should we add this feature." The more useful question is usually what system this feature is part of, and what that system wants to become. I bring that lens to almost every engagement.
03 /
I'm useful where engineering meets context.
I have enough technical depth to read architecture and write code when I need to. I have enough media context to know what's actually at stake. The valuable spot is in the overlap, especially when the two sides aren't used to talking to each other.
04 /
I work inside the system.
Advice ages fast once it leaves the room. Systems keep moving, and the interesting problems only show up when you sit close to the feedback loops. So I stay embedded: in the architecture reviews, in the build decisions, in the tradeoffs while they're still live. The work gets better when everyone at the table is solving the same problem, and that's the table I want to be at.
// Engage
Looking to engage on something specific?
If you're thinking through media infrastructure, AI production workflows, or where storytelling systems are headed and want a thinking partner, that's the conversation. Email is the front door. We'll figure out from there whether advisory, speaking, or a longer engagement makes sense.