Systems thinking, in production.
As Business Systems Lead at Valeo Financial Advisors, I shape the technical environment for the firm's internal platform: its architecture, infrastructure, delivery standards, and production operation. I build the shared engineering systems that make good practice easier to repeat across the team.
Production · Technical lead & platform owner
From inherited prototype to production source of truth in about a month — and now the platform behind a 200-person quarterly process.
VAMOS replaced the spreadsheet behind practice composition and compensation. My scope spans its architecture, delivery standards, review, and production operation, with contributors owning bounded features inside the platform.
In development · Platform architect & owner
A safe, self-service deployment boundary for the flood of internal apps AI has made easy to create.
Armada is designed to give AI-built internal apps a safe place to run: company SSO at the gateway, isolated containers, deny-by-default egress, and self-service deployment. Owners will upload an app, choose its audience, and let the platform handle the rest. The architecture makes the responsibility boundary enforceable instead of aspirational.
In production · Technical standards & enablement
A shared engineering harness that gives every repository the same domain context, workflows, review standards, and delivery gates.
VFA-Tools packages repeatable engineering workflows. VFA-Context carries the firm's shared domain and technical knowledge. Versioned together across production repositories, they make good engineering practice part of the environment instead of something each project has to rediscover.
Systems thinking
When tools, data, processes, and people interact, the important behavior happens between the parts. I trace those relationships, plan for second-order effects, and design the system around the outcome — not the components.
Context
I'm a CFP® professional who builds software. I can sit with advisors and compliance, understand the problem in their terms, model it, and ship the system without losing meaning through a translation layer.
Ownership
I own the whole platform surface: applications, data, infrastructure, CI/CD, and the standards the team builds against. The job is making those pieces reinforce each other — and making the team stronger at operating them.
Leverage
I build the shared context, guardrails, and automated review that make AI-assisted engineering work for a team. The tools can do the typing; judgment and ownership stay human.
Technical leadership
VFA-Tools and VFA-Context turn shared domain knowledge, engineering practices, and review expectations into a versioned harness used across repositories. The standard travels with the work instead of depending on someone remembering to explain it.
After hours, systems thinking turns into games, local automation, helmet builds, and increasingly strong opinions about audiobooks.
In development
A browser incremental built around one recursion: more compute → more mind → more reach. Independent systems compound into four endings shaped by choices the game never turns into a visible morality slider.
Try the current build →
Cosplay
Built, finished, painted, and weathered by hand.
Books
Recommendations, mostly sci-fi and fantasy, with the hook and why each one earned a place.
Home Automation
Home Assistant on local hardware, automations that disappear into the background, and a hard rule that the internet going down should not break the lights.
If your problem spans software, operations, data, and people, that's exactly the kind of problem I like solving.
