The CTMO Quarterly Volume 1 · Issue 2 · Q2 2026

The
Translator
Problem

Your CMO and CTO are not the problem. The gap between them is structural, and it has been there since the day you hired them both.

John Kirker, CTMO April 1, 2026 ctmo.com
Read
In This Issue
Section 01 Editor's Letter

The Gap Is in the Org Chart. Not in the People.

JK
John Kirker
CTMO · ctmo.com

There is a meeting that happens at almost every $10M to $100M company, at least quarterly, sometimes monthly. Your CMO says the pipeline is thin because the product team hasn't delivered the integrations they promised. Your CTO says the campaigns are underperforming because marketing keeps changing the brief. Both are right. Neither is solving the actual problem.

What you are watching is not a communication failure. It is a structural failure. The distinction matters more than most CEOs realize: communication failures respond to better meetings, clearer briefs, the occasional offsite. Structural failures respond to none of those things. They recur, quarter after quarter, because the organizational chart has a seam that no one owns.

I coined the term "Chief Technology Marketing Officer" in 1999, not because I had a tidy framework for it, but because I kept encountering the same gap in every company I worked with. Marketing had a goal. Technology had a stack. The space between those two things had no owner. What I was doing, across client after client, was sitting at that seam. Not coordinating between the two sides. Owning the gap.

"Communication doesn't fix a structural problem. It just makes the structural problem easier to describe."
John Kirker · The CTMO Quarterly · Q2 2026

One of my longest engagements began because someone trusted me with a problem nobody had been able to name. A home improvement company. $17 million in revenue. $160,000 a month in advertising. Zero tracking. The founders were not fighting. They were friendly. They met regularly. And the company was bleeding money out of a gap nobody could see.

I did not fix their communication. I closed the gap. Fourteen years later, they sold to a major national manufacturer in their category at close to $100 million.

By the end of this issue you will have a named framework for diagnosing whether you have this problem. Most companies at your stage do. You will also have one question to take into your next leadership meeting. That question will produce at least three different answers from your team. The divergence is the gap, visible in real time.

The question you should be sitting with as you read: If the misalignment between your marketing and technology teams is structural and not personal, what does that imply about every personnel decision you have made to try to fix it?

Section 02 Featured Analysis

The Translator Problem: Why the Gap Persists Regardless of Who You Hire

The Belief Worth Challenging

The belief running through most $10M to $100M companies right now sounds like this: "We need better communication between our marketing and technology teams."

It is a reasonable belief. It points at a real symptom. And it has sent hundreds of capable CEOs down a path that never resolves the problem. The evidence is visible in how companies respond when the gap surfaces: standing syncs, shared Slack channels, a Head of Marketing Operations hired to sit between the two functions. When none of that works, someone gets promoted or replaced.

Here is what this pattern reveals: the problem is not communication. It is architecture. Marketing and technology do not fail to align because they do not talk. They fail to align because they are optimizing for different clocks, different success metrics, and different risk tolerances. Communication doesn't change any of those things.

The reframe: Your CMO and CTO are doing exactly what good CMOs and CTOs do. That is precisely why the gap exists. Two excellent people, each optimizing correctly for their own function, create a gap at the intersection. It is an org chart problem, not a people problem.

The Translation Layer

The gap has a name: the Translation Layer. It is the structural seam between marketing's operational reality and technology's operational reality where revenue decisions live and no function has ownership. It exists because the two functions don't share a clock.

The Translation Layer: Where Revenue Decisions Live Without an Owner
Marketing Function
Campaign Clock
Time horizonWeeks and months
Success metricPipeline, conversion, attributable revenue
Risk toleranceSpeed: test fast, iterate, move before certain
Decision languageAudience, offer, channel, conversion
The Seam
Technology Function
Release Clock
Time horizonSprints and quarters
Success metricSystem stability, integration integrity, velocity
Risk toleranceStability: plan, test, document before deploying
Decision languageArchitecture, integration, throughput, debt

Revenue decisions live at the seam. Neither function owns it. No org chart draws a line to it. That is the Translation Layer gap.

