Architecture Knowledge HubIf your scope statement says "implement GenStudio" and the goal is "content supply chain transformation," you have a gap in the requirements.
GenStudio for Performance Marketing is built around one loop: create content, activate it to paid channels, learn from performance. That's a well-defined slice.
It doesn't own campaign planning. It isn't your governed DAM. It doesn't run cross-team review workflows, owned-channel journeys or asset-level analytics. Each of those is a different system with a different job.
So before build starts, map the loop you're implementing against the chain you were asked to transform. Write down which layers are in scope, which are out, and which system is the system of record for each.
Skip that step and the project "finishes" while planning, DAM and measurement look exactly like they did on day one.
The agentic angle: agents live inside specific products and follow those products' permissions. Adobe's Content Production Agent serves the GenStudio for Performance Marketing loop. No single agent covers planning, the DAM and measurement for you.
Which layers of the chain does your current scope statement quietly leave out?
Agentic angle
Availability changes quickly. Confirm status in your own tenant before you build on any tool below.
Agents sharpen the scoping question instead of removing it. Adobe's agents ship inside specific applications and respect that application's access controls, so an agent in one product can't do the job of a layer that lives in another. GenStudio for Performance Marketing has a Content Production Agent that interprets briefs and produces channel content, plus an MCP tool that exposes ad performance and creative insights. Planning, DAM, journeys and analytics have their own agents elsewhere.
Adobe tools to know
- Content Production Agent (GenStudio for Performance Marketing): interprets briefs and produces on-brand channel content. Beta at the October 2025 announcement; confirm current status.
- GenStudio for Performance Marketing MCP tool (via CX Coworker Gateway): ad performance data and creative insights. Requires an extra entitlement.
- Data Insights Agent (Customer Journey Analytics) and Journey Agent (Journey Optimizer): cover measurement and journeys outside the product's loop.
Best practices
Items marked (Adobe) come from Adobe documentation. The rest are design advice.
- Map each agent to one layer of the chain before you scope, and write down the layers no agent covers.
- Treat an agent's product boundary as a scope boundary in the statement of work.
- Confirm licensing early: agent jobs consume AI credits and need a license, trial or promo SKU. (Adobe)
Sources
- Agentic AI in CX Enterprise Applications
- SiliconANGLE: Content Production Agent in beta
- Adobe MCP servers (CX Enterprise Agentic Tools)