Who Owns the Truth When the Vendor Leaves
Two public documents describe the same company's marketing over the same twelve months. One is an agency case study. The other is a year-in-review post from the company's chief marketing officer.
The accomplishment lists barely overlap. The agency claims the website, the brand foundation, the search rankings. The executive claims the campaigns, the channels, the new departments, the reporting dashboard. Each list reads as an inventory of what the other party never shipped.
The growth figures differ by a factor of five. Same company, overlapping windows, and two numbers that cannot both describe the same reality. Different start dates. Different measurement instruments. Different definitions of the thing being counted.
Neither document acknowledges that the other author exists.
Neither party is lying. That is the part worth sitting with. Both are selecting: which window, which instrument, which frame. And both are free to select because nothing was ever built that would force one version of the truth. No shared attribution architecture. No revenue-connected reporting. No single system both parties had to publish from. The company at the center of both narratives settled significant revenue that year and still cannot say, in numbers anyone would co-sign, what produced it.
In this article:
Why this happens on purpose
Vendors measuring in their own instruments is rational behavior for vendors. Their tools, their windows, their renewal case. A case study built from a third-party SEO platform will always show the vendor's channel in its best light, because the platform was chosen to do exactly that. None of this requires bad faith. It requires only the absence of anything that would constrain the selection.
Clients rarely notice, because reporting arrives looking like measurement. A monthly deck with charts feels like visibility. It is a channel narrating itself, in an instrument the client neither chose nor controls, denominated in metrics that stop one step short of revenue.
The gap stays invisible until a transition exposes it. A vendor exits. An executive arrives. Someone new asks the first-principles question: what has all of this actually produced? And the honest answer, assembled from the vendor's tool exports and the client's disconnected analytics, is a shrug wearing a dashboard.
What ownership Really means
Dashboard access gets mistaken for ownership. Access is a login the vendor can revoke, into a system the vendor configured, displaying what the vendor decided to display.
Ownership is structural. The attribution architecture lives in your accounts. The tracking, the pipeline data, and the revenue connection sit in systems you control and would keep in any vendor's absence. The logic is documented well enough that your next hire can read it without a handoff call. When a vendor transition happens, and one always happens, the record of what worked does not walk out the door inside someone's head or someone's tool subscription.
The retention implication runs deeper than continuity. Whoever owns the measurement layer owns the renewal decision. When the vendor owns it, every renewal conversation happens inside the vendor's frame, argued from the vendor's numbers. When you own it, vendors compete on contribution to a truth they don't control. The conversation changes shape entirely.
question to ask before signing
Every vendor evaluation eventually reaches the capabilities conversation. Portfolio, process, price. One question belongs ahead of all of it:
What do we own when you leave?
If the answer is a login, a report archive, and goodwill, then the engagement is structured so that the truth about your own business accrues to someone else. Two years later you will be reading their case study about you, next to your own team's version of the same period, wondering why the numbers don't match.
They don't match because no one made them. That was a decision, made by default, at signing.
Who owns the truth when a vendor leaves — FAQs
Why do the numbers differ between a vendor's case study and what the client reports internally?
Usually because neither party built the system that would have forced them to agree. The vendor measures in their own tools, inside their own selected windows, using metrics that favor their channel. The client measures in whatever they have access to. When neither measurement layer is connected to actual revenue, both parties can be technically accurate and functionally incompatible. The discrepancy isn't evidence of dishonesty. It's evidence that a shared attribution architecture was never built.
Is this a vendor problem or a client problem?
It's a structural problem, which means it belongs to whoever is responsible for building the infrastructure. Vendors have rational incentives to measure in their own instruments — their chosen tools, measurement windows, renewal case. Clients rarely push back because reporting that arrives formatted like measurement feels like measurement. The responsibility for building something that constrains both parties sits with whoever owns the engagement architecture. If no one owns it, the vendor fills the vacuum by default.
What's the difference between dashboard access and actual ownership?
Access is a login the vendor can revoke into a system the vendor configured. Ownership means the attribution logic lives in accounts you control, the tracking and revenue connection survive any vendor transition intact, and your next hire can read the documentation without a handoff call. The test is simple: if the vendor left tomorrow, what would you still be able to answer? If the honest answer is "we'd lose the reporting," the vendor owns the measurement layer — which means they own the renewal conversation.
Does this only apply to marketing vendors?
The mechanism is the same anywhere a vendor controls the measurement instrument for work you're paying them to do. Marketing is where it's most visible because the gap between activity metrics and revenue is widest and most exploitable. But the dynamic — vendor selects the frame, client receives the output as truth — appears in any engagement where attribution architecture was never built into the contract.
What should we actually own at the end of an engagement?
The attribution architecture in your accounts. Tracking configured in systems you control. A documented logic of what was measured, how, and why — legible to someone who wasn't in the room when it was built. Revenue-connected reporting that doesn't require the vendor's tool subscription to access. And a clear record of what produced results, denominated in numbers both parties had to publish from the same source. If the engagement doesn't produce that, it produces a case study the vendor writes about you and a shrug wearing a dashboard.
What is the right question to ask before signing with any vendor?
What do we own when you leave? Not "what will we have access to" — access and ownership are different things with different consequences. The answer to that question tells you whether the truth about your own business will accrue to you or to someone else. Everything else in the vendor evaluation, including portfolio, process, and price, is downstream of that.
