Revenue leadership / GTM systems / applied AI
I build the system behind the number.
I lead revenue teams and build the infrastructure they run on—from positioning and pricing to pipeline intelligence, workflow orchestration, and coaching.
Chief Revenue Officer at meez ↗
Operator profile
The operating thesis
The best revenue leaders can move between the boardroom and the workflow—without losing the thread.
Strategy without instrumentation is theater. Automation without judgment is noise. I connect the commercial model, the people running it, and the technical layer that makes better decisions repeatable.
One operator / four layers
Executive altitude. Builder proximity.
Commercial strategy
ICP, positioning, pricing, packaging, channel, and the choices that shape unit economics.
Set direction →02Revenue systems
Forecasting, signal capture, lifecycle design, attribution, and operational feedback loops.
See the work →03Technical build
APIs, enrichment, AI routing, workflow orchestration, CRM architecture, and CLI-native execution.
Open the stack →04Leadership system
Talent density, performance truth, coaching cadence, incentives, and Team One accountability.
Work together →Selected operating chapters
Proof across stages.
Not one playbook repeated five times. A career learning how revenue systems change from formation to scale.
meez
Chief Revenue Officer
One mandate across acquisition, conversion, retention, expansion, and the operating system beneath them.
↗02RepeatMD
VP of Sales
$10M → $25M ARR while growing the sales organization from 4 to 19.
↗03Moxie
VP of Sales
$2.1M → $3.3M MRR in seven months with material gains across lead-to-close and demo-to-close.
↗04Design Pickle
VP Sales & Partnerships
An AI-native outbound motion, pricing transformation, and a rebuilt commercial stack.
↗05Mindbody
Revenue leadership
Nine years across SMB, mid-market, expansion, and vertical leadership as revenue grew past $250M.
↗Builder’s bench
Fluent in the tools. Loyal to the outcome.
The stack changes. The operating principles do not: clean inputs, explicit logic, observable workflows, human judgment at the right moments, and a feedback loop that improves the system.
Explore the stack ↗revenue-system.trace
- 01capture
CRM + call + email + calendar
ready - 02enrich
account + intent + relationship context
ready - 03reason
route task to the right model
active - 04act
forecast / flag / coach / follow up
queued - 05learn
outcome returns to the system
watching