Content Value Chain
Content Value Chain — Capability Map

Research Reports

This report is part of the Content Value Chain capability map — an ongoing, evidence-graded research project checking what marketing and content platforms actually document, not what their marketing pages promise. Each category we publish breaks one part of the content operating stack into specific, testable capabilities, then checks every vendor's own public documentation against each one, using a five-tier evidence scale from Verified to Unknown. We don't rank vendors or declare a winner — the matrix shows what's documented, capability by capability, so you can weigh it against what actually matters for your team.

What you're reading here answers one question: what these platforms could do, based on what's publicly documented — the Licensed ceiling. It doesn't answer whether any of it is actually switched on in a specific organization's instance, or whether teams use it day to day — those are separate questions (Enabled, Practised), and they can only be measured inside a real stack, not from public documentation. That's the deeper version of this same assessment: the Content Value Chain diagnostic runs the identical evidence discipline and five-tier scale against your own tools instead of the open market.

It's the same framework behind the Content Value Chain book; this is the field research underneath it, published as we do it.

Framework coverage map

Where the research sits in the system

The Content Value Chain is a dependency structure, not a menu of options — each layer is built on the one before it, from diagnosing what's broken (Diagnosis) through to sensing and reacting to the market (Market Environment). Seven layers, sixteen named components between them — each component is one specific, book-chapter-sized piece of a content operation, like "Brand LLM / AI Brand Governance" or "Universal Taxonomy."

Every report we publish picks one component and breaks it into a handful of specific, testable capabilities — concrete claims like "does this platform enforce brand rules while content is being generated, or only after" — then checks every vendor's own documentation against each one. A highlighted component below has at least one published report; the rest are components we haven't researched yet, not components that don't matter. Altogether, the framework breaks down into 103 specific, testable capabilities spread across 13 of its components — the ones where "does this product do X" is a fair, checkable question. Two more categories work differently: Failure Modes Map and Market Environment are diagnostic and market-context lenses rather than product capabilities, so they're part of the framework but never vendor-graded the same way. Any single report only ever covers one component's worth of that — a handful of capabilities, checked against a handful of vendors — which is what this map is actually tracking: how much of the 103 is covered so far, and how much is still ahead.

01

Diagnosis

Failure Modes Map

Surface variance, drift, and automation theatre before they compound under AI scale.

02

System Model

Content Factory (Ch.2)Service Lifecycle (Ch.3)Content Value Chain (Ch.4)

Shift from production pipeline to value creation system.

03

Structural Infrastructure

Universal Taxonomy (Ch.5)Atomic Content (Ch.9)Pattern Library (Ch.10)

Make content reusable by design — a shared vocabulary, atomic units, and reusable patterns.

04

Execution Infrastructure

Digital Backbone (Ch.11)DAM Memory Bank (Ch.12)

Connect workflow, routing, telemetry, DAM, and memory so the system can operate as one.

05

Control Systems

Insight Engine (Ch.6)AI Agent Org Chart (Ch.7)AI Strangler Facade (Ch.8)Brand LLM / AI Brand Governance (Ch.13)Decision Domain Map (Ch.14)

Govern AI execution and human judgment at scale through clear ownership and decision boundaries.

06

Activation Layer

Variant Ledger (Ch.15/16)

Track every variant in production, measure outcomes, and feed signal back into the system.

—

Market Environment

Market Environment

The external context the system operates in — competitors, analyst coverage, and market signals outside your own stack.

Diagnostic

Licensed, Enabled, Practised

Want to know if this is true for your own stack?

Every report in this library answers what's Licensed — what your tools could do, based on public documentation. The real question is what's actually configured in your instance, and whether your team's day-to-day workflow goes through it or around it. That's the Enabled and Practised half of this assessment, and only your own stack can answer it.

A Content Value Chain diagnostic runs this same evidence-graded check — the same primitives, the same five-tier scale — against what your organization is actually licensed for, has configured, and genuinely uses in practice.