GTM Engineering Is Just Marketing Ops With Better PR | Sara McNamara

There is a specific kind of organizational amnesia that ops professionals know intimately. Things are running. Leads are routing correctly. Data is clean. Campaigns are launching on time. Integrations are holding. And because everything is working, no one is thinking about why.

Then someone gets laid off. Or the budget gets cut. And six months later, leadership is looking at a smoldering pile of broken automations and corrupted records, wondering what happened.

What happened is that you had someone who knew where all the bodies were buried — and you forgot they existed.

Sara McNamara has watched this cycle play out at Cloudera, Slack, Salesforce, and now as Revenue Operations and Go-to-Market Lead at Vector. She has built GTM systems at companies that have become the infrastructure for entire industries. And she has a clear-eyed view of what is happening to her function right now: operations is being rebranded, compressed, and quietly erased from org charts at the exact moment it is becoming the most strategically valuable job in go-to-market.

The rebranding cycle has been hard to miss. Marketing ops became revenue ops. Revenue ops is now competing for oxygen with GTM engineering. GTM engineering is cross-pollinating with "marketing engineering," "systems architects," and a half-dozen other titles that want "engineer" somewhere in the name.

Sara is not impressed.

The danger is not the title itself. The danger is that companies use the title as cover for not staffing ops properly — and then wonder why no one is executing the "new playbooks." If your ops team is buried in triage and basic maintenance, it is not because they lack the expertise to do GTM engineering. It is because you have not given them the capacity to do anything else.

And as Sara put it, there is something worth naming about who tends to champion these rebrands: "It feels like a lot of men who just want better titles, when in reality they're still doing the exact same work."

Here is what is not talked about enough: ops is a catch-all for organizational dysfunction.

The agency that works out of a spreadsheet and cannot integrate with anything, ops figures it out. The event was planned in the last 72 hours; ops builds the tracking. The campaign was approved without considering data implications; ops cleans up the records afterward. The list was imported from a conference with no consent documentation. Ops handles the compliance exposure quietly.

This invisible load never gets counted. It does not show up in a capacity model. It does not factor into headcount decisions. It accumulates until the ops team disappears, and six months later, leadership is staring at a smoldering pile of broken automations and corrupted records, wondering what happened.

What happened is that you had someone who knew where all the bodies were buried. And you forgot they existed.

With AI reshaping what ops teams spend time on, Sara is thinking carefully about what must remain under direct ownership and what can safely move.

Her answer is specific: the GTM data layer. CRM. Marketing automation platform. Data warehouse. The sources of truth that everything else depends on.

This is not a conservative position. It is a systems design position. The risk she is flagging is vendor lock-in at a foundational level, the scenario where you have migrated your core business logic into an AI platform, and then the pricing changes. She pointed to the Uber and Instacart playbook: subsidize adoption, create dependence, then raise rates once switching costs are prohibitive. "If all of a sudden it becomes a million dollars a year, and we aren't completely screwed, like there's a lot of talk out there where people say I'm going to replace my CRM with AI and I'm like... then what?"

Her framework: treat the GTM data layer as the house's steel frame. Everything else signals: orchestration and AI-native tooling are the interior. Interesting, valuable, worth building. But you do not rebuild the frame every time you renovate the kitchen.

The framing that ops is shifting "from builder to enabler" in the AI era makes some practitioners bristle. It sounds like a downgrade, like ops is being moved from the engine room to the help desk.

Sara's reframe is worth sitting with.

The work that consumed ops capacity before pulling lists, building manual reports, and constructing integrations from scratch for every new use case was not the part of the job that required the most expertise. It was the part that left the least time for the work that did. If AI handles more of the execution layer, ops professionals have the capacity to do the thing they have always been best positioned to do: see across the whole GTM system and make it function coherently.

The risk is not that ops becomes irrelevant. The risk is that the vacuum gets filled by someone else. Engineering. Marketers who went through a GTM engineering bootcamp. Vendors who want to own the orchestration layer and lock you in. If ops practitioners are not present and fluent in the AI conversation, they will find that the strategic territory they were best suited to claim has already been claimed.

The practitioners she is most concerned about are not the systems thinkers, but the campaign ops professionals whose identity is tied to execution volume. The answer is not panic. It is a question: if AI can send 500 campaigns, what could you do with that capacity? What does it look like to be in the strategy seat rather than the execution seat?

No conversation about marketing ops is complete without attribution – the perennial unsolved problem that every new wave of technology promises to fix. AI is no exception.

Sara's position is direct: we are spending too much energy on it.

The dark funnel is real. Incognito browsers exist. Decisions get made in conversations that leave no digital trace. The moment you think you have closed the loop, a new privacy policy or browser update reopens it. Chasing perfect attribution is chasing a moving target that will never stop moving.

More importantly, an organization that needs attribution to prove marketing is doing something has a larger problem that attribution will not solve. It is an internal positioning problem. It is a trust problem between functions. And resolving that through data engineering rather than through the harder work of organizational alignment is a workaround, not a fix.

Her practical suggestion: add a "where did you hear about us?" field to your demo request form. It is zero-party data. It is directionally reliable. It is unglamorous. It works.

Sara McNamara is the Revenue Operations and Go-to-Market Lead at Vector and the creator of the Marketing Operations Strategist newsletter.

Special thanks to Claude for helping to summarize this conversation.