THE DXP MATURITY MODEL
The DXP has evolved again. See where your platform stands and what it means for your business.
Start with your teamWhich of these statements sounds most like your team?
How are they connected?
Think of Stage 1 as a product, Stage 2 as an architecture, Stage 3 as an operating model, and Stage 4 as an automation cheat code that unlocks when stages 2 and 3 are thoroughly complete. Each stage is defined by a shift in autonomy.
Everything in one box
Where the category began, and legacy vendors originated. Everything is in the vendor's box, and integrations are a costly SI project.
One vendor's content, rendering, roadmap, and only vendor-supported capabilities, all built the vendor's way. The suite promises an all-in-one platform but delivers unshakable dependency.
Time. Integrations outside of the suite are projects priced by the hour. The majority of effort and cost goes into integrations, versus content, design, or personalization.
The power of a connected stack
This DXP unites a set of technologies that together help organizations manage and deliver experiences across channels. The platform enables simpler connections to other platforms.
Best-of-breed systems, front-end freedom, and independent scaling. Teams can replace one system without replacing the others. Orchestration empowers teams to bypass sprints and launch faster. What varies by platform is how systems connect; a difference that determines a team's ability to reach the next stage.
Two ways to be composable
Systems connected point-to-point in code. Sources map to components by hand, per channel. More systems means more code, and the more the stack hardens into the rigidity it was meant to escape.
The same systems are connected by configuration, not code. Sources connect in clicks, data maps visually to components, and content models stay clean because in-context content lives in a composition layer. Marketers compose with content that lives throughout the stack.
Wired: permanent developer capacity. The code "tax" grows with every system and channel and is owed in perpetuity. Orchestrated: the decision to adopt orchestration.
Agents and humans create for agents and humans
With composability and orchestration as the base, importance shifts to operationalizing how humans and agents build together. The DXP remains the structured workspace for experiences.
AI agents can reach other platforms, providing the power to solve advanced use cases through prompts and automations. Content is structured for people and for the answer engines and assistants acting on their behalf. Humans and agents work in tandem, fully governed, and within brand guidelines. The role of AI-enabled creator emerges for those tasked with starting projects from a prompt and managing the experiences through AI.
Trust, at first. Teams review work, monitor the audit trail, and increase autonomy as deemed fit. Agency partners will need a new pricing model when billing for hours drops because the hours required for projects did.
The experience tunes itself
The DXP is a governance hub for self-adapting logic: responding to emerging trends, launching experiences for niche searches, and optimizing elements of the site, app, or agentic experience through continuous testing and personalization.
Optimization is a continuous loop, versus a series of campaign tasks. Humans set objectives, budgets, guardrails, and handle the exceptions the platform escalates. Marketer roles become less hands-on. Agentic capabilities are mastered, and governance and structure are established. Scaling experiences moves to autopilot.
Discipline in Stages 2 and 3 with emphasis on personalization and governance excellence. Even when the building blocks exist, organizational readiness is crucial.
A suite cannot become agentic simply by changing its homepage. Agents inherit the reach of the platform they live on. An agent on a suite automates the suite. Agents in stacks wired together in code can still only automate within the borders of the platform they live on
Teams on suites or on a wired composable stack can avoid paying the perpetual glue tax by embracing orchestration. Adding an orchestration layer will bring teams to Stage 2 in weeks through configuration, secure Stage 3 once governance is in place, and grow into Stage 4 as trust and automation mature.
Eight dimensions by which an organization can assess placement.
Why it matters: An agent's reach is the architecture's reach.
Why it matters: Who can ship without asking is the clearest sign of stage.
Why it matters: The unit of work sets the pace everything else runs at.
Why it matters: Idea to live is the number your competitors are measured on.
Why it matters: A growing share of visits is an agent acting for a person.
Why it matters: Programs fail on variant production and page speed, not intent.
Why it matters: Speed without governance is a liability. Governance without speed is a museum.
Why it matters: How your partner bills tells you which side of the split they're on.
A place to start, by department, plus a test you can run.
Choose the foundation, not the CMS. Composable, orchestration and integrations are the platform. CMS, personalization and analytics are choices on top. Decide the first three first.
Pick a partner who bills for judgment. If the proposal is priced in sprints for integration work, it is a wired build.
Start with one page. Compose it from two sources that exist. No migration required to prove the model.
Move connection from code to configuration. Map one source to one component by configuration and time it. Keep presentation out of content models; volatile content lives in the composition layer.
Decide the governance before the autonomy. Roles, permissions and workflow gates apply to agents the way they apply to people. Write the brand guidelines for AI now.
Name an AI-enabled creator. Someone on the team who will start from a prompt this month.
Start with one workflow. Variants, translations, or SEO and AEO fields. Run it in review mode until checking slows considerably.
Give the agent reach. An agent confined to one repository automates a silo. Expose the orchestrated stack, including the systems the DXP does not own.
Structure content for two audiences. Typed, validated, semantic. The same entry renders a page for a person and clean, citable content for an agent.
Set objectives, budgets and guardrails. Improve conversion on the trial funnel, stay within brand rules, never change pricing copy, and escalate anything with a legal flag.
Build the weekly review. A summary of what changed and why, read by a person who can stop it.
Run the loop on one funnel. Detect, hypothesize, test, promote, repeat. Keep everything else in review mode.
Promote workflows to automations. Events, schedules and signals start work; deterministic where it must be, agentic where judgment is required; everything logged.
Design the escalation path. The exception is the feature. Decide what stops the loop and who hears about it.
A suite that added a generative assistant; names drafting copy inside its own editor as agentic.
The stress test: The agent could not act on a system the vendor doesn't own. It could not create structure, just text. There is no review mode.
A composable stack where one system shipped an agent whose reach ends at its own API. The rest of experience still needs a developer.
The stress test: The agent could not build a page that draws content and data from three external systems.
Classic examples of agents bolted on to a wired stack. Agents unable to create change, work autonomously, or reach outside the platform can never mature to be agentic by definition. Orchestration may not be unglamorous, but it is foundation each evolution depends on.
Ask three questions.
Can the agent act on a system the vendor doesn't own?
Can the agent run in review mode where a marketer can see each change before it lands?
Is the content typed and modeled for an answer engine to cite and an agent to act upon with accuracy?
A platform that passes the vibe check earns the label "agentic". Without these boxes checked, know that your team is investing in a roadmap it has no control over.
How leaders ready their organization for the future
Uniform is composable from origin and is a MACH Alliance member. Orchestration was built by configuration, meaning composability never needed to wired.
Scout, the AI agent, acts across all platforms that Uniform orchestrates. It performs in review or autonomous mode, under the same roles and permissions as a human user. Uniform Code takes a site from prompt to production and makes it editable the same day.
Automations is the programmable layer that turns optimization into a standing loop. Stage 4 represents an industry direction.
A means to understand a marketing organization's future through its tech stack, from a single-vendor suite to a platform that autonomously tunes experiences, and to learn what the next stage requires.
The first-generation digital experience platform: one vendor's content, rendering and roadmap, with integrations sold as projects. The unit of work is the release and time from idea to live is months.
Both use best-of-breed systems. Wired connects them point-to-point in code, so every system adds more code. Orchestrated connects them by configuration, keeps content models clean, and lets marketers compose across sources without a ticket. Only orchestrated leads to the agentic stage.
A platform where agents do most of the work across the stack, and humans approve what ships, with content structured for people and agents acting on their behalf. It requires reach across every system, governance, and structured content.
The building blocks exist: edge personalization and testing, agents, and event- and schedule-triggered automations. The organizational readiness does not. It emerges when Stages 2 and 3 are implemented properly.
No. An agent inherits the reach of the platform it runs on, so agents on a suite or a wired stack are bound by that platform. You can advance stages through orchestration by configuration and governance.
Five foundational capabilities define a DXP: composable from the start, orchestration with visual experience management, integrations, agentic, and edge rendering at scale. The repository and tools are secondary and can come from any vendor: CMS, personalization and testing, and analytics.
Use the picker at the top of this page, or read the "you know you're here when" lists under each stage. The eight dimensions show which one is holding you back.
Ready to unlock your brand's potential?
Let's talk about the stage your company needs
.svg){kind=icon}
.jpg)
