The rebrand that actually matters
On April 24, 2026, Adobe quietly replaced its flagship Experience Cloud with CX Enterprise, a fully agentic platform. The star feature: persistent "Coworkers" that orchestrate creative, marketing, and customer-experience tasks across systems 24/7 toward measurable business outcomes.
The rebrand is not cosmetic. Adobe did not add an AI layer to existing workflows. They rearchitected the product around a fundamentally different premise: that the primary user of an enterprise marketing platform is no longer a human doing tasks inside the tool. The primary operator is an AI agent doing tasks across tools, with humans approving, reviewing, and steering. If you were already an Adobe Experience Cloud customer, your account has been auto-migrated. The Coworker tile is already waiting in your dashboard.
This is significant because Adobe's stack already sits inside most enterprise marketing organizations. The CRM integrations, asset libraries, analytics pipelines, and email platforms are already connected. Deploying a Coworker does not require a new vendor relationship or a new data integration project. You are turning on agents inside infrastructure that already knows your business.
What a Coworker actually is
A Coworker is a persistent AI agent built on top of Adobe's Firefly and Sensei AI stack, connected to the full CX Enterprise suite. It operates differently from any AI tool most marketing teams have used before.
Persistent memory across campaigns and quarters. A Coworker remembers last quarter's A/B test results, which creative variants underperformed, which email subject lines caused unsubscribes, and which audience segments responded best. It brings that context into every new campaign it plans without you having to re-brief it.
Read and write access across your marketing stack. Depending on the permissions you grant, a Coworker can read from your CRM, write to your email platform, pull creative assets from DAM, update campaign settings in the marketing automation tool, and post results to Slack. You define the scope. It operates within it.
A single business objective, not a task queue. This is the key design difference. You do not assign a Coworker tasks. You assign it an outcome. Example: "Increase trial-to-paid conversion by 18% this quarter." The Coworker figures out what tasks to do in service of that outcome each week, proposes them, and executes after you approve.
Escalation only when the guardrails you set require it. You define what decisions need human review. Everything else runs autonomously. A well-configured Coworker should interrupt you two or three times per week, not twenty.
15-minute deployment playbook
Log in and find the CX Enterprise tile. Adobe has auto-migrated all existing Experience Cloud customers. Look for the blue CX Enterprise badge in the top navigation. If it's not there, check your admin settings - rollout is complete but some enterprise accounts may need a manual enablement toggle flipped by your Adobe rep.
Create your first Coworker and give it one clear objective. Resist the temptation to give it multiple goals. One objective, measurable by a single metric, for one quarter. The Coworker will self-define its weekly task list in service of that objective. You review and approve the list before it runs for the first time.
Connect your CRM and email platform. One OAuth click for each. If your team already has the Experience Cloud CRM connector enabled, the Coworker inherits those permissions automatically. No additional IT ticket required.
Review the agent's first weekly plan. After connecting tools, the Coworker analyzes your existing data and proposes five to seven specific actions for week one. Read each one. Approve the first three. Reject or defer the others with a note explaining why. This teaches the Coworker your priorities faster than any briefing document would.
Approve and let it run for 7 days. The Coworker executes the approved actions, logs every step, and returns at the end of the week with a performance summary and a proposed plan for week two. Your review of the week-one summary is the most valuable 15 minutes you will spend on marketing operations this quarter.
Distinguish real intent from malicious intent.
hCaptcha User Journeys finds malicious intent across sessions, devices, and apps. Detect intent signals that expose risk before it escalates.
Understand motives, not just outcomes. Book a demo and find out how it works.
Real early results (first 10 days)
Adobe's internal pilot customers ran Coworkers for 10 days before the public launch. The results they shared at the announcement are specific enough to be worth examining carefully, because they reveal something important about where the real value is.
Campaign launch time dropped from 3 to 4 weeks to 4 to 6 days. This is not because the Coworker is faster at the creative steps. It's because the Coworker eliminates the handoff latency between creative, operations, and analytics. Every status meeting, every "waiting for approval" email, every "what's the status of X" Slack message represents time. The Coworker doesn't wait for meetings. It moves on schedule.
2 to 3 times more personalized touches per customer without adding headcount. The Coworker can run 40 micro-segments simultaneously where a human team would run 4. Each segment gets a tailored email sequence, a relevant creative variant, and an optimized send time. The marginal cost of running segment 40 instead of segment 4 is essentially zero.
Marketing teams spending 60% less time in status meetings. When an agent is doing the work and logging every action with a timestamp and outcome, the status meeting ceases to serve its original purpose. The status is already in the Coworker's weekly report. You spend the meeting time on strategy instead of progress updates.
The prompt template
You are a CX Enterprise Coworker. Your single objective this quarter is: Increase trial-to-paid conversion by 18%.
Every Monday you will:
1. Pull last week's trial signups and activation rates from CRM
2. Identify the top 3 drop-off points in the onboarding flow
3. Propose 2 creative tests (email subject lines + landing page variants)
4. Schedule the tests in the marketing automation platform
5. Report results + recommended next action in the #growth Slack channel
Escalate to me only if projected lift is below 5% or if budget >$5k is required.The escalation rule at the bottom is as important as the weekly tasks. It tells the Coworker precisely when to ask for help and when to keep moving. Without a defined escalation threshold, the Coworker either interrupts constantly or runs silently past decisions that actually needed human judgment. Define the threshold before you activate, not after.
Bottom line for operators
Adobe just removed the last structural excuse for slow campaign velocity. For the past decade, the bottleneck in enterprise marketing has not been ideas or budget. It has been coordination: the time it takes for creative to hand off to ops, for ops to hand off to analytics, for analytics to hand off back to creative with results. The Coworker runs that coordination loop without a handoff. It is always in the same meeting, because there is no meeting. It just runs.
The competitive moat for non-technical marketing teams has shifted. It used to be "easy to use." It is now "impossible to outrun." A team running three Coworkers is operating at a pace that no human-only team can match on coordination speed, personalization volume, or test velocity. If your team is still using a project management board to track campaign status, you are not behind on tools. You are behind on operating model.
Immediate action: Log into Adobe Experience Cloud today and create your first Coworker with a single conversion objective. The 7-day pilot will tell you more about your actual marketing bottlenecks than any audit or retrospective you've run in the past year.