Case Study 07 · CModel Data, Inc · Stakeholder Alignment
The Problem
The Head of Marketing was reading HubSpot too literally — using it to try to find deal and revenue data, which put HubSpot and Salesforce in direct competition instead of in sync. From her perspective, she had no ROI story. She couldn't prove marketing's impact because the numbers she was looking for weren't showing up where she was looking.
The numbers weren't missing. She was looking in the wrong place. And nobody had drawn the line clearly enough between what each system is actually built to do.
The Reframe
The core insight was a systems framing, not a features problem. HubSpot is the marketing-quality layer — it owns lead generation, lead quality, and marketing attribution. Salesforce is the deal layer — it owns opportunity progression, pipeline management, and revenue. The two systems aren't alternatives to each other. They're sequential. HubSpot hands off to Salesforce. You can't read deal-close data in HubSpot because deals don't live there.
Once that separation was clear, the actual ROI proof for the Head of Marketing came into focus:
The "art of the deal" — everything after the handoff — sits under RevOps, not marketing. The Head of Marketing's job is to prove the quality and volume of what goes into the top of that funnel. That data is fully in HubSpot. She just hadn't been looking at it that way.
What Was Built
Understanding the split is one thing. Having the tooling to operate within it is another. Three builds translated the reframe into something she could actually work with.
Marketing ROI Report. Built a report showing opportunities created by marketing — filtered to accounts she owns via the HubSpot sync, with closed-won logic applied. This gave her a bridge: the handoff point where marketing influence could be traced into Salesforce outcomes without requiring her to live in Salesforce to find it.
Sync Direction Decision. Formalized Salesforce as the source of truth for the sync. This wasn't just a technical config — it was a governance decision. HubSpot changes would no longer silently override deal data in Salesforce. Marketing could operate freely in HubSpot without the risk of corrupting RevOps records downstream.
HubSpot Identity Layer. Built a set of new fields — Record Origin, Original Source, UTM Source, and others — so that anyone opening a HubSpot record can immediately see where it came from and how it entered the system. Form conversions are now traceable end to end. Source attribution is visible on the record, not buried in a report.
"The ROI story was never missing — it was in HubSpot the whole time. The problem was a framing problem. Once the two systems were understood as a stack instead of a competition, the right questions became obvious."
How It Happened
This wasn't resolved in a single meeting or a formal onboarding doc. It built over time — session by session, as her actual questions evolved. Early questions were about why certain numbers weren't showing up. Later questions were about how to read what was there. The reframe wasn't handed to her — it emerged from working through real problems together until the accurate model replaced the inaccurate one.
That's a slower path than a slide deck. It's also the one that sticks.
The Result
The Head of Marketing now operates from an accurate model of what marketing owns versus what RevOps owns. She asks different questions than she did before — more specific, more confident, grounded in the right system for each data point. She has a marketing ROI report she can actually use. She has source attribution on her records. She has a sync she can trust.
The deal-close numbers she was chasing before weren't wrong to want — they just weren't hers to own. Now she's got the numbers that are.
What Was Built