Creative teams don't need more tools — they need everything in the same infrastructure

Creative teams don't need more tools — they need everything in the same infrastructure

Posted 3/11/26
11 min read

Creative teams have never had more tools. They've also never spent more time moving work between them. The invisible cost of fragmentation — the exports, the re-uploads, the lost approvals, the diverging versions — is now larger than the inefficiency of any single tool. The shift isn't toward better tools. It's toward fewer seams.

  • The average enterprise marketing org operates 91 distinct tools at 33% utilization
  • Companies lose an average of $21M per year on unused SaaS licenses
  • Consolidation is accelerating — but creative operations is the last function to benefit

There's a specific moment that every creative operations leader recognizes. A campaign is in final review. The brief lives in one platform. The assets sit in another. Comments were left in email, or maybe in a Slack thread, or possibly on an annotation tool that half the team has access to. The approved version is somewhere in a shared drive — unless someone uploaded a newer version to the project management tool, in which case no one is sure which file is current. External stakeholders received a review link three days ago but their feedback came back as a PDF markup attached to a forwarded email.

Nothing in this scenario is broken. Every tool is functioning exactly as designed. The problem isn't any individual tool. The problem is the space between them.

Fifteen thousand tools and a third of them actually used

The martech landscape in 2025 reached 15,384 commercial solutions, up 9% year over year. That number has grown nearly a hundredfold since 2011. The average enterprise marketing organization now operates 91 distinct tools, according to Gartner's Marketing Technology Survey. Utilization hovers around 33% — meaning roughly two-thirds of purchased capability sits dormant. Licensed, partially integrated, and ignored.

This isn't a new finding. What's new is the trajectory. Utilization has been declining for years — from 58% in 2020 to 42% in 2022 to 33% in 2023. Gartner's 2025 survey shows a partial recovery to 49%, but against a backdrop of even more tools per organization. The math hasn't changed: teams are spending more on technology, using less of what they buy, and losing an average of $21 million per year on unused SaaS licenses.

The standard response has been to call for "stack rationalization" — audit your tools, cut the duplicates, consolidate where possible. That advice is correct and insufficient. It treats the symptom (too many tools) without addressing the structural cause: the work of creative production doesn't live in any single tool. It lives in the transitions between them.

The hidden tax: what happens between tools

Ask a project manager how long a campaign takes from brief to delivery. Then ask them how much of that time is spent on the actual creative work versus moving information between systems. The ratio is almost always worse than anyone expects.

The fragmentation tax shows up in predictable ways. Version confusion is the most visible: when the brief is in Notion, assets in Google Drive, feedback in email, and delivery through a separate distribution platform, no single system holds the authoritative state of the project. Each tool maintains its own version of truth. Conflicts don't surface until someone notices — usually too late, usually in production.

Approval bottlenecks are the second cost. When review happens outside the environment where the asset lives, every approval cycle requires an export, a share, a context switch, and a re-import. Multiply that by the number of stakeholders, the number of variants, and the number of rounds, and you have a process where the review infrastructure consumes more time than the review itself. As we explored in The validation paradox, slow approvals aren't usually caused by slow reviewers — they're caused by the friction that sits between the reviewer and the asset.

Context loss is the third and most insidious cost. Every time work moves between systems, metadata drops. The reasoning behind a creative decision, the client feedback that shaped a revision, the approval status of a specific variant — this information exists somewhere, but it's scattered across tools in formats that don't talk to each other. When a new team member joins a project, or when a regional adaptation requires reference to the original decision chain, reconstructing context from fragmented systems becomes a research project.

None of these costs appear on a dashboard. They don't show up in tool-specific analytics. They exist in the margins — in the 45 minutes someone spent finding the right file, in the approval cycle that restarted because feedback was left in the wrong channel, in the regional variant that went live with an outdated asset because the version in the shared drive wasn't the version in the project management tool.

Why "best of breed" broke creative operations

The "best of breed" philosophy — pick the best tool for each function, then integrate them — dominated enterprise software procurement for a decade. It made sense in domains where workflows are linear and handoffs are clean: CRM feeds marketing automation, marketing automation feeds analytics. The data moves in one direction, the integrations are standardized, and the failure modes are predictable.

Creative production doesn't work this way. A campaign asset moves through briefing, creation, internal review, revision, external review, approval, versioning, localization, and distribution — and at each stage, different people need to interact with it in different ways. The brief author needs to see the latest version alongside the original direction. The reviewer needs to annotate directly on the asset. The production lead needs to track which variants have been approved and which are still in progress. The external partner needs access to review without access to internal conversations.

In a "best of breed" stack, each of these functions lives in a different tool. The brief is in a project management platform. The asset is in a storage system. The annotation is in a review tool. The approval is in an email or a workflow engine. The external review is in a link-sharing service. The version history is — well, it depends on which tool you're looking at.

This architecture creates a paradox: the more specialized each tool becomes, the more work is required to connect them. Gartner has noted that complexity of the current ecosystem, customer data challenges, and inflexible governance are the most common impediments to greater utilization. The tools aren't the problem. The seams are.

The martech consolidation trend is well documented: CRM platforms absorbing marketing automation, MAPs expanding into CDP territory, suites replacing point solutions. But this consolidation has mostly happened in demand generation, analytics, and customer data. Creative operations — the part of marketing that actually produces the work — remains one of the last holdouts of fragmented tooling.

