Growth systems leader with deep performance-media operating expertise.
I stabilize and scale growth systems. Across 15+ years, I have led media investment, CRO, measurement, agency governance, marketing operations, AI-enabled workflows, and executive decision support across PE-backed, enterprise, and global environments.
My current work connects $15M+ in media, CRO, measurement, agency governance, and investment decisions across a 180+ institution education portfolio. Earlier work includes $100M+ global programs, 30+ person teams, and measurable performance rebuilds across financial services, advocacy, education, technology, retail, healthcare, and B2B environments.
- I build the operating layer underneath growth: allocation logic, CRO systems, measurement discipline, QA, agency accountability, and decision cadence.
- Current bounded evidence includes a multi-brand education growth system with $15M+ media scope, 180+ institutions, $500K reallocation, 150+ landing pages, 60+ campaigns, and an observed ~17% to ~28% lead-to-enrollment movement with explicit causal boundaries.
- Historical proof includes ~500% growth in WEX approved applications, 86% YoY growth in Stand Together web-qualified engagements, and $100M+ global programs with 30+ person teams.
The point is not that I can optimize campaigns. The point is that I can design the system through which investment, conversion, measurement, execution, and accountability work together.
Claims and boundaries are governed in the growth-architecture-os claim system and summarized in the proof-points entry point.
| Evaluation question | Start here | What it shows |
|---|---|---|
| Can he lead a complex growth system at current enterprise scale? | Multi-Brand Education Growth System | Current growth-system scope, allocation, CRO, measurement, agency governance, and causal discipline |
| Are the claims themselves governed? | Semantically Governed Claims | Claim authority, SG0-SG3 semantic routing, causal controls, and public-safety boundaries |
| Can he connect marketing metrics to business economics without overstating causality? | Media Metrics to Financial Outcomes | CAC, LTV, payback, incrementality, and explicit limits on causal claims |
| Can he show acquisition-rebuild proof? | WEX App Growth Rebuild | Approved applications grew approximately 500% after the rebuild; application-stage only |
| Can he show operating-performance proof? | FFIA Measurement Model | 86% YoY growth in web-qualified engagements while outperforming benchmarks by 3x; engagement-stage only |
| Can he establish an operating rhythm? | First 90 Days | Diagnosis, stabilization, ownership, and decision cadence |
| Is the AI work governed or just experimental? | AI Operating Model | Source awareness, human review, bounded automation, and reusable workflows |
| Can he safely publish patterns from private systems? | Private-to-Public Release Gate | Privacy scanning, explicit exclusions, allowlisted overlays, and Git-aware drift enforcement |
For role-specific routes through the portfolio, use the Evaluator Paths.
| Repository | Role |
|---|---|
growth-architecture-os |
The operating-system hub: leadership models, diagnostics, governed claims, case studies, playbooks, templates, and decision logic |
marketing-intelligence-agent |
The intelligence layer: source-aware monitoring, signal detection, risk triage, and briefing workflows |
marketing-ops-toolkit |
The utility layer: practical scripts for audits, reporting, campaign health, and recurring operations |
marketing-ops-playbooks |
The method layer: repeatable governance, taxonomy, funnel QA, and performance diagnostics |
brand-context-system |
The context layer: structured inputs, provenance, asset manifests, prompts, and validation |
brand-design-system-starter |
The implementation layer: tokens, foundations, component guidance, CSS variables, and AI-assisted handoff |
private-to-public-release-gate |
The publication-governance layer: privacy-gated generation, allowlisted distribution overlays, and Git-aware drift detection for public derivatives of private systems |
Canonical relationship map: GitHub Ecosystem Map.
The release gate matters because an interconnected portfolio needs a defined publication boundary as well as shared methods. It makes the move from private operating context to public evidence reviewable without implying that every repository is generated from a private source.
- Spend is capital allocation, not just campaign management.
- Growth improves when investment, conversion, measurement, execution, and accountability operate as one system.
- Reporting should end in a decision, an owner, or a clearly named information gap.
- Governance should improve performance, not add ceremony.
- AI should support source-aware judgment and repeatable work, with humans accountable for the result.
This portfolio is built for inspection. Public claims stay within the source evidence; case studies separate observed outcomes from inferred business impact; and the repositories use validation and governance controls where those controls materially improve trust.
Usage and rights: this portfolio is public for professional review, not open-source reuse. See USAGE.md.