Marketing Operations Built for What's Next.

Cisco Security's marketing and sales teams were working from different playbooks — misaligned on funnel definitions, which made pipeline reporting unreliable and conversion metrics impossible to trust.

Over 18 months, Eric served as the embedded strategic advisor across IT, Marketing, and Sales. He architected a unified funnel stage model enforced through system design rather than process agreements, giving Sales leadership data they could finally act on. He assessed the org structure and MarTech stack, recommended a consolidation strategy to leadership, and advised on the technical architecture to bring a fragmented multi-instance environment down to a single, rationalized stack. When a data compatibility issue surfaced in their attribution setup, he identified the root cause and guided the client to the right solution for their constraints and scale.

The revenue engine never went dark — not once — while three enterprise teams and an entire MarTech stack were restructured around it.

Intuitive Surgical needed a MarTech stack that could move fast without cutting corners — in an environment where regulatory compliance isn't optional.

Eric expanded their MOps infrastructure from a single integration to 10+, each one fully built out, optimized, and purpose-fit for the data requirements of a large-scale medical device enterprise.

The result: a tightly connected, compliance-ready stack that actually gets used — built to support the complexity of the business, not just check a box.

At Verizon's scale, brand consistency in outbound email isn't a nice-to-have — it's non-negotiable.

Eric built a new library of on-brand templates directly inside the MAP and CRM, giving teams a compliant, ready-to-use toolkit that removed the guesswork.

Every email going out now looks like Verizon — no exceptions, no rogue designs, no brand drift.

Dell EMC²'s Syncplicity division ran three critical systems — Marketo, Salesforce, and NetSuite — each owning its own data domain, but none of them connected. The gap meant manual data entry and list exports between systems. Automation wasn't possible — people were the integration layer.

Eric served as the architect for the Marketo side of a three-way sync across all three platforms. He designed how Marketo consumed data from Salesforce and NetSuite to determine what to communicate and when — and how Salesforce would consume Marketo engagement data to support sales and customer support processes in return.

The result: onboarding and renewal sequences that couldn't exist before were built and launched — automated lifecycle communications running on clean, connected data across the full stack.