Five AI Marketing Platforms Say They Enforce Brand Rules in Real Time. Here's What Their Own Documentation Actually Backs Up.
We checked Gradial, Writer, Jasper, Typeface and Persado against the same seven brand-governance capabilities, using each vendor's own public documentation and four evidence grades. No vendor briefings, no sales decks. This edition re-grades every cell against the vendors' product and help documentation: 21 of the 35 cells are now Verified. Most of these platforms document how they apply brand rules while content is written. Where they differ most is what happens after it is written.
About this research
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 four evidence grades, 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 the same four grades 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.
Where this fits in the whole 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.
Diagnosis
Surface variance, drift, and automation theatre before they compound under AI scale.
System Model
Shift from production pipeline to value creation system.
Structural Infrastructure
Make content reusable by design — a shared vocabulary, atomic units, and reusable patterns.
Execution Infrastructure
Connect workflow, routing, telemetry, DAM, and memory so the system can operate as one.
Control Systems
Govern AI execution and human judgment at scale through clear ownership and decision boundaries.
Activation Layer
Track every variant in production, measure outcomes, and feed signal back into the system.
Market Environment
The external context the system operates in — competitors, analyst coverage, and market signals outside your own stack.
This report is entirely about the highlighted block — whether AI marketing agents actually enforce brand rules is a Control Systems question, not a content-production one. It assumes the layers below it are already handled elsewhere. A platform can ace this report's matrix and still fail if those foundations aren't in place — which is exactly the kind of gap a diagnostic, rather than a single-category report, is built to catch.
About Brand LLM / AI Brand Governance
That block breaks down into seven specific, testable capabilities — the part of a content operation responsible for making sure AI-generated content actually follows brand and compliance rules, not just approximates them.
BL-1 — Terminology store
The difference between an agent that has your banned-word list and one that's actually blocked from using those words.
BL-2 — Validated-claims library
Whether the agent can catch a specific claim — "proven," "guaranteed," "FDA-cleared" — that needs evidence it doesn't have, not just avoid obviously risky language.
BL-3 — Tone as rules
Whether "brand voice" is a real, versioned setting your team controls, or something baked into a prompt that has to be re-explained — and can drift — every time.
BL-4 — Contextual rules
For a platform selling itself to multinational or multi-brand teams: whether "global" means regionally aware, or just "one voice, everywhere."
BL-5 — Retrieval grounding
The difference between an agent that "knows about your brand" because it was told once, and one that checks your actual source of truth every time it writes something.
BL-6 — Rules applied during generation
Whether brand rules are applied while content is generated, shaping what gets written, or only checked afterwards in review. The sharpest line between vendors that hold rules as separate settings and vendors that hold them as written instructions.
BL-7 — Output checked before release
Whether the platform automatically checks generated content against your rules before it goes live, what it checks, and what happens when content fails the check.
How we chose these seven, and what they're not
These seven capabilities aren't a checklist assembled from vendor marketing pages or category-analyst reports. They come from the book itself: Chapter 13 gives Brand LLM / AI Brand Governance four structural primitives and three functions — retrieval grounding, constraint enforcement, output validation. We restated all seven as something a product either verifiably does or doesn't do, then checked each vendor's documentation against them. A taxonomy built from what vendors already sell would just describe the market back to itself; this one comes from the framework's own architecture, and vendors either match it or don't.
That also means this isn't exhaustive. These seven are the specific claims the book makes about what brand governance actually requires — not a complete inventory of every feature a marketing platform might ship. A vendor can have real strengths (analytics, workflow speed, integrations) that don't appear here at all, because they're not what this component is about. And a vendor with real gaps here can still be the right choice for a team whose priorities sit elsewhere. This report answers one narrow question well. It doesn't answer "which tool should I buy."
That's the difference from a feature comparison. A feature comparison starts from a vendor's own list of what it sells and checks a box when the feature exists. This starts from what the book argues has to be true for brand governance to work, independent of how any vendor names or packages it — which is why every primitive is named by function ("terminology store enforced at generation"), never by a vendor's product name for it. A box only gets checked here when a vendor's own documentation — not its marketing copy — actually backs that specific claim. In the full report, every grade links straight to that documentation: the exact page, the exact sentence it's based on, so you're never taking our word for it either.
How to read the grades
Evidence grade
- Verified — the vendor's own product, help or developer documentation describes the specific mechanism.
- Vendor-claimed — stated on a marketing or product page, without a described mechanism.
- Inferred — reasoned from adjacent evidence, not directly stated.
- Unknown — not found in what we checked. That is not the same as confirmed absent.
A small ◦ marker next to Unknown means a near-miss: the vendor documents something close, but it doesn't meet the capability as defined. The full findings explain what.
How it arrives (shown under Verified grades)
- •Native — the product does it out of the box; you supply only your content, such as a word list.
- •Configured — an administrator fills in named fields or settings the product provides, such as a tone field or a per-channel rule.
- •Assembled — your team would have to build it from generic parts, such as a free-text prompt or custom fields. We never grade Assembled above Inferred, because a capability you have to design yourself is not one the product delivers.
Plan level (where the documentation says so)
- •Higher tier — the product does it, but not on every plan.
- •Add-on — available as a separate purchase.
- •Third-party — needs another product alongside it.
No plan label means it is in the base product, or the documentation didn't say which plans include it.
Where this grading stops
Everything in this report is graded from the outside, from documentation any buyer can read. That sets a limit, and we hold to it. The highest grade here, Verified, means the vendor's own documentation describes the mechanism. It does not mean we have tested it, that it works as described, or that you have it.
We grade three levels in a full assessment. Licensed: what the product can do on the plan you buy. Enabled: what is actually switched on and configured in your instance. Practised: whether your team's day-to-day work goes through it or around it. Public documentation can only answer the first, so that is where the grading in these reports stops. Where a vendor keeps its user guides behind a customer login, the grade stops earlier still, at what its public pages and developer documentation show, and we say so in the findings.
The other two levels can only be measured inside your own stack. That is what the Content Value Chain diagnostic does, with the same capabilities and the same evidence rules.
The matrix
| Capability | Gradial | Writer | Jasper | Typeface | Persado |
|---|---|---|---|---|---|
| BL-1 Terminology store | Inferred | Verified Configured | Verified Configured · Higher tier | Vendor-claimed | Verified Configured |
| BL-2 Validated-claims library | Unknown◦ near-miss | Unknown◦ near-miss | Unknown◦ near-miss | Unknown◦ near-miss | Unknown◦ near-miss |
| BL-3 Tone as rules | Verified Configured | Verified Configured | Verified Configured | Vendor-claimed | Verified Configured |
| BL-4 Contextual rules | Verified Configured | Verified Configured · Higher tier | Verified Configured | Verified Configured | Verified Configured |
| BL-5 Retrieval grounding | Verified Native | Verified Configured | Verified Native | Inferred | Inferred |
| BL-6 Rules applied during generation | Inferred | Verified Configured | Verified Configured · Higher tier | Vendor-claimed | Verified Configured |
| BL-7 Output checked before release | Verified Configured | Inferred | Inferred | Verified Native | Verified Native |
Re-graded 14 October 2026 against the vendors' product, help and developer documentation. 27 of the 35 grades changed from the first edition (20 August 2026, graded from marketing pages). Every changed cell is marked in Evidence & sources below.
What the documentation actually shows
This report was first published in August 2026, graded from what the five vendors say on their marketing pages. In October we went back to their product, help and developer documentation and re-graded every cell with the same rules we now use in every report. 27 of the 35 grades changed...
Unlock the full findings and evidence
Add your name, email and current vendor to open the full findings and the full source-by-source evidence list on this page.
Licensed, Enabled, Practised
Want to know if this is true for your own stack?
Three of these five platforms document an automated check of AI output against your brand rules, and only one documents rewriting the copy until every rule passes. If your team runs one of them — or is evaluating one — the real question is what's actually configured in your instance, and whether your team's day-to-day workflow goes through that gate 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 capabilities, the same four evidence grades — against what your organization is actually licensed for, has configured, and genuinely uses in practice.