The Three Gaps Inside the Seam

01
The Clock Gap
Marketing needs to respond to market conditions in days. Technology's next available sprint is three weeks out. Decisions stall at the seam.
Signal: Marketing campaigns are regularly delayed by technical requirements. Technology builds are regularly invalidated by marketing pivots.
02
The Metric Gap
Marketing measures pipeline and attributable revenue. Technology measures system stability and development velocity. Each function evaluates the same decision against a different definition of success.
Signal: Post-mortems attribute the same outcome to different causes depending on who is in the room.
03
The Risk Gap
Marketing tolerates and requires speed. Technology tolerates and requires stability. These risk postures are not compatible by default — they require a function to hold the tension between them.
Signal: Marketing requests are "too fast." Technology timelines are "too slow." Both are accurate from inside each function's operating model.

Three Solutions That Don't Work

The following are not stories about talented people making bad decisions. They are stories about smart organizations applying reasonable solutions to a problem they correctly identified but incorrectly diagnosed. In each case, the leaders involved were doing exactly what good leaders do. The gap is in the org chart, not in the people.

Composite A The Technical CMO

A $35M B2B software company hired a CMO with a technical background. The thesis was reasonable: someone who speaks the CTO's language will close the gap. The hire was strong. Her campaigns were technically sophisticated. Her attribution was clean. Her team respected her. The CTO and CMO worked together better than any pair the company had seen.

Eighteen months in, pipeline was flat. The CMO was optimizing for what the technology team valued — clean data, defensible attribution, integration integrity — because that was the shared vocabulary that made the partnership work. The campaigns were tighter. The conversion was lower. The gap had not closed. It had moved.

The lesson: Language fluency between two functions is worth having. It does not eliminate the structural gap. It shifts which problems get solved. The seam still has no owner.
Composite B The CTO with Marketing Authority

A $22M consumer brand gave its CTO formal ownership of the marketing technology stack after a prolonged standoff over tool purchases. The thesis: if one function owns the stack, the integration problem goes away. Integration did improve. Attribution became technically precise.

Campaign configurations required three-week lead times. The marketing team had stopped requesting changes that took too long to get through the CTO's prioritization queue. Revenue slowed, not from bad campaigns but from a configuration velocity problem no one had anticipated. The CTO's prioritization was rational. He was optimizing for the wrong clock.

The lesson: When one function's operational rhythm is imposed on the other, the gap moves downstream. It shows up in revenue.
Composite C The Agency Bridge

A $48M services company hired a digital agency to serve as the translator between marketing and technology. Six months in, the arrangement worked. The agency understood both sides. Decisions moved faster.

Then the company needed a real-time attribution call that touched both a live campaign and an active infrastructure change. The agency could not access the CTO's codebase. The CTO's team could not move faster than their sprint allowed. The decision that needed to move in days returned with a six-week timeline.

The lesson: External parties cannot hold structural tension that lives inside the organization. They bridge gaps when stakes are low and timelines are long. They cannot own the seam when revenue is on the line.

What Right Looks Like

One of my longest engagements began in 2008 under conditions that made the Translation Layer problem visible immediately: $17 million per year in revenue, $160,000 per month in advertising spend, zero tracking. A home improvement company. Not underspending on marketing. Spending aggressively on campaigns that had no connection to the technical infrastructure needed to measure, route, and close what those campaigns generated.

I did not hire into the gap. I became the gap. Every decision that touched marketing and technology went through a single function with accountability for the outcome. Ad spend was cut from $160,000 per month to roughly $60,000 per month. Lead volume increased 160%. Conversion improved. Average deal size increased. The call center software was rewritten. Attribution went from zero to closed-loop, tracking every dollar of spend to every closed deal.

Fourteen years later, the company was doing close to $100 million per year and sold to a major national manufacturer in their category. Not because the marketing and technology teams eventually learned to communicate better. Because the seam had an owner from day one.

