The news
A recent piece in MarTech diagnoses a pattern most marketing ops teams will recognize immediately: automation systems that started lean and purposeful, then slowly accumulated workflows, edge cases, and stakeholder requests until they became too tangled to trust. The result isn't a broken system — it's an overloaded one, and the symptoms show up as slower campaign launches, inconsistent lead data, and teams quietly routing around the tools they're supposed to rely on.
Our take
This exact pattern shows up in nearly every overloaded GTM stack. Marketo instances with 400+ active programs. HubSpot portals where nobody can answer "what happens when a lead fills out this form" without a 20-minute archaeology project. Lifecycle stages managed inside campaign workflows instead of centrally — so MQL means something slightly different depending on which nurture stream touched the contact first.
The article frames this as a complexity and maintenance problem. That's accurate. But here's the sharper read: automation debt is the reason most AI projects fail before they start.
When teams ask dAIs to help them add AI to their GTM workflows, the first thing we do is map what's already running. And what we consistently find is that the existing automation is too fragile and too opaque to hand off to anything smarter. You can't build an AI layer on top of a system that your own team doesn't fully understand. The model doesn't fix the logic gaps — it inherits them, and then executes them faster and at higher volume.
The MarTech piece recommends a systems-based approach: centralize operational logic, separate it from campaign logic, and build with reuse in mind. That's exactly right. But there's an urgency here the article undersells. AI in GTM is an operator problem, not a technology problem — and automation debt is the most common operator problem dAIs encounters. Teams that clean up their automation foundation now are the ones who will actually be able to use AI when they're ready to layer it in. Everyone else will keep adding workflows to a system that's already underwater.
The so-what
The audit your team has been putting off isn't a nice-to-have — it's a prerequisite. Before you add AI to anything, you need to know what your automation is actually doing. Pick one process (lead lifecycle, lead routing, or event follow-up are the usual suspects), document every workflow that touches it, and consolidate ruthlessly. The teams winning with AI aren't the ones with the most sophisticated models — they're the ones who did their homework on the messy stuff first.
---