AI makes fragmentation worse, not better

The instinct in 2026 is to assume that AI will solve the integration problem. If the tools don't talk to each other, an AI agent will bridge them. If context is scattered, an AI will reassemble it. If approvals are slow, an AI will route them faster.

This misunderstands the problem. AI tools are commoditizing rapidly — the generation capability that was a differentiator in 2024 is a feature in every major platform by 2026. But AI amplifies whatever infrastructure it sits on top of. If the underlying workflow is fragmented, AI accelerates the fragmentation. It produces more variants faster, across more tools, with less human oversight at each transition point.

The result is a new form of creative sprawl: AI-generated assets that are technically on-brand in isolation but operationally untracked — no clear approval chain, no version lineage, no traceability back to the original brief. The generation is faster, but the governance is absent. As one analysis put it, the organizations that build their AI-ready operational framework first and then adopt tools within that framework will outperform those that adopt tools first and try to impose order afterward. The same principle applies to creative operations: AI doesn't fix fragmentation. It pressurizes it.

The shift: from stacking tools to replacing seams

The argument here is not that creative teams should use fewer tools for the sake of simplicity. It's that the actual cost center in modern creative operations is the connective tissue between tools — and that this cost is now larger than the inefficiency of any individual tool in the stack.

The most expensive minutes in a production workflow are not the ones spent inside a tool. They're the ones spent between tools: exporting an asset from one system to upload it to another. Copying approval status from an email into a project tracker. Rebuilding context for an external reviewer who doesn't have access to the internal system. Re-checking which version is current because three systems show three different states.

What's changing in 2026 is that a category of platform has emerged that eliminates these transitions entirely — not by integrating with other tools, but by consolidating the functions that creative production actually requires into a single environment. Briefing, creation tracking, annotation, approval workflows, versioning, external review, and delivery — all in one place, with one version of truth, one approval chain, and one audit trail.

This is the operating model that MTM was built for. Not as another tool in the stack, but as the environment where the entire production lifecycle lives — from the first brief to the final delivery. Campaign coordination, asset management, collaborative annotation, structured approval workflows, external review links, versioning discipline, and production visibility all coexist in a single infrastructure. The brief author, the designer, the reviewer, the external client, and the production lead all work in the same system, on the same assets, with the same version history.

The value proposition isn't a feature list. It's the elimination of the seams. When the brief, the asset, the feedback, the approval, and the delivery all live in the same place, there's nothing to export, nothing to re-upload, nothing to reconcile. The version is the version. The approval is the approval. The context doesn't get lost because it never left.

For teams that have been stacking tools to solve individual problems, the shift is conceptual before it's technical: stop optimizing individual functions and start eliminating the transitions between them. The tool isn't the bottleneck. The seam is. And MTM is what a creative operations environment looks like when the seams are gone.

The executive question: what would you build if you started from zero?

Every creative operations leader inherits a stack. Rarely does anyone get to design one from scratch. But the thought experiment is useful: if you were building a creative production infrastructure today, with no legacy tools and no sunk costs, would you buy seven separate platforms and wire them together? Or would you start with a single environment where coordination, validation, and delivery already coexist?

The answer is obvious when the question is framed that way. The challenge is that most organizations don't ask it — because the stack was built one procurement decision at a time, each one reasonable in isolation, none of them planned as a system.

2026 is the year that logic inverts. The martech landscape is consolidating. AI is pressurizing fragmented workflows. The cost of the seams is becoming impossible to ignore. The teams that move first toward a unified creative operations infrastructure — where every asset, every approval, and every version lives in one place — will operate faster, with less rework, less confusion, and less of the invisible tax that fragmentation has been quietly extracting for years.

The rest will keep exporting, re-uploading, and wondering where the time went.

FAQ

How many martech tools does the average enterprise use? According to Gartner's Marketing Technology Survey, the average enterprise marketing organization operates 91 distinct tools. The broader martech landscape reached 15,384 commercial solutions in 2025. Despite this volume, utilization rates hover between 33% and 49% depending on the survey year, meaning the majority of purchased capability goes unused.

What is the "fragmentation tax" in creative operations? It's the cumulative cost of moving work between disconnected tools — version confusion, approval bottlenecks caused by context switching, metadata loss during exports, and the time spent reconstructing project context from scattered systems. These costs don't appear in any single tool's analytics but they represent a significant share of total production time.

Doesn't AI solve the integration problem? Not by itself. AI accelerates whatever infrastructure it sits on. If the underlying workflow is fragmented across multiple tools, AI produces more content faster with less governance at each transition point. The result is more assets with less traceability. AI works best when it operates within a unified environment where approvals, versioning, and coordination are already consolidated.

What does "consolidation" mean for creative operations specifically? It means moving from a stack of specialized point solutions — one for briefs, one for assets, one for reviews, one for approvals, one for delivery — to a single platform where the entire production lifecycle coexists. The goal isn't fewer features; it's fewer transitions between systems, which eliminates the version conflicts, context loss, and approval friction that fragmented stacks create.

How does MTM address this? MTM consolidates the functions that creative production actually requires — campaign coordination, asset management, collaborative annotation, approval workflows, external review links, versioning, and delivery — into a single environment. Instead of integrating separate tools, it eliminates the need for them by providing one system where every stakeholder works on the same assets, with the same version history, and the same approval chain.

Sources