Post-Sale Revenue Engine Builder.
CS Ops - RevOps - FP&A-Informed Strategy.

I build the operating systems that make CS teams drive revenue — not just retain it.

​

There's a version of CS that leadership tolerates: reactive, intuition-driven, good at relationships but disconnected from the P&L. I've walked into that version more than once. The health scores are manual or missing. The expansion motion is whatever individual CSMs decide to do that week. Renewals are managed in a spreadsheet. Finance doesn't trust the forecast, and CS leadership can't explain why NRR is moving.

​

That's the problem I solve.

​

My approach starts with the operating system — the full engine that CS and RevOps teams actually run on. That means designing the entire customer lifecycle from onboarding through adoption, value realization, expansion, and renewal, then building the infrastructure that makes each stage inspectable and improvable. Health scoring with real predictive logic. Journey and playbook automation in Gainsight or ChurnZero. Expansion inspection routines that create pipeline, not just hope. Renewal processes tied to financial forecasting, not gut feel. And critically: an enablement layer that ensures CSMs actually use what I've built.

​

That last part is what most systems-builders skip. I don't just implement — I train, iterate, and drive adoption until the tooling changes behavior.

​

My differentiator is the FP&A background. Before I was a CS Ops leader, I sat in finance. I understand what the P&L looks like from the CFO's chair, and I know how to translate CS performance into board-level language. When I build a health score or an expansion program, I can connect it directly to the metrics your investors care about. NRR is my north star — everything I build is engineered to move it.

​

The results are specific: NRR improved from 106% to 109% through a structured health score and expansion operating system I designed. $11M in net-new ARR was unlocked through formal expansion and inspection routines. $4M in incremental ARR came from ML-driven customer programs. I've done this across 600+ enterprise customers, in payments, EdTech, and InsurTech — and I've done it both building from zero and transforming functions that had been running broken for years.

​

You should work with me when your CS Ops infrastructure doesn't exist yet, or exists but isn't producing the NRR outcomes your business needs. When you need someone who can sit in a board meeting, talk the numbers, and then go build the system that actually delivers them. When you're tired of hiring people who understand one half of the equation.

I understand both halves.