"The companies that solved this problem were not the ones with the most talented CMO or the most sophisticated CTO. They were the ones that recognized the gap was structural and assigned it to something with a clear line of accountability."
From the Featured Analysis · Q2 2026
The integration question: What is the specific decision in your company that currently requires both your CMO and your CTO to agree — and who owns the outcome when they don't? If the answer is "it goes to me" or "it stalls," you have named the gap. That is the work.
Section 03 The Panel Debate

Who Actually Owns the Seam?

Four voices. One structural gap. No clean consensus.

EV
Dr. Eleanor Vance
Systems Architect
"The gap is architectural before it is organizational. Two functions running incompatible systems will never align through communication alone."
MO
Marcus Okafor
Revenue Operator
"Companies don't feel this as an architecture problem. They feel it as a pipeline problem. The fix starts with accountability, not a systems audit."
NC
Nadia Chen
AI Strategist
"AI has made this 10x worse. Every AI tool the marketing team purchases creates a new integration requirement that the CTO has to absorb."
LP
Linda Park
Historian
"This pattern has appeared at every major technology transition since the 1960s. The companies that solved it didn't communicate their way out. They built a new category of practitioner."
JK
John Kirker
CTMO & Practitioner
"The function is non-negotiable. The org chart is flexible. You don't have to build a new box to own the seam."
EV
Dr. Eleanor Vance
The Architecture Argument
I want to start with something this conversation almost always skips: the gap is architectural before it is organizational. Your CRM was built to support a sales motion. Your marketing automation platform was built to support campaign execution. Your development infrastructure was built to support product delivery. None of these systems were architected to exchange state with each other in real time, at the speed that revenue decisions require. The CMO and CTO are operating out of different systems that produce different representations of the same company. They are not just talking past each other. They are reading from different instruments. Put two excellent people in seats that read from incompatible instruments, and you will get misalignment. Swap the people, and you will get misalignment again. The structural fix is a function that sits at the integration point of those systems with the technical authority to define how they exchange information and the business authority to decide which decisions require that exchange.
MO
Marcus Okafor
The Accountability Rebuttal
Eleanor is describing a real problem and I won't argue with the architecture diagnosis. But companies don't feel this as an architecture problem. They feel it as a pipeline problem, a conversion problem, a missed quarter. What breaks in practice is almost always a handoff — and handoffs are not primarily systems problems. They are accountability problems. Someone was supposed to own a decision. Either no one did, or two people both did with incompatible definitions of what the right outcome looked like. My prescription is less elegant than Eleanor's but faster: audit every decision that currently crosses the CMO/CTO boundary and assign explicit ownership to every one of them. That audit will tell you whether you have an architecture problem or an accountability problem. In my experience, most companies have an accountability problem that looks like an architecture problem until you get close enough.
NC
Nadia Chen
The AI Acceleration Argument
Both of you are underweighting something: AI has made this problem structurally harder in the last 24 months. Every AI tool the marketing team purchases — and they are purchasing them faster than any previous category of martech — creates a new integration requirement that lands in the technology backlog. Copilot for campaign copy. Predictive lead scoring. AI-personalized landing pages. Automated audience segmentation. Each tool sits at the boundary between marketing's operational world and the technical infrastructure, and each requires someone who understands both sides to configure, maintain, and interpret correctly. The companies getting this right are not the ones with the best AI tools. They are the ones that created a function to govern the boundary between marketing's tool appetite and the technical stack that has to absorb it. In most companies, no one is asking that question before the purchase is made. The AI purchases happen. The integration backlog grows. The CTO's frustration compounds. And the CEO calls it a communication problem.
LP
Linda Park
The Historical Pattern
Every major technology transition in the second half of the twentieth century produced a version of the Translator Problem. When mainframes moved into large organizations in the 1960s and 1970s, a new function had to emerge — data processing — that sat between the technical infrastructure and the business operations that needed to use it. Companies that tried to solve this by teaching business users to program failed. Companies that tried to solve it by teaching programmers to understand business operations also failed. What worked, eventually, was a hybrid function with a different identity: someone for whom both sides were native language, not translation. The pattern repeated when the internet arrived in the 1990s. What emerged in the companies that succeeded was a new function that operated at the seam. What we are watching now is the same structural transition, with AI as the forcing function. The historical record is clear: companies that tried to solve this with communication practices were still arguing about it five years later.
JK
John Kirker
The Practitioner Close
I want to say something that might be uncomfortable after four well-argued positions: the function does not have to be a hire. When I stepped into the home improvement engagement in 2008, there was no budget for a new C-suite function. There were founders who needed the gap closed and were willing to give me authority over both sides of it. The function was me. One person, accountable for the seam, with access to both the marketing strategy and the technical architecture. That was enough to go from $17 million to close to $100 million. Marcus is right that accountability matters. Eleanor is right that architecture matters. Nadia is right that AI is accelerating the timeline. Linda is right that the historical fix is always the same. The function is non-negotiable. The org chart is flexible. The question is how long you are willing to let the gap cost you before you decide what to do about it.

