Lead with the business question
I try to start with what leadership needs to decide, then work backward into the data and reporting layer. That keeps the output practical instead of overbuilt.
Home / How I Work
How I Work
How I work: the core principles, values, and operating approach I bring to the role.
This page is the short version of how I work. I start with the business question, build a measurement layer the team can trust, keep the reporting readable, and stay close to the operational handoffs so leaders can make decisions quickly.
Readable reporting
Trusted measurement
Operational handoffs
Testing mindset
Core Principles
The core principles and values I bring into the work.
These are the habits that shape the way I build scorecards, diagnose funnel issues, communicate with stakeholders, and decide what the next deliverable should be.
Keep the reporting readable
I prefer scorecards and views that a marketing executive can scan quickly. If a team cannot explain what changed and what to do next, the reporting is too heavy.
Make the handoffs visible
I do not like stopping at leads. The real story usually lives in the handoffs between marketing, intake, booking, service delivery, and follow-up.
Stay honest about data confidence
I would rather show where attribution or revenue mapping is incomplete than overstate certainty. Trust in the measurement layer matters more than polish.
Build for testing, not just monitoring
The goal is not only to report what happened. It is to create a system the team can use to test faster, rule out weak ideas, and scale the better ones.
Translate across teams
I try to make the same data useful to marketers, leadership, operations, and support teams. That usually means simpler language and clearer definitions.
How that shows up in practice
The common thread is practical decision support: clear metrics, plain-language framing, honest caveats, and a shorter path from reporting to action.
Reporting style
Readable first
One glance should show what changed and what to do next
Decision rhythm
Weekly
Scale, fix, or test instead of passive dashboard review
Data posture
Trustworthy
Cleaner definitions before more complicated analysis
Stakeholder style
Plain language
Executive-friendly without hiding the mechanics
North Star Metrics
The metrics I would expect a performance-minded marketing leader to scan first.
These are the numbers that tend to create the fastest alignment between media performance, funnel economics, and operational throughput.
Media efficiency
ROAS
Useful only if offline conversion handoff is trustworthy.
Lead economics
Cost / lead
Shows what it costs to create qualified demand at the top of the funnel.
Booking economics
Cost / booked customer
The cleaner view of what acquisition really costs when the goal is a booked job.
Demand pressure
Calls / day
A clean upstream read on whether demand generation is actually landing.
Operating North Star
Services booked / day
The most direct bridge between marketing and revenue operations.
Example growth baseline scorecard
A simple weekly view should let a marketing executive see demand volume, cost per funnel goal, booking output, and media efficiency in one glance.
Spend
$22.4K
Media cost for the week
Cost / lead
$86
Top-of-funnel efficiency by qualified inquiry
Calls / day
41
Early read on demand pressure
Cost / booked customer
$214
What it costs to turn demand into a real booking
Services booked / day
17
The clearest operating output
ROAS
4.2x
Readable only with closed-loop revenue mapping
Revenue Impact KPIs
The proof points that show the work is driving revenue, not just reporting.
Marketing executives usually need a second layer beyond dashboard activity: metrics that connect operations to revenue creation, cost discipline, and speed through the funnel.
Pipeline contribution
In a sales-led motion, this shows how much qualified pipeline is sourced or influenced by marketing. In a service business, the closest equivalent is booked revenue contribution from marketing-sourced demand.
CAC efficiency
This is the capital-efficiency view: whether customer acquisition cost is improving while quality and downstream conversion still hold up.
Funnel conversion velocity
This shows how quickly prospects move from first engagement to qualified conversion, booking, or closed revenue. Faster movement usually means the operating system is reducing friction.
Example executive KPI view
This is the kind of summary a CMO or CFO can use to see whether marketing operations is functioning as a growth engine.
Pipeline contribution
46%
Share of qualified pipeline influenced by marketing programs
Booked revenue contribution
$1.8M
Service-business equivalent of pipeline impact
CAC efficiency
-12%
Acquisition cost down while quality holds
CAC ratio
3.7:1
Revenue returned for each unit of acquisition cost
Conversion velocity
5.2 days
Average time from first touch to booked customer
Velocity trend
+18%
Funnel moves faster after workflow and routing fixes
Customer Life Cycle Map
The funnel needs to connect marketing to the real customer journey.
Measurement becomes useful when it spans the handoffs between marketing, lead intake, booking, delivery, follow-up, and referral instead of stopping at the form fill. Each stage should also have a clear cost-to-goal metric so budget decisions stay grounded in funnel reality.
First Touch
Channel, campaign, and offer start the demand path.
SpendCTRLanding CVR
Call / Form
Lead quality and speed-to-response begin to matter.
Calls / dayForm rateCost / lead
Booked Job
This is where many source-quality assumptions get confirmed or challenged.
Book rateShow rateCost / booked customer
Completed Service
The revenue event needs to connect back to the original source.
RevenueROASCompletion rate
Repeat Customer
Lifecycle value grows when follow-up is consistent and visible.
Repeat rateTime to returnLTV
Referral / NPS
The strongest quality signal is a customer who returns and refers.
Referral rateNPSReview rate
Example lifecycle scorecard
A lifecycle view helps show whether a weak result comes from poor media, expensive lead generation, weak intake, or leakage later in the customer journey.
Lead to call
38%
Traffic that becomes a real inquiry
Cost / lead
$86
What it takes to create a qualified inquiry
Call to book
44%
Intake and scheduling strength
Cost / booked customer
$214
The cost of reaching the real conversion goal
Book to complete
82%
Operational follow-through
Repeat or refer
19%
Downstream quality signal
Canonical Stack
The systems and handoffs the scorecards depend on.
A useful operating stack follows the same customer life cycle as the funnel: attract demand, capture intent, route it fast, connect bookings to revenue, and feed those results back into reporting and testing.
Stage-Aligned Stack
One operating view from first touch to referral.
The stack does not need to be complicated. It needs to keep the customer journey, the operational handoff, and the scorecard aligned.
Attract
Google Ads
Meta
Spend, CTR, cost / lead
Measure
GA4
GTM
CallRail
UTMs, touch weights, call attribution
Route
HubSpot
Forms
Email
Response time, lead status, source quality
Book
ServiceTitan
Scheduler
Cost / booked customer, book rate, completion
Report
Power BI
Podium
ROAS, repeat rate, NPS, referral rate
Google Ads
GA4
CallRail
HubSpot
ServiceTitan
Power BI
Podium
Example Stack Scorecard
What a healthy operating layer should show.
The stack itself should be measurable. If tagging, routing, booking sync, and reporting freshness are weak, the funnel scorecards will be weak too.
Tracking coverage
94%
Pages and campaigns tagged correctly
Call attribution
89%
Calls matched to channel and campaign
Booking sync
91%
Booked jobs tied back to source data
Dashboard freshness
Daily
Decision view refreshed on a useful rhythm
Taxonomy adoption
100%
Shared naming across campaigns and sources
Test velocity
3 / month
Enough clean data to run and judge tests
Attribution
Attribution should help decisions, not just sound sophisticated.
Attribution is useful when it clarifies which sources are driving booked work, where tracking breaks before revenue is recognized, and how multiple touches should be weighted so each meaningful campaign interaction gets a fair share of value.
| Approach | What it helps with | Where it breaks |
|---|---|---|
| First-touch | Good for understanding what started demand. | Overstates channels that introduce the lead but do not help close it. |
| Last-touch | Useful when leadership wants a quick read on what appears to be converting. | Can over-credit branded search and direct traffic if offline conversion data is weak. |
| Weighted multi-touch | Assigns partial value across the major touches so the campaigns that introduce, assist, and close demand each receive proportional credit. | Still depends on clean UTMs, call tracking, and booked-job handoff, or the weights become guesswork. |
| Operational reality check | Compare attribution with call-center speed, booking rate, and downstream completion. | If that comparison is missing, ROAS and CAC can look more certain than they really are. |
Example attribution view
A practical attribution board compares weighted touch value with booked-job reality so budget decisions do not lean on first-click or last-click thinking alone.
Intro touch weight
25%
Value assigned to the campaign that started demand
Assist touch weight
35%
Credit for the campaign that moved the prospect closer
Close touch weight
40%
Value assigned to the campaign that drove the booking
Campaign value
$31K
Weighted revenue assigned back to the journey
Offline match rate
87%
How much booked revenue is tied back to source
Action signal
Scale search
When weighted value and booked outcomes agree
What I Know How To Build
The repeated capabilities behind the portfolio.
These are the kinds of operating deliverables that keep showing up across the strongest work in the portfolio.
Tracking and taxonomy cleanup
UTMs, campaign names, stage definitions, and source mapping that make cross-brand or cross-channel reporting trustworthy enough to use.
Closed-loop reporting
Bringing spend, leads, calls, booked jobs, and revenue into one decision surface that helps a CMO know what to scale, fix, or test.
Lead and source quality visibility
Scoring and segmentation that make acquisition reporting more useful than raw volume by itself.
Attribution that stays practical
Enough attribution to guide decisions, plus the discipline to point out where the tracking still is not complete.
Call-center and booking leakage diagnosis
Showing where a channel looks weak because the downstream handoff is weak, not because the media itself is failing.
Growth testing support
Once the measurement layer is stable, build the weekly rhythm that helps the team stop weak ideas fast and scale what is working.
Example operating deliverables
The goal is not more dashboards. It is a short list of tools the team can actually use to make better weekly decisions.
Friday brief
Scale / Fix / Test
Simple actions tied to ROAS and booked-job rate
Source-quality board
Lead to revenue
Which channels create real downstream value
Leakage view
Call to book gap
Shows where the handoff is failing
Test tracker
Win / Lose / Learn
Keeps experiments tied to measurable outcomes
Best supporting pages
If you want to see these fundamentals in action, the strongest next reads are the Marketing AI page, the 120 Day Plan IHS, and the examples where the measurement layer drove real decisions.