Leadership & Operating Approach

How I turn strategy into systems teams can use.

My approach to leading Revenue Operations, Marketing Operations, and data transformation: make the decision clear, give people ownership, and build the technical foundations that make execution repeatable.

From direction to delivery

01

Strategy

Clarify the decision.

02

Systems

Connect the work.

03

Adoption

Make it repeatable.

Business context. Technical depth.
Shared ownership.

The leadership lens

A player-coach across strategy, delivery, and adoption.

I connect executive priorities with the practical work of configuring systems, improving data quality, building reporting, and helping teams adopt new ways of working. My leadership experience spans sales, data and product, development, marketing operations, and cross-functional delivery.

I stay close enough to the implementation to understand the tradeoffs. I also create the documentation, decision rights, and shared operating rhythm that let teams move forward with confidence.

01 / Operating model

How I establish an operating model.

01

Define the decision.

Start with the business question, the person accountable for acting, and the evidence they need. Agree on the meaning of the metric before building the report.

02

Map the handoffs.

Trace how work and data move across teams. Make entry criteria, ownership, response expectations, and escalation paths explicit.

03

Sequence the roadmap.

Prioritize fixes by business impact, dependencies, effort, and operational risk. Deliver a useful first increment, then expand from what the evidence supports.

04

Make adoption part of delivery.

Pair the technical change with training, SOPs, a named owner, and a review cadence. Use exceptions and feedback to improve the process.

02 / Team experience

What teams can expect from me.

Focus

Clear priorities and practical ownership

I translate broad goals into work a team can plan, deliver, and maintain. Responsibilities, dependencies, and acceptance criteria should be visible enough that people know what good execution looks like.

Judgment

Technical judgment with business context

I can move between CRM configuration, integration logic, SQL and Power BI, web experiences, and executive discussions. That range helps me identify where a problem originates and explain the choices in language each team can use.

Continuity

Enablement that outlasts the launch

I build reusable standards: metric definitions, campaign taxonomy, QA checklists, field mappings, SOPs, dashboards, and training. These make knowledge easier to share and reduce dependence on a single person.

03 / Applied leadership

The approach in practice.

MarketForce

Role context
September 2025–present

Connecting strategy and operating infrastructure

Aligning GTM execution, data and reporting, product positioning, web strategy, and revenue visibility. The work connects company direction with the systems and standards needed to carry it out.

BetterLife

Engagement
March–September 2025

Making the marketing-to-sales handoff reliable

A six-month HubSpot–Salesforce engagement combining lifecycle definitions, routing, access logic, data hygiene, reporting, training, and adoption. Shared ownership made the technical integration usable across Marketing and Sales.

KnowFully

Role context
June 2021–June 2024

Enabling a shared service across business units

Leading web strategy, marketing technology, reporting, and conversion optimization across three verticals and 16 education/SaaS business units. Governance and a shared knowledge base supported consistent execution across a varied portfolio.

Let’s connect

Discuss a leadership opportunity.

I’m interested in senior roles where I can build capable teams, connect strategy to execution, and improve the systems behind growth.