Systems thinker. Storyteller. Builder.
The person behind Agegency — and the thinking that drives every system built.
From timelines to pipelines
The foundation was creative production. Years spent inside After Effects timelines — building motion graphics, compositing, and visual storytelling frame by frame. That work taught a specific way of thinking: every element has dependencies, every sequence has an architecture, and the final output is only as good as the structure underneath it.
That same systems thinking transferred directly into AI infrastructure. The shift wasn't from creative to technical — it was from one kind of systems work to another. Compositing layers in a motion pipeline and orchestrating agents in a multi-step workflow are structurally the same problem: manage dependencies, sequence operations, and produce a coherent output from complex, interconnected parts.
Compounding work, financial independence
The goal is precise: build a body of work that compounds. Every client engagement, every product shipped, every agent deployed should make the next one faster, sharper, and more valuable. Financial independence isn't the end — it's the condition that allows the work to stay honest and the systems to stay interesting.
The creative influences are deliberate. Anime — particularly the long-arc strategic storytelling in series like Death Note and Legend of the Galactic Heroes — isn't entertainment, it's a lens. Multi-move thinking, anticipating counter-strategies, building systems that account for adversarial conditions. The narrative framework maps directly onto decision architecture: define the outcome, model the opposition, sequence the actions, execute with precision.
Future-Back Design as operating mode
Future-Back Design isn't a consulting product bolted on to make engagements sound more structured. It's a personal operating mode — the way every project, product, and decision gets approached whether or not a client is involved. Start with the defined outcome. Map the dependencies between now and that outcome. Sequence the actions by leverage and dependency. Build the system.
The methodology exists because it was built for personal use first. Client work adopted it because it works — not because it was designed to be sold. That distinction matters: the framework is load-bearing, not decorative.
Outcomes before activity
Every action must trace back to a defined outcome. Busy is not a strategy.
Systems over heroics
A good system outlasts any single effort. Build the infrastructure, not just the result.
Clarity is the deliverable
Complexity is often a symptom of unclear thinking. The real work is making things legible.
Ship before perfect
Working beats polished. Deployed and iterable is worth more than planned and unbuilt.
If you're building something and the gap between the vision and the current state feels wider than it should — that's usually an architecture problem. Start with a brief.
OPEN A BRIEF