The most dangerous idea in martech right now isn't that AI will collapse your stack. It's that because AI can replace something, it should. These are very different decisions with very different consequences.
The real shift happening — as Gareth Chilton argues in a sharp piece for MarTech — is repricing, not replacement. AI is applying downward pricing pressure to the coordination layers of your stack while leaving structural, liability-bearing systems largely intact. For MOps leaders, this distinction isn't academic. It's the difference between a smart consolidation and a governance disaster waiting to happen.
The Stack Isn't One Thing — Stop Auditing It Like It Is
Most marketing operations teams evaluate their stack the same way: usage metrics, license cost, stakeholder complaints. What that framework misses is the more important question: what does this tool actually absorb?
Every tool in your stack falls into one of two categories. The first is surface functionality — coordination wrappers that reduce friction. Intake forms, workflow builders, status dashboards, lightweight asset browsers. These are valuable, often well-designed, and genuinely useful. But their core value proposition is convenience, not risk absorption. They make coordination faster and more visible. They don't make it defensible.
The second category is structural depth — systems that own operational liability. Enterprise DAMs with rights enforcement and expiry rules. CRMs with audit-grade interaction histories. Attribution platforms integrated across advertising, CMS, and analytics pipelines. These aren't just expensive to replace in terms of license fees. They're expensive to replace because switching means transferring governance, evidentiary traceability, and integration maturity to something new. The cost is measured in organizational risk, not just vendor contracts.
When you audit with this lens, a lot of your "expensive" tools suddenly look cheap, and a lot of your "cheap" tools suddenly look vulnerable.
Where Commoditization Pressure Is Real — And Where It Isn't
Let's get specific about which stack layers are actually exposed.
High commoditization pressure (surface/coordination layers):
- Standalone intake and briefing tools — If the primary value is a structured form with routing logic, AI-assisted internal builds are credibly viable. The prototype-to-working-tool timeline has collapsed.
- Basic workflow and task management overlays — Tools whose core function is task routing and status visibility face serious pricing pressure. Organizational inertia and interface familiarity are no longer sufficient competitive moats.
- Lightweight asset libraries without activation integration — Storage-plus-search without downstream channel connections, rights management, or expiry enforcement is increasingly replicable.
- Proofing layers without regulatory weight — Review and approval tools that aren't embedded in compliance or audit workflows are coordination conveniences, not structural requirements.
Defensible value through operational risk ownership:
- CDP and identity resolution platforms — The coordination interface is replicable. The unified identity graph, consent architecture, and downstream activation integrations are not. A CDP's value isn't the UI — it's the data model and the compliance liability it absorbs.
- Enterprise CRM systems — Salesforce or HubSpot aren't expensive because their interfaces are irreplaceable. They're defensible because they carry audit-grade interaction histories, territory governance, and deep integration with revenue reporting. Replacing them means re-absorbing all of that operational maturity.
- Attribution and measurement infrastructure — Multi-touch attribution tools integrated across paid, owned, and earned channels aren't just dashboards. They're evidentiary systems that inform budget decisions. The deeper the integration, the higher the switching cost — and the higher the liability if something breaks mid-migration.
- DAMs with rights and expiry enforcement — An enterprise digital asset management system feeding multiple channels with market-specific rights windows and audit trails represents a genuine transfer of legal liability if replaced. Prototype speed does not hide this.
The pattern is consistent: repricing occurs where substitution is credible and liability remains low. It does not occur evenly, and assuming it does is how MOps teams make expensive mistakes.
The Prototype Trap That's Going to Cost Someone Their Job
Here's where the repricing thesis has a sharp practical edge: the speed at which AI can produce a working prototype is actively misleading procurement conversations.
A team can now assemble a functional intake form, approval workflow, and status dashboard in a fraction of the time it took two years ago. That prototype genuinely works. It demonstrates possibility. And it creates organizational pressure to cancel the vendor contract and own the build internally.
What the prototype doesn't demonstrate is production readiness. In real environments, multiple teams modify assets simultaneously. Regional adaptations overlap. Legal holds freeze assets mid-campaign. Access control failures create compliance exposure. Audit logs are subpoenaed. Concurrency, governance, and evidentiary integrity are not features you prototype — they're disciplines you build over years.
The most common mistake in AI-driven stack consolidation is confusing the speed of building a coordination layer with the cost of absorbing structural liability. These are not the same thing, and the delta between them is where governance failures live.
Actionable Takeaways for MOps Leaders
- Run a liability audit, not just a usage audit. For each tool, ask: if this fails or gets replaced, who absorbs the operational and legal risk? Tools where the answer is "the vendor" are more defensible than they appear in a cost comparison.
- Flag every tool whose primary value is a UI. If a vendor's pitch centers on interface design, workflow visualization, or ease of use — and not on what liability they absorb — treat that as a commoditization signal.
- Treat CDPs, CRMs, and attribution infrastructure differently from coordination tools. These are not the same decision. Consolidation logic that applies to intake tools does not apply to identity resolution or audit-grade systems.
- Demand production-readiness criteria before any internal build decision. Prototype demos should be evaluated against: concurrent access control, audit trail integrity, integration depth with existing systems, and failure recovery protocols.
- Pressure vendors on coordination-layer pricing. If a vendor can't articulate what operational risk they absorb beyond workflow convenience, use AI repricing as a negotiating lever. That pressure is legitimate and increasingly credible.
- Identify your best-of-breed structural systems and protect integration depth. The switching cost in liability-bearing tools isn't just migration effort — it's the re-accumulation of operational maturity. Don't underestimate it.
The Stack That Survives AI Repricing Is the One That Knows What It Owns
The marketing stack isn't collapsing. It's being sorted. Coordination layers will face sustained pricing pressure as AI makes substitution credible — and MOps teams that hold premium contracts for convenience tools will find those negotiations getting harder to justify internally.
The teams that emerge from this consolidation cycle with functional, defensible stacks will be the ones who audited by liability ownership rather than feature comparison. Surface tools will get cheaper or get cut. Structural systems — the ones that absorb governance, integration depth, and operational risk — will justify their cost more clearly than ever. The strategic question isn't whether to consolidate. It's whether you know which half of your stack is which.