Where the panel landed: all four voices agreed the gap is real and the cost is measurable. They disagreed on whether the primary fix is architectural, accountability-based, or a new dedicated function. No one argued the gap resolves without deliberate action.

Section 04 The Framework

The Translation Layer: A Diagnostic You Can Run in 24 Hours

Apply this before you make any structural decision. Find the gap first. Then decide what to do about it.

Step 1: List the decisions that have no owner

Identify every decision your company has escalated to the CEO in the last 90 days that involved both marketing and technology. Count them. That number is the cost of the Translation Layer gap expressed in escalations per quarter.

Wrong Fix
Better Communication
Scheduling more syncs, creating shared channels, mandating cross-functional briefings. These reduce friction at the edges but do not change the underlying clocks, metrics, or risk tolerances. The gap remains. The friction resurfaces every quarter.
Wrong Fix
Consolidating Under One Leader
Hiring a CMO who speaks technology, or giving the CTO authority over the marketing stack. These consolidate two functions under one clock — and one clock is wrong for the other function's actual job. Either pipeline slows or systems destabilize, depending on whose clock wins.

Step 2: Assign the seam explicitly

The right fix requires one thing: explicit ownership of the Translation Layer. A person or function whose job is to operate at the seam between marketing intent and technical execution, with accountability for outcomes on both sides.

This function requires three things, regardless of how it is structured:

1. Access: To both marketing strategy and technical architecture in real time, before decisions are made.

2. Authority: To decide when marketing requirements must adapt to technical constraints, and when technical timelines must adapt to marketing realities.

3. Accountability: For the outcome of decisions that live at the seam. Not advocacy for one function. Ownership of the result.

The diagnostic question to ask today

Take this into your next leadership meeting. Ask it directly, and watch what happens.

"What is the specific decision in your company that currently requires both your CMO and your CTO to agree — and who owns the outcome when they don't?"
The Translation Layer Diagnostic · Q2 2026

Three things will happen. Someone will name a decision immediately. Someone else will name a different one. A third person will be surprised that others experience this differently. That divergence is the gap, visible in real time. The disagreement is not the problem. The problem is that no function currently owns what happens next.

Section 05 The Provocation

The Case Against Adding a New Function

WS
William Stover
Steel-Manned Counterargument — Written in Good Faith

I will grant the featured analysis its central observation: the CMO/CTO alignment problem is real, it is expensive, and it does not respond to better communication practices. On that, we agree.

Where I push back is on the prescription. The Translation Layer framework describes, with some precision, what excellent leadership looks like at the intersection of marketing and technology. It then concludes that because most companies lack this function, they need a new organizational layer to fill it. That conclusion does not follow automatically.

The leaders I respect most at the CMO and CTO level already carry this responsibility — not because someone built a function around it, but because they understood that their job included the seam. They made it part of how they operated. They did not need a named function to own something they saw as inherently theirs.

"Before you build the function, answer this honestly: have you made it clear to your senior leaders that the intersection of marketing and technology is part of their accountability — and then measured them on it?"
William Stover · The Provocation · Q2 2026

