Proof of Impact
Most GTM problems aren't strategy problems. They're architecture problems. Signals getting lost between systems. Manual processes eating the time that should go to selling. Data that exists but isn't connected to action. I've spent 16 years finding those gaps and building the infrastructure to close them — reducing manual handoffs by 60–85%, cutting event-to-pipeline processing from 7+ days to under 24 hours, and building the signal-to-action systems that let teams scale outcomes without scaling headcount.
2
Revenue System Design
Built end-to-end signal architecture— consolidating intent signals across Marketo, Salesforce, Demandbase, Bombora, event platforms and other third party and first party signals into unified prioritization scoring. At the center is a Conversion Zone methodology: a proprietary framework cross-referencing engagement signals against product ownership and open opportunity data to surface white-space accounts with persona- and product-specific playbooks for SDR activation.
3
Customer Success Referrals
Built a referral lead program from pilot to production — validating manually via Google Form before operationalizing in Salesforce as a formal referral record process triggering leads to sales. When AE follow-up rates fell short, diagnosed the structural problem and moved ownership to an incentivized SDR team to ensure consistent, timely follow-up. A clean example of test-and-learn before you build, and fixing process problems at the root rather than the symptom.
Repeatable Frameworks
Skills Matrix
Repeatable Frameworks
I believe the ROI of GTM systems isn't in the tools — it's in how they're connected. I've built these systems hands-on: writing the requirements, mapping the workflows, sitting in the UAT sessions, and staying until the adoption actually happens. The architecture only matters if the people using it trust it and can act on it.