Would cutting the DXP or orchestration layer save an organization money?

Removing the orchestration layer often appears to save a license line item but actually transfers work back to developers—who must rebuild integrations, manage personalization in code, and handle frequent content requests—making developer hours the costliest budget line and undermining long-term efficiency.

Uniform blog/When the CMS gaslights the new marketing team

When the CMS gaslights the new marketing team

Turner SatoPosted on May 25, 2026

6 min read

When the CMS gaslights the new marketing team

TL;DR

Many marketing teams inherit restrictive go-to-market architectures that stifle autonomy and increase dependence on developers. True digital agility comes from adding an orchestration layer, like a DXP, to enable self-service, faster campaigns, and effective personalization. The key takeaway: expecting a CMS to drive digital experiences leads to costly bottlenecks—modern teams need a DXP to unlock full marketing potential.

That which stands between what marketers are able to do and what their digital stack allows them to do is architectural, and no one discovers this faster than a new marketing team.

For instance, ninety-three percent of marketers say personalization improves leads or purchases; yet, real experiences demonstrate how little can be accomplished until a personalization tool that works seamlessly with the content management system (CMS) is in place.

The promise versus the queue

Every CMS purchase makes sense when the team evaluating the platform is the same team that will operate it, including the promise of marketing autonomy.

Then turnover happens. The marketing manager who configured the workflows leaves. The developer who built the custom components moves to another project.

The promise of autonomy never comes to fruition. Marketing projects remain in the development queue.

Gaslighting the new marketing team

When the new team inherits this stack, they find a CMS with a perfectly fine webpage editor, but hampered by workflows. The simplest site changes pass through development sprints.

The complexity both confuses and frustrates. The CMS was supposed to be self-service; in the void of autonomy, complex workflows grew and robbed the brand of its potential. Competitive windows close while campaign tickets sit in the backlog.

Under budget pressure, this team is now forced to justify technology costs without fully understanding why the stack works the way that it does.

The disconnect is architectural

New team realization #1: a CMS manages content well but is not designed to orchestrate digital experiences. Uniting company-wide content and data in a workspace where it can be assembled into personalized experiences is the work of an orchestration layer.

The orchestration layer, generally a digital experience platform (DXP), provides the easiest path to usable personalization, testing, and optimization because it connects the CMS to the rest of the architecture without custom integration code or continued dependency on devs. From the DAM to the PIM–even other CMSs–information from external systems can be used to create experiences that drive real engagement and revenue.

Expecting a CMS to act as a full composable experience platform is the true culprit of marketer autonomy as it solidifies marketing’s dependence on development.

Without the orchestration layer, every new tool would require code to integrate. Every software update would need a developer to navigate. Every website change demands a ticket.

The CMS remains an expensive content repository, versus becoming the autonomous publishing engine the DXP enables it to be.

The budget line that looks optional is the one doing the work

After headcount reductions or leadership changes, if an orchestration layer exists, it is often the first budget line questioned.

The CMS license looks essential while the DXP line item looks discretionary. However, the math runs in the opposite direction.

New team realization #2: Removing the orchestration layer does not reduce cost; it transfers cost back to the development team, which resumes its marketing-related workload, including:

Building and maintaining custom integrations
Managing personalization logic in raw code
Fielding tickets for changes as minute as a typo

Which brings us to new team realization #3: developer hours are the most expensive line item in the digital experience budget.

An orchestration layer not only eliminates routine developer dependency, it is what allows the entire architectural investment to perform on budget.

What the new team should know

When a new marketing team inherits a stack only to discover that self-service is unattainable and changes require developer tickets, the diagnosis has to conclude that the CMS is a root cause. When the budget tightens, the judgement can not be that the DXP is superfluous.

Long-term needs must overcome short-term gains. The content management system did what it does best: it managed content. Unfortunately, it was also asked to do the job of a composable experience platform, which is not.

Once organizations recognize this architectural reality, they stop seeking quick resolutions to budget cuts and start asking “What will it take technologically to perform the best on our budget?” A recognition that determines whether the new marketing team wields a powerful marketing platform or remains stuck in the slow trudge of code-heavy development dependence.

Don’t let your CMS gaslight your marketing team. Schedule time now to learn exactly how a DXP reduces developer dependency and unlocks usable personalization and faster campaigns.

FAQs

A CMS primarily manages and stores content but is not designed to orchestrate personalized, multi-system digital experiences; without an orchestration layer (DXP) above the CMS, routine marketing changes and integrations require custom code and developer tickets, so teams remain dependent on developers.