As software begins to interpret objectives, make decisions, and act across systems, the question is whether the environment around the stack contains enough context, rules, permissions, and accountability for both people and machines to operate reliably.
For years, marketing leaders have been taught to think about martech as a collection of capabilities. CRM handles customer data. DAM manages assets. Workflow coordinates work. CMS publishes. Automation executes repeatable processes. Analytics measures what happened.
The strategy followed naturally: build the right stack, connect it, get people to use it, and keep improving the architecture. That model still matters. But it rests on an assumption we rarely talk about — that a person is sitting somewhere in the middle, making sense of everything the technology doesn’t know.
A person knows which of the five assets in the DAM is the approved one. They know the CRM record is technically correct, but six months out of date. They know Legal objected to that phrase last time, even though nobody ever updated the guidelines. They know one market needs another review before anything goes live.
The stack has always had a human operating layer holding it together. AI is starting to expose what happens when that layer is no longer guaranteed.
The stack was built for human operators
Even the great waves of marketing automation didn’t fundamentally change this arrangement. Someone still defined the rule, configured the workflow, set the variables, and decided where automation started and stopped. The system executed within the boundaries that people had established in advance.
Where the technology fell short, people filled in the blanks. Because humans are good at working around ambiguity, marketing organizations have tolerated weak metadata, half-designed processes, inconsistent governance, local exceptions, and information scattered across inboxes, spreadsheets, meetings, and institutional memory.
That tolerance shaped the stack we have today. It also explains why so many organizations can have well-integrated technology and still depend on a handful of experienced people who just know how things work.
For a human-operated environment, it can remain inconvenient rather than catastrophic. A person can spot the inconsistency, phone somebody, check an old email, or know that the documented process isn’t quite how the process actually works. Software has no such luxury.
10X your SEO with Semrush for Enterprise.
The world’s most powerful SEO platform, purpose-built for Enterprise.
Request demo
AI has no tribal knowledge
As intelligent systems move from assisting marketers to selecting, deciding, routing, generating, or acting, much of that invisible human context needs to be available somewhere the technology can access it.
A system needs to know not only that information exists, but which version is authoritative. It needs to know whether an application can perform an action and whether it’s allowed to do so in a given situation. It needs to know whether an asset is available, approved, current, correctly licensed, and appropriate for a particular market or audience.
This is why discipline is becoming more important than ever. Metadata, provenance, permissions, workflow state, rights, and ownership are starting to matter differently. None of them is new. Enterprise architects have been talking about them for years. The difference is what happens when they’re weak.
A bad taxonomy is used to make the DAM annoying to search. Now it can cause software to select the wrong asset. An ambiguous approval state is used to trigger another Teams message. Now it may determine whether a system believes it has permission to publish.
The weakness hasn’t changed. The actor has. That creates a requirement martech strategy has rarely had to consider: machine operability.
Human usability asks whether a marketer can work with the technology. Machine operability asks whether the information, rules, and capabilities within that environment are explicit enough for another system to understand and act on them reliably.
Gartner’s 2026 CMO Spend Survey suggests investment is already moving faster than operating maturity. CMOs are allocating an average of 15.3% of their marketing budgets to AI initiatives, yet only 30% report having mature AI readiness capabilities. Seventy percent say their internal marketing processes aren’t mature enough to implement and scale AI effectively.
That gap isn’t simply an AI problem. It’s an operating-environment problem.
CreativeOps is where the cracks show first
Creative production makes this easy to see because generative AI has dramatically increased the amount of marketing that can be produced.
At task level, the economics look fantastic. A first draft takes minutes. Visual routes multiply. Localization happens almost instantly. Work that once required more people, agency hours, or production budget suddenly appears available at a fraction of the effort.
Then it reaches the rest of the process. A tenfold increase in generation doesn’t create 10 times more useful marketing. If briefing, rights management, review, approval, localization, and publishing still run as they did before, very little changes. You haven’t removed the bottleneck. You’ve only moved it.
McKinsey found something similar at the enterprise level. Of 25 organizational attributes examined, workflow redesign showed the strongest relationship with reported EBIT impact from generative AI. Yet only 21% of organizations using the technology said they’d fundamentally redesigned at least some workflows.
Making the task faster doesn’t make the system better.
Get MarTech Insights That Matter
Platform news, strategy analysis, and industry trends. Trusted by 40,000+ marketing professionals.
The hard part starts after generation
Imagine a global campaign producing thousands of variants. Creating them may now be straightforward. The difficult questions arrive afterward.
Which product information is current? Which claims have been approved? Which imagery can be used in which territory? What parts of the brand system can change? Which markets require additional review? What happens when something falls outside the normal process?
A seasoned reviewer carries much of that context instinctively. A machine doesn’t.
CreativeOps is becoming a proving ground for the next martech operating model. Its role has been framed in terms of briefing, resources, workflow, review, approval, technology, and delivery. As more production becomes automated, the organization faces the question of how human judgment, deterministic automation, and intelligent systems work together.
Adobe’s Workfront Content Reviewer is an early example of where this is heading. It can participate in projects and approval workflows in a similar way to a user, assessing work and making recommendations before a human makes the final call.
The clever part isn’t that AI can review an asset, but rather everything that has to exist before the review means anything.
Brand rules have to be explicit enough to assess. Approval criteria need to be clear. Rights and context need to be available. On-brand needs to mean more than “John from brand will know it when he sees it.”
If 10 years of institutional knowledge are still required to decide whether something is safe to ship, another agent doesn’t solve the problem. The platforms are connected while the judgment is often not.
Connected isn’t the same as operable
A smart martech reader could reasonably ask whether this is simply composable architecture, APIs, and interoperability repackaged for the AI era. It isn’t.
Integration solved an important problem. It allowed information and capabilities to move between systems without everything having to live in a single giant platform. But access isn’t understanding.
An API can expose an asset perfectly and give a machine no idea whether that asset is approved. It can expose customer data without explaining whether a particular use is permitted. It can expose a workflow status without telling the system whether that status grants authority to act.
Integration makes the information available. Operability makes the environment understandable enough to use. That second part doesn’t arrive free with the connector.
Somebody still has to intervene. Someone still has to define the rules, clean the metadata, structure the rights, clarify ownership, and decide what each workflow state means. It isn’t the sort of work that gets the glamorous transformation slide.
Unfortunately, it’s the work that determines whether the glamorous transformation survives contact with the organization.
This changes where martech strategy should begin. Most roadmaps start with the estate already in place.
- What’s underperforming?
- What’s duplicated?
- What can be consolidated?
- Which platform needs replacing?
- What are we missing?
Those are sensible questions, but they also make today’s stack the starting point for tomorrow’s operating model. That’s backward. Start instead with the operating capability marketing wants to build: What do we expect people and intelligent systems to be able to do together?
You have to work backward into the technology. If the ambition is automated localization, the requirement isn’t simply a better generative model. Marketing needs structured assets, reliable rights information, useful metadata, market rules, approval logic, and an authoritative place for the final content to live.
If the ambition is more autonomous campaign optimization, the interesting question isn’t whether software can move budget. Of course it can. The question is when it’s allowed to, what information it should use, where the exceptions sit, and who owns the call when it gets one wrong.
An AI use case quickly becomes a martech requirement. That’s why AI strategy and martech strategy are becoming difficult to separate. AI strategy asks what greater intelligence makes possible. Martech strategy determines whether the organization is capable of supporting it.
Yesterday’s repositories become tomorrow’s infrastructure
There is another, slightly counterintuitive consequence. Some of the less fashionable parts of the stack may become more important as human interaction with them declines.
DAM is a good example. A poorly governed DAM, full of duplicates, weak metadata, and questionable rights information, doesn’t become strategic just because someone plugs AI into it. It becomes a faster way to find and use the wrong asset.
A DAM containing authoritative assets, strong metadata, clear rights, and meaningful relationships between content, products, and markets is a different proposition. Intelligent systems can consume that context directly.
Fewer people may eventually need to log into the DAM itself. That doesn’t mean it’s become less important. It may mean it’s graduated from “somewhere people go” to “somewhere the operating environment depends on.”
It also requires a rethink of procurement. Functionality, UX, implementation, and cost remain important, but buyers also need to ask whether the data, context, and actions inside a platform can participate in a wider environment that the organization controls.
A vendor can have the best AI demo in the room and still leave you with a very expensive dead end if everything useful is trapped inside its own ecosystem.
The environment must become the foundation of the strategy
The stack isn’t disappearing, and neither are people. This also isn’t an argument for handing the keys to autonomous agents and hoping for the best. Different organizations will move at different speeds and delegate different levels of authority to software.
What matters is preserving the ability to make those choices. The next martech roadmap needs to describe more than which platforms marketing intends to buy, replace, consolidate, or connect. It needs to describe the operating capability marketing intends to build.
That means machine operability sitting alongside human usability. It means turning more of the rules, permissions, context, and accountability carried by experienced people into infrastructure that the wider environment can use. It means recognizing that the next source of martech advantage may have very little to do with who owns the longest feature list.
For 20 years, the martech stack has largely existed to give marketers better tools with which to run marketing. Its next job is bigger: to create an environment in which people, automation, and intelligent systems can run marketing together without relying on somebody in the corner who just knows how this stuff works.
The next martech strategy will be decided by whether you’ve built an environment where both people and machines can be trusted to work.