Skip to main content

Platform leadership in practice.

The platform, and the systems around it.

At Valeo Financial Advisors, my scope spans the technical environment around the internal platform: applications, data, infrastructure, CI/CD, and the shared engineering harness used across repositories. These are the systems through which I make architecture, delivery, review, and production responsibility repeatable; details are abstracted for a public page.

Flagship platform

Production · Technical lead & platform owner

VAMOS — the firm's internal advisor platform

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.

Impact
Replaced a spreadsheet behind a roughly 200-person quarterly process
Delivery
Inherited prototype to production in about one month
Leadership
Architecture, delivery standards, review, and production accountability
  • React
  • TypeScript
  • FastAPI
  • PostgreSQL
  • Azure
Read the writeup →

Platform ownership

In development · Platform architect & owner

Armada — a deployment platform for AI-built apps

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.

Purpose
Self-service path for internally built applications
Boundary
Gateway SSO, isolated containers, and deny-by-default egress
Governance
Ownership, access, infrastructure, and support boundaries defined at the platform level
  • Python
  • FastAPI
  • React
  • PostgreSQL
  • Azure
Read the writeup →

Implementation lead → platform owner

Salesforce — implementation lead & platform owner

I led Valeo's original Salesforce implementation and still own it as the firm's system of record, turning executive priorities into platform work.

Delivery
Led requirements, data model, configuration, development, and the Phase 1 rollout
Current role
Platform owner and roadmap partner to senior leadership
  • Salesforce
  • Flow
  • SOQL

How the team builds

Production · Engineering systems designer

CARL — an autonomous software-development pipeline

CARL drives agents from ticket to pull request through isolated workspaces, model routing, and human approval gates. The full autonomy path did not outperform an engineer directing good tools, but its Review Layer now gives every team pull request a consistent automated review.

Current use
Reviews every VAMOS pull request into dev
Finding
Caught a browser-only timezone defect after CI was green
Ownership
Designed and built the pipeline and review layer

Review evidence

VAMOS PR #283

“Adoption chart month labels are off-by-one in Eastern time”
The underlying data was correct, but every chart label was wrong for Eastern-time users. CI stayed green because its runner used UTC.

Fixed in the follow-up commit, with regression tests added.

Real finding from a VAMOS pull request, lightly edited for public display.

  • Python
  • Claude Agent SDK
  • GitHub API
  • systemd
Read the writeup →

In production · Technical standards & enablement

VFA-Tools & VFA-Context — a portable agent harness

A versioned set of skills, shared domain context, and hooks that gives every repository the same engineering standards and blocks PR creation until review passes.

Distribution
Versioned once and embedded into production repositories
Enforcement
PR creation requires review on the exact submitted commit
Layers
Shared context, workflow skills, and deterministic hooks

Embedded engineering harness 

.claude/
├── hooks/
│   ├── pr-guard.mjs
│   └── submodule-integrity.mjs
├── rules/
│   ├── backend-python.md
│   └── security-gates.md
└── skills/ → VFA-Tools
    ├── VFA-Context/
    ├── vfa-pre-pr/
    ├── vfa-review-code/
    └── vfa-review-data-model/
  1. Session start verifies that the versioned tools and context are present.
  2. Editing loads the rules and domain context relevant to the work.
  3. A pull request into dev requires a passing review on the exact commits being submitted.
  4. Any later commit invalidates that pass and requires another review.
  • Claude Code skills
  • Markdown
  • git submodules
  • Conventional Commits

Operational leverage

Designer & builder

Operational Automation — eliminating the firm's busywork

A set of unattended workflows that remove recurring document and data chores from the firm's operating rhythm.

Outcome
Turns recurring document work into unattended workflows
Scope
Secure file intake, PDF splitting, and Salesforce automation
Design goal
Runs without ongoing operator intervention
  • Python
  • systemd
  • Salesforce Flow