The Lab — agentic-first
I direct the films. I also build the systems that make them.
Most directors hand the operations to someone else. I build them — increasingly with AI agents doing the heavy lifting. This page is the proof: the site you're reading runs on an agentic content pipeline I designed.
I'm a director and DP first — but the work that wins is as much about systems as it is about shots. Casting, scheduling, post pipelines, distribution, the website you're on right now: I treat all of it as something to design, automate, and improve.
“Agentic-first” means I reach for AI agents before I reach for busywork — not as a gimmick, but as leverage. The same instinct that finds the shot in the chaos on set is the one that spots where a repetitive process should become an automated one.
It makes me a faster collaborator, a sharper operator, and a studio that punches above its size. Here's how it shows up.
Principles
Story first, systems second
Automation serves the work, never the other way around. The craft sets the bar; the systems protect it from friction.
Build the boring parts
If a task is repetitive, it's a candidate for an agent. I'd rather spend my attention on the frame and the performance.
Own the pipeline
From pre-pro to publish, I understand — and often build — the tools in the chain, so nothing is a black box on deadline.
Measure, then trust
Every system earns its place with results. If it doesn't make the work better or faster, it's gone.
Experiments
This site's content engine
An agentic content-ops pipeline — audits, SEO, alt-text, structured data — that keeps the portfolio sharp with near-zero manual upkeep.
AI-assisted pre-production
Agent-driven shotlists, look development, and scheduling that compress days of prep into hours.
Automated post & delivery
Pipelines that turn one shoot into platform-native cutdowns and get them where they need to go.
Built with agents
Agentic content-ops spine
Audit + apply tools (lint, links, SEO, alt-text, slug integrity) an AI agent runs against the live CMS — clean content, no busywork.
Structured data, automatically
Every page emits rich schema.org JSON-LD (Person, CreativeWork, BlogPosting, Breadcrumb, FAQ) so search and answer engines understand the work.
CMS-driven everything
Colors, type, copy, and case studies are all editable from one place — the same discipline I bring to a client's operations.
Built fast, built to last
Modern stack, fixture-fallback resilience, and performance budgets — the site never goes down and never goes stale.
Want this kind of thinking on your project?
Director's eye, operator's systems. Let's build something that performs.
Start a project