What’s up folks, welcome to our 4 part series of crawling through the dungeon of martech architecture. You’ve arrived at our final episode, part 4: The Dispatch Tower.

We’ll tackle:

(00:00) - Intro
(00:59) - In This Episode
(01:30) - Sponsor: Mammath Growth
(02:33) - Sponsor: GrowthLoop
(03:58) - FLOOR 4: THE DISPATCH TOWER
(04:39) - What Happens When 30 Vendors Turn On AI at the Same Time
(21:24) - Boss Battle: The Agent Avalanche
(22:53) - Why You Need a Central Referee, With Agent Guardrails
(26:48) - Sponsor: Knak
(27:55) - Sponsor: MoEngage
(28:52) - Privacy Compliance and Data Minimization
(38:38) - The Dispatch Layer that Controls Routing Logic
(44:00) - The Layer Above the Dispatch is the Interface
(47:20) - What Production AI Agents Look Like on a Governed Data Foundation
(50:27) - The Deterministic Layer: Why the Interface Can't Run on Guesses
(53:09) - System Stewardship: The Role That Emerges When You Clear This Floor
(59:33) - FINAL ACHIEVEMENT: The Dungeon Is Cleared

---------------------------------------------------------------------------
OPENING
---------------------------------------------------------------------------

Welcome back to the Dungeon of Martech Architecture.

You've arrived at the final floor. Parts 1 through 3 built the foundation, the meaning layer, and the causal memory. Part 4 is the floor most organizations have been living on the whole time, often without knowing it.

Episode 1: CRM Gravity
We conquered the source of truth and discovered that the data warehouse replaces the CRM with portable audiences.

Episode 2: The Eye of Context
We learned why AI fails without context engineering and built the shared meaning infrastructure that keeps agents from misinterpreting what they read.

Episode 3: The Correlation Masquerade
We escaped the correlation trap and built the causal memory layer that separates agents that optimize correctly from agents that confidently scale the wrong behavior.

Episode 4: The Dispatch Tower
Today, we tackle the governance chaos of 30 vendors all claiming authority, and confront the interface decision that most organizations already made without realizing it.

Let's finish our descent.

---

---------------------------------------------------------------------------
FLOOR 4: THE DISPATCH TOWER
---------------------------------------------------------------------------

Congratulations martech crawler, you’ve arrived to the final floor of the dungeon. Let’s face it, most of your fellow crawlers will never make it this far. They’re still lost in political battles debating why the CRM shouldn't hold product activation data or they ended up falling prey to the correlation trap and I forever stuck in the boomerang room.

But you’ve made it. You’re proudly wearing the 3 badges of honor on your jacket: data janitor, context king and causal brainiac.

This floor is the hardest because it combines collaborative political battles but some serious technical obstacles as well. The layout of this floor is best described as a hot mess of agent spaghetti.

Every vendor in your stack has an agent now. Your ESP has one. Your CDP has one. Your MAP has one. Your CRM has one. Your ad platform has one. Each one has separate logic, separate assumptions, separate permissions, and a roadmap slide that says “autonomous.”

None of them knows what the others are doing.

And nobody volunteered to referee this stuff.

At the top of this floor, there is a door most organizations never noticed. Whoever controls that door controls what instructions get through, which systems can act, and which agent gets authority over the customer.

What Happens When 30 Vendors Turn On AI at the Same Time

Your inbox is probably already full of emails from every platform in your stack, all saying some version of “Turn on AI today.”

Each one promises autonomous intelligence. Each one wants permission to write, recommend, segment, suppress, score, enrich, personalize, or trigger something. Each one is operating from its own model of the customer. None of them can explain what happens when two agents try to update the same record, message the same person, or optimize against conflicting goals.

You are now the referee. Congratulations.

Rich Waldron, CEO of Tray.ai, describes how this feels on the ground:

RICH WALDRON, Episode 162
"If you're the marketing ops leader and your 30 vendors are telling you to go turn on the AI for their application, you sort of become like an AI referee. You have to figure out, well, do I turn it on for this one and not for this one? And is this one gonna overwrite what occurs here? You feel it already. Your inbox floods with vendors begging you to 'just turn on our AI capability' -- 30 different platforms all promising transformation. Suddenly you're an unwilling AI referee asking impossible questions: which AI systems should I activate first? What happens when one AI's decisions contradict another's? Are all these systems feeding sensitive data into the same models?"

"Agents backed by an iPaaS give you full governance and control of where execution happens. For teams drowning in vendor AI chaos, the third option -- iPaaS-backed agents that naturally integrate with everything -- provides centralized governance, unified control points, and consistent execution environments."

Rich is describing the nightmare version of the final floor: every vendor ships an agent, and marketing ops gets stuck deciding which ones are safe, which ones are redundant, which ones are risky, and which ones quietly conflict with each other.

The answer is not to let every team turn on whatever they want. It is also not to create a central AI police force that blocks everything until innovation dies in a committee.

The middle path is an operating model: a small central group that sets standards, reviews risk, creates reusable patterns, and lets the business move quickly without turning the stack into a haunted appliance store

Funny enough, I spoke with someone who actually did volunteer for that AI referee job – her title is a bit fancier though. Here’s Lindsay Rothlisberger, Director of GTM Innovation at Zapier and also a member of their AI Center of Excellence.

At Zapier, she sits at the spoke of a hub-and-spoke AI Center of Excellence, a small central team led by a Chief AI Officer, with Lindsay as the GTM representative responsible for translating governance into go-to-market practice. Her work covers deciding which AI tools get activated, setting the standards for what a shared skill has to pass before it enters the internal library, and keeping track of what people are building before it fragments into 100 unsanctioned experiments.

LINDSAY ROTHLISBERGER, Zapier
"We have a skill that reviews our skills for data and security compliance. It gives you a red, yellow, green. Red — here's what you definitely need to fix. And in most cases, Claude can just say, 'I can go fix that for you. Would you like me to do it?' And just do it. So it's a pretty simple process. But it is a standard review skill that runs through all of these different things."

Every shared skill at Zapier has to have a named owner. If it's used across a team, someone is accountable for maintaining it. Skills covering go-to-market operations are owned by RevOps. New builders who want to ship a skill that runs through a cross-functional workflow pair with a RevOps partner to build it. The governance operates as a co-authorship model, designed to make s...