Here is my more direct concern: every new organizational function creates a new coordination cost. The Translation Layer sits between two existing functions and takes on decisions that currently flow through the CMO and CTO. Now you have three functions at the intersection instead of two. The seam you were trying to close has potentially moved, not disappeared. I have watched companies add coordination layers to fix alignment problems and emerge with more alignment problems at a different organizational altitude.

If you have made the intersection explicitly part of your leaders' accountability and the problem persists, you likely have a structural gap. If you have not done that, you may be solving a management clarity problem with an organizational structure answer.

The Translation Layer is a real description of a real gap. My argument is that you should exhaust the clarity solution before you institutionalize the function.

Section 06 The Evidence Locker

Every Number Has a Basis

Every claim in this issue has a labeled basis. Composites are identified as composites. Confidence levels are assigned to any figure that involves practitioner analysis or extrapolation from limited data.

2008–22
Primary — John Kirker
Home improvement company: $17M to ~$100M over 14 years. Translation Layer owned by a single function from day one.
Starting conditions: $17M/year revenue, $160K/month advertising spend, zero tracking. Optimization phase: ad spend reduced to ~$60K/month (62% reduction), lead volume increased 160%, conversion improved, average deal size increased. Outcome: company acquired by a major national manufacturer in the home improvement category. Relationship continued post-acquisition.
5/5 — Primary source, direct engagement documentation
2000–12+
Primary — John Kirker
Terminix eDeals Platform: $500M+ in trackable revenue over a decade. Translation Layer built into infrastructure, not dependent on a person.
The PinID system operated at the seam between offline marketing (direct mail campaigns) and online and call center execution (web personalization, lead routing, automated follow-up). The system continued generating revenue long after active consulting involvement ended. The translation function had been built into the architecture. Terminix is a publicly known Rollins, Inc. subsidiary.
4/5 — Primary source; $500M+ figure is practitioner-reported based on campaign volume, duration, and revenue per transaction; not independently audited
1996–2001
Primary — John Kirker
PinID direct mail attribution system: deployed at 200+ enterprise customers before UTM parameters or Google Analytics existed.
The PinID system tracked offline direct mail campaigns to online conversion events a decade before the industry had language for attribution. Deployed across mortgage, insurance, pest control, and recruitment verticals. Served 45+ Fortune 500 clients through the Stirling Bridge Group, including Terminix, Kaiser Permanente, Allstate, Charles Schwab, and Fidelity. The system predated the analytics category it was solving.
5/5 — Primary source, direct operational records
Historical
Pattern — Linda Park
The marketing/technology alignment gap has appeared at every major technology transition since the 1960s. The structural fix has always been a hybrid function, not better coordination.
Documented in technology diffusion literature (Rogers, 1962; Moore, 1991) and organizational behavior research on functional integration. The pattern: data processing (1960s-70s), IT/business alignment (1980s-90s), digital/traditional integration (2000s-10s), AI/marketing integration (2020s). Companies that solved this with communication practices were still debating it five years later.
3/5 — Well-documented pattern; application to current AI transition is editorial inference
2024–26
Observed — Editorial
AI tool adoption is creating Translation Layer pressure 3-5x faster than the previous martech adoption cycle. Most companies have no governance at the boundary.
Marketing teams at $10M to $100M companies are evaluating and purchasing AI tools on timelines measured in weeks. Each purchase creates an integration requirement that lands in the technology backlog measured in sprints. The most exposed companies are those where marketing has budget autonomy for tool purchases but no obligation to route tool evaluations through the technical function before commitment.
2/5 — Directional observation; no systematic measurement for this specific dynamic at this company-size segment
Section 07 · The Trailing Question

If the gap between your marketing and technology functions is structural — built into the clocks, metrics, and risk tolerances of each — then every time you escalate a decision between them to yourself, you are absorbing the cost of the gap personally. What is that costing you, in CEO time and in revenue that did not close?

That number is not in any dashboard. Calculating it is the work this issue asks you to do.

Forward this to the person in your company who would argue with it most. That conversation is the point.