The DXP Scorecard — Independent Platform Evaluation
Independent Platform Evaluation
Scored on implementation experience
Not vendor briefings
v1.4 · 187 criteria · 10 categories

Scoring Methodology

We decided to give away the recipe. Every score on this site is produced by a structured 187-item framework, and we're publishing all of it: every criterion, every weight, every composite formula. No black box.

Evaluating platforms?

You deserve to see exactly how they're being judged. Not just the scores.

You're a platform vendor?

You deserve to understand why you scored the way you did and what would move the needle.

Making a decision?

You should be able to stress-test our logic against your own priorities.

If you find this framework useful and want to use it in your own evaluations, go ahead. All we ask is that you credit us.

Last updated April 2, 2026

Framework Version
v1.4
Current
Total Criteria
187
Scored items
Categories
10
Scored dimensions
Platforms Scored
37
Headless CMS, Traditional DXP, Traditional CMS

Score Bands

All 187 criteria produce a 0–100 score. These bands define what each range means.

90-100Best-in-class. Industry-leading capability.
75-89Strong. Production-ready, minor gaps only.
60-74Adequate. Functional with known limitations.
40-59Weak. Significant gaps, workarounds required.
20-39Poor. Barely functional, extensive custom work needed.
0-19Absent, broken, or no evidence found.

Composite Scores

Raw category scores are combined into composites that drive the dashboard charts. This is how a platform's position on the bubble chart and detail panels is determined.

Capability ScoreX-axis position

Overall platform capability across content management, features, architecture, and AI enablement

Cat 1 ×0.25Cat 2 ×0.3Cat 3 ×0.25Cat 10 ×0.2
Cost-to-Feature EfficiencyY-axis position

Value delivered relative to total cost of ownership

Cat 5
Build ComplexityBubble size

Difficulty and effort required to implement

Cat 6
Maintenance BurdenRing color

Ongoing operational and upgrade overhead

Cat 7
Platform VelocityTrend indicator

Release momentum, ecosystem health, market trajectory

Cat 4
Use-Case FitDetail panel

Suitability for specific use case categories

Cat 8
Compliance & TrustDetail panel

Platform-level regulatory compliance, security certifications, data governance, and authoring UI accessibility

Cat 9
Capability formula: (Cat 1 × 0.3) + (Cat 2 × 0.4) + (Cat 3 × 0.3) weighted to reflect that platform capabilities (Cat 2) have broader differentiation than foundational CMS features or architecture alone.

Category Reference

Every scored criterion, organized by category and sub-category. Categories 1–4 are publicly visible; 5–9 require a free account. Item weights reflect relative importance within each category's weighted average.

1
Core Content Management

Fundamental content modeling, authoring, and delivery capabilities

14 items
1.1Content Modeling
1.1.1
Content type flexibility
How broadly you can define custom data structures — field types available, nesting depth, and whether schemas can be defined in code.
1.0×
1.1.2
Content relationships
How well the platform models connections between content entries, including bidirectional links, reference filtering, and graph-style traversal.
1.0×
1.1.3
Structured content support
Whether content can be built from reusable components and nested blocks rather than monolithic page documents.
1.0×
1.1.4
Content validation
The richness of rules that prevent invalid content from being saved or published — required fields, regex, cross-field, and custom validators.
0.8×
1.1.5
Content versioning
Whether editors can compare version history, roll back changes, schedule publications, and manage draft/published states independently.
1.0×
1.2Authoring Experience
1.2.1
Visual/WYSIWYG editing
How close the editing experience is to the actual rendered output, and how much visual control editors have without engineering help.
1.0×
1.2.2
Rich text capabilities
The power and extensibility of the inline text editor — custom marks, embeds, paste handling, and whether output is portable across frontends.
0.8×
1.2.3
Media management
How well the platform handles image, video, and file assets — including transforms, focal point, metadata, and organizational structure.
1.0×
1.2.4
Real-time collaboration
Whether multiple editors can work on the same content simultaneously without data loss or manual coordination to avoid conflicts.
0.8×
1.2.5
Content workflows
The depth of publish approval chains — customizable stages, role-based routing, scheduled transitions, and full audit history.
1.0×
1.3Content Delivery
1.3.1
API delivery model
Whether the platform exposes a well-designed REST and/or GraphQL API with flexible querying, filtering, sorting, and pagination.
1.0×
1.3.2
CDN and edge delivery
Whether content is served via a global CDN with fine-grained, per-entry cache invalidation and configurable TTL controls.
0.8×
1.3.3
Webhooks and event system
How reliably and configurably the platform notifies external systems of content events — payload filtering, retries, and debug tooling.
0.8×
1.3.4
Multi-channel output
Whether content is structured and delivered in a channel-agnostic way that supports web, mobile, and other surfaces from a single model.
0.8×
2
Platform Capabilities

Extended platform features beyond core content management: personalization, search, commerce, analytics, localization, DAM, editorial tooling, marketing, and integration depth

30 items
2.1Personalization & Experimentation
2.1.1
Audience segmentation
Whether the platform can define distinct audience segments based on behavioral, demographic, or contextual attributes without external tooling.
1.0×
2.1.2
Content personalization
How natively the platform swaps content variants for different audiences, without requiring a separate personalization service to orchestrate.
1.0×
2.1.3
A/B and multivariate testing
Whether the platform supports running controlled experiments — A/B tests and multivariate — to compare content or UX variants with statistical rigor.
0.8×
2.1.4
Recommendation engine
Whether the platform surfaces algorithmically or rule-based product and content recommendations to visitors as a native capability.
0.6×
2.2Search & Discovery
2.2.1
Built-in search
Whether the platform includes a configurable search engine that editors can tune without deploying a separate search infrastructure.
1.0×
2.2.2
Search extensibility
How extensively the built-in or integrated search can be customized — indexing fields, ranking signals, facets, and result filtering.
0.8×
2.3Commerce Integration
2.3.1
Native commerce
Whether commerce functionality such as cart, catalog, and checkout is built into the platform rather than requiring third-party integration.
0.8×
2.3.2
Commerce platform integration
How well the platform connects to leading commerce engines — Shopify, Salesforce Commerce, commercetools, SAP — for real-world production use.
1.0×
2.3.3
Product content management
Whether the platform is optimized for managing product copy, attributes, enrichment, and catalog content at scale.
0.8×
2.4Analytics & Intelligence
2.4.1
Built-in analytics
Whether the platform includes its own analytics dashboard for content performance, visitor behavior, and engagement metrics.
0.8×
2.4.2
Analytics integration
How easily the platform connects to external analytics tools and surfaces data inside the CMS for editorial decision-making.
0.8×
2.5Multi-Site & Localization
2.5.1
Multi-site management
Whether managing multiple distinct sites, regions, or brands in a single instance is a supported workflow rather than an architectural workaround.
1.0×
2.5.2
Localization framework
Whether the platform has a structured locale model — content inheritance, translation state tracking, and fallback rules — built into the core.
1.0×
2.5.3
Translation integration
How well the platform integrates with human translation vendors or machine translation services to move content through localization workflows.
0.8×
2.5.4
Multi-brand governance
The degree to which multi-brand permissions, shared component libraries, and publishing guardrails are enforced at the platform level.
0.8×
2.6Digital Asset Management
2.6.1
Native DAM capabilities
Whether the platform includes a purpose-built digital asset library with metadata management, versioning, rights tracking, and usage attribution.
1.0×
2.6.2
Asset delivery & CDN optimization
Whether the platform delivers assets through a CDN with on-the-fly image transforms, format conversion, and responsive sizing without external tooling.
1.0×
2.6.3
Video & rich media management
Whether the platform can natively host, transcode, and stream video and rich media assets without requiring a separate video platform.
0.8×
2.7Authoring & Editorial Experience
2.7.1
Visual page builder & layout editing
Whether editors can visually assemble and lay out pages using drag-and-drop components with a live preview of the published result.
1.0×
2.7.2
Editorial workflow & approvals
Whether content can be routed through configurable multi-step review and approval chains before publication.
1.0×
2.7.3
Publishing calendar & scheduling
Whether editors have a calendar view of upcoming content and can schedule publish, embargo, or expire content at specified times.
0.8×
2.7.4
Real-time collaboration
Whether multiple authors can work on content simultaneously with live presence, inline comments, and conflict prevention.
0.8×
2.8Marketing & Engagement
2.8.1
Forms & data capture
Whether the platform includes a native form builder with conditional logic, progressive profiling, and CRM/marketing integration on submission.
0.8×
2.8.2
Email marketing & ESP integration
Whether the platform can send or orchestrate email campaigns natively or via deep integrations with enterprise ESPs.
0.8×
2.8.3
Marketing automation
Whether content interactions can trigger automated marketing workflows like drip campaigns, lead scoring, or nurture sequences.
0.8×
2.8.4
CDP & customer data integration
Whether the platform connects to a CDP to unify customer profiles and power personalization with real-time audience data.
0.8×
2.9Integration & Extensibility
2.9.1
App marketplace & ecosystem
The size and quality of the platform’s official integration marketplace, including partner ecosystem depth.
1.0×
2.9.2
Webhooks & event streaming
Whether the platform can reliably push content events to external systems via configurable, secure webhooks.
1.0×
2.9.3
Headless preview & staging environments
Whether editors can preview unpublished content on any headless frontend via shareable links before committing to publish.
1.0×
2.9.4
Role-based permissions & governance
Whether the platform supports granular custom roles with field-level, content-type, and environment-scoped permissions.
1.0×
3
Technical Architecture

API design, security, infrastructure, and developer experience

17 items
3.1API & Integration
3.1.1
API design quality
How well-designed the platform APIs are — consistency, versioning strategy, RESTful or GraphQL conventions, and overall developer ergonomics.
1.0×
3.1.2
API performance
How fast and reliable API responses are at production scale, including latency, caching behavior, and rate limiting approaches.
0.8×
3.1.3
SDK ecosystem
The quality and breadth of official SDKs, typed client libraries, and code-first tooling available across programming languages.
1.0×
3.1.4
Integration marketplace
The size and quality of the pre-built connector and plugin ecosystem for common third-party tools and enterprise integrations.
0.8×
3.1.5
Extensibility model
Whether the platform exposes hooks, plugins, or extension points that allow custom behavior to be added without forking core code.
1.0×
3.2Security & Compliance
3.2.1
Authentication
The strength of identity and authentication options — SSO, SAML, OAuth 2.0, MFA, and programmatic API key management.
1.0×
3.2.2
Authorization model
The granularity of role and permission models — who can view, edit, publish, or delete specific content types, spaces, or environments.
1.0×
3.2.3
Compliance certifications
Whether the platform holds externally audited certifications that validate its security posture for enterprise procurement requirements.
0.8×
3.2.4
Security track record
The platform's historical record of handling security vulnerabilities — responsible disclosure, patch velocity, and severity of known CVEs.
0.6×
3.3Infrastructure & Reliability
3.3.1
Hosting model
Whether the platform's infrastructure model — SaaS, PaaS, or self-hosted — aligns with enterprise reliability, sovereignty, and control needs.
0.8×
3.3.2
SLA and uptime
The strength of contractual and documented uptime guarantees, SLA tier definitions, and incident communication practices.
1.0×
3.3.3
Scalability architecture
How the platform behaves under sudden traffic spikes — auto-scaling behavior, global distribution, and capacity management controls.
0.8×
3.3.4
Disaster recovery
Whether the platform provides automated backups, point-in-time recovery, and documented RTO and RPO commitments.
0.8×
3.4Developer Experience
3.4.1
Local development
How smooth the inner-loop developer experience is — local setup speed, emulators or stubs, hot reload, and dev environment parity.
1.0×
3.4.2
CI/CD integration
Whether the platform integrates cleanly into CI/CD pipelines — preview environments, content migrations, and automated deployment gates.
0.8×
3.4.3
Documentation quality
The depth, accuracy, and usability of official documentation including API references, step-by-step guides, and real-world code examples.
1.0×
3.4.4
TypeScript support
The quality of TypeScript type definitions and type-safe SDK support throughout the developer experience.
0.8×
4
Platform Velocity & Health

Release momentum, ecosystem health, and market trajectory

13 items
4.1Release Cadence
4.1.1
Release frequency
How frequently the platform ships meaningful improvements — features, performance updates, and bug fixes — to production.
1.0×
4.1.2
Changelog quality
Whether release notes are detailed, clearly communicated, and structured to help developers understand the scope and impact of each change.
0.8×
4.1.3
Roadmap transparency
Whether the vendor publicly shares a product roadmap that gives customers confidence in the platform's future direction and priorities.
0.8×
4.1.4
Breaking change handling
How the platform handles breaking API or schema changes — versioning windows, deprecation notices, and automated migration tooling.
1.0×
4.2Ecosystem & Community
4.2.1
Community size
The size of the active developer and practitioner community across forums, GitHub, Discord, Slack, Stack Overflow, and events.
0.8×
4.2.2
Community engagement
How actively the vendor engages with community questions, feature requests, bug reports, and open-source contributions.
0.8×
4.2.3
Partner ecosystem
The breadth and quality of certified implementation partners and system integrators with verified production experience.
0.8×
4.2.4
Third-party content
The volume of community-created learning resources — tutorials, blog posts, open-source starters, templates, and video content.
0.6×
4.3Market Signals
4.3.1
Talent availability
How easily organizations can hire experienced developers and practitioners for this platform in the general job market.
1.0×
4.3.2
Customer momentum
Signals of healthy customer growth — published case studies, analyst recognition, net new logo announcements, and review site ratings.
0.8×
4.3.3
Funding and stability
The vendor's financial health and structural stability — funding runway, revenue signals, ownership structure, and assessed longevity risk.
0.8×
4.3.4
Competitive positioning
How clearly the platform differentiates itself and maintains a defensible competitive position against its closest direct alternatives.
0.6×
4.3.5
Customer sentiment
Aggregated user ratings and community feedback from G2, Capterra, TrustRadius, Reddit, and review forums — reflecting real-world satisfaction across both technical and editorial stakeholders.
1.0×
5
Total Cost of Ownership

Licensing, implementation, and operational cost signals

11 items
5.1Licensing
5.1.1
Pricing transparency
Whether pricing tiers, feature inclusions, usage limits, and overage rules are clearly documented without requiring a sales conversation.
1.0×
5.1.2
Pricing model fit
Whether the pricing model — seat-based, usage-based, flat, or consumption — aligns with how typical teams actually use the platform.
1.0×
5.1.3
Feature gating
How many enterprise-essential features are locked behind higher tiers, inflating effective cost for realistic production use cases.
0.8×
5.1.4
Contract flexibility
The flexibility of contract terms — availability of monthly options, multi-year discounts, and ease of adjusting capacity up or down.
0.8×
5.1.5
Free / Hobby Tier
Whether the platform offers a usable free or developer tier that enables genuine prototyping and evaluation before committing.
0.8×
5.2Implementation Cost Signals
5.2.1
Time-to-first-value
How quickly a new team can go from account creation to a working content-driven application in a real project context.
1.0×
5.2.2
Typical implementation timeline
The typical calendar time and team composition required for a standard production implementation at a mid-market scale.
0.8×
5.2.3
Specialist cost premium
Whether platform expertise commands a meaningful salary or consulting rate premium above general web development market rates.
0.8×
5.3Operational Cost Signals
5.3.1
Hosting costs
The all-in infrastructure cost at scale — bandwidth, storage, compute, and required add-on services — beyond the base license.
0.8×
5.3.2
Ops team requirements
How large a dedicated operations team is required to keep the platform secure, healthy, and performant in production.
0.8×
5.3.3
Vendor lock-in and exit cost
How difficult and costly it is to migrate away — data export completeness, API portability, proprietary dependencies, and switching friction.
1.0×
6
Build Simplicity

How easy it is to implement and get started — higher scores mean simpler builds

10 items
6.1Learning Curve
6.1.1
Concept complexity
How intuitive the platform's core concepts are for a developer encountering them for the first time, before any training.
1.0×
6.1.2
Onboarding resources
Whether the vendor provides structured onboarding — quickstarts, tutorials, sandbox environments, and interactive guided paths.
0.8×
6.1.3
Framework familiarity
Whether the platform uses mainstream languages, frameworks, and patterns that most developers already know and can apply immediately.
0.8×
6.2Implementation Complexity
6.2.1
Boilerplate and starter quality
How well the official starter templates and boilerplate generators reduce initial project setup friction and accelerate time to first feature.
0.8×
6.2.2
Configuration complexity
How much configuration is required before the platform is usable, versus sensible out-of-the-box defaults that work for most cases.
0.8×
6.2.3
Data modeling constraints
Whether the data modeling layer imposes constraints or conventions that require workarounds for common real-world content patterns.
1.0×
6.2.4
Preview and editing integration
How easily developers can wire up live preview and in-context visual editing in a frontend application without platform-specific complexity.
0.8×
6.3Team & Talent
6.3.1
Required specialization
Whether the platform demands hard-to-hire specialist skills or whether any competent full-stack developer can be productive quickly.
1.0×
6.3.2
Team size requirements
The minimum viable team size needed to build, ship, and sustain a production project on this platform.
0.8×
6.3.3
Cross-functional complexity
How much cross-functional coordination — between developers, designers, content editors, and ops — the platform's model inherently demands.
0.6×
7
Operational Ease

How easy it is to operate, upgrade, and maintain — higher scores mean less burden

10 items
7.1Upgrade & Patching
7.1.1
Upgrade difficulty
How painful and risky major version upgrades are — including breaking change frequency, migration tooling, and required downtime.
1.0×
7.1.2
Security patching
Whether security patches are applied automatically by the vendor (SaaS) or require manual operator action with associated downtime risk.
1.0×
7.1.3
Vendor-forced migrations
Whether the vendor has a history of forcing customers through disruptive platform migrations — infrastructure, API version, or product EOL.
1.0×
7.1.4
Dependency management
How much ongoing effort is required to keep platform plugins, modules, and runtime dependencies current and mutually compatible.
0.6×
7.2Operational Overhead
7.2.1
Monitoring requirements
How much observability, alerting, and monitoring infrastructure the team must build and maintain around this platform.
0.8×
7.2.2
Content operations burden
The editorial overhead of day-to-day content operations — publishing bottlenecks, approval delays, broken workflows, or fragile processes.
0.8×
7.2.3
Performance management
How much ongoing engineering effort is required to keep the site performant — cache tuning, image optimization, and query analysis.
0.6×
7.3Support & Resolution
7.3.1
Support tier quality
The responsiveness, expertise, and reliability of vendor support at standard enterprise contract tiers during real production incidents.
0.8×
7.3.2
Community support quality
How effective the community forum, Stack Overflow, and GitHub issues are for resolving real implementation problems without vendor support.
0.8×
7.3.3
Issue resolution velocity
How quickly the vendor and community resolve reported bugs and regressions between initial identification and confirmed fix delivery.
0.8×
8
Use-Case Fit

Suitability for specific use case categories

56 items
8.1Marketing Sites
8.1.1
Landing page tooling
Page builder capabilities, template system, marketer self-service, drag-and-drop layout, component library for marketing
1.0×
8.1.2
Campaign management
Campaign content workflows, scheduling across channels, campaign-level analytics, content calendaring, multi-channel coordination
0.8×
8.1.3
SEO tooling
Meta title/description management, sitemap generation, structured data support, redirect management, URL management, canonical handling
1.0×
8.1.4
Performance marketing
Form handling, CTA management, conversion tracking integration, landing page optimization, lead capture
0.8×
8.1.5
Personalization and targeting
Whether the platform can deliver targeted content variants to different audiences without requiring a separate personalization engine.
1.0×
8.1.6
A/B testing and experimentation
Whether marketers can run content experiments directly within the platform with statistical reporting and winner selection.
1.0×
8.1.7
Content velocity
How quickly a marketing team can go from brief to published page using templates, reusable blocks, and streamlined approval flows.
1.0×
8.1.8
Multi-channel publishing
Whether content can be authored once and delivered across web, email, social, mobile, and other channels through structured models.
0.8×
8.1.9
Marketing analytics integration
How well the platform surfaces content performance data from analytics tools directly within the editorial interface.
0.8×
8.1.10
Brand and design consistency
Whether the platform enforces brand guidelines through locked style tokens, approved components, and restricted overrides.
0.8×
8.1.11
Social and sharing integration
Whether the platform manages social preview cards, social publishing workflows, and user-generated content embeds natively.
0.8×
8.1.12
Marketing asset management
Whether the platform provides or integrates with a DAM layer tuned for marketing asset volumes, transforms, and rights management.
0.8×
8.1.13
Marketing localization
Whether the platform supports transcreation, locale-specific campaign variants, and regional compliance beyond simple translation.
0.8×
8.1.14
MarTech ecosystem connectivity
Breadth of pre-built integrations with CRM, marketing automation, CDP, and ad platforms for orchestrated marketing workflows.
1.0×
8.2Commerce
8.2.1
Product content depth
PIM capabilities, variant/SKU modeling, rich product descriptions, product media management, attribute management
1.0×
8.2.2
Merchandising tools
Category/collection management, promotional content, cross-sell/upsell content, search merchandising, content-driven discovery
0.8×
8.2.3
Commerce platform synergy
Integration depth with Shopify, commercetools, BigCommerce, Salesforce Commerce; real-time sync; content-commerce blending patterns
1.0×
8.2.4
Content-driven storytelling
Whether the platform supports shoppable editorial content like buying guides and lookbooks that blend rich storytelling with product references.
1.0×
8.2.5
Checkout and cart content
Whether trust badges, upsell banners, and shipping callouts in the checkout flow can be managed from the CMS.
0.8×
8.2.6
Post-purchase content
Whether order confirmation, delivery tracking, product onboarding, and loyalty content can be managed from the CMS.
0.8×
8.2.7
B2B commerce content
Whether the platform handles B2B needs like customer-specific pricing, quote flows, gated catalogs, and technical spec sheets.
0.8×
8.2.8
Search and discovery content
How well the platform enriches search results with content, manages search landing pages, and blends editorial with product results.
1.0×
8.2.9
Promotional content management
Whether sale banners, countdown timers, and promo messaging can be scheduled with time-based activation and channel targeting.
0.8×
8.2.10
Multi-storefront content
Whether a single CMS instance can serve multiple storefronts with shared product content but storefront-specific editorial.
1.0×
8.2.11
Visual commerce and media
Whether the platform supports 360-degree views, video, AR/3D models, and image hotspots for product detail pages.
0.8×
8.2.12
Marketplace and seller content
Whether the platform can manage multi-vendor content with seller profiles, contributed descriptions, and content moderation at scale.
0.8×
8.2.13
Commerce content localization
Whether product descriptions, regulatory content, and promotional calendars can be localized per market with currency awareness.
0.8×
8.2.14
Commerce conversion analytics
How well the platform connects content engagement to commerce outcomes like revenue attribution and conversion measurement.
1.0×
8.3Intranet & Internal
8.3.1
Access control depth
Granular permissions for internal content, audience-based content visibility, SSO integration for employees, department-level access
1.0×
8.3.2
Knowledge management
Taxonomy/tagging system, search quality for internal content, content organization patterns, archival/lifecycle, knowledge base templates
1.0×
8.3.3
Employee experience
Portal/intranet capabilities, notification system, social features (likes, comments), employee directory integration, mobile access
0.8×
8.3.4
Internal communications
Whether the platform supports targeted internal communications with read receipts, acknowledgment tracking, and mandatory-read workflows.
1.0×
8.3.5
People directory and org chart
Whether the platform provides employee directory, org chart visualization, and team pages with HR system integration.
0.8×
8.3.6
Policy and document management
Whether policies and SOPs can be managed with version control, audit trails, mandatory acknowledgment, and automated review reminders.
1.0×
8.3.7
Onboarding content delivery
Whether the platform can deliver structured onboarding journeys with role-specific paths and progressive disclosure.
0.8×
8.3.8
Enterprise search quality
Whether search spans the CMS and connected systems like SharePoint and Confluence with AI-powered relevance and faceting.
1.0×
8.3.9
Mobile and frontline access
Whether deskless and frontline workers can access content via native mobile apps with offline support and push notifications.
0.8×
8.3.10
Learning and training integration
Whether the platform integrates with LMS platforms or provides native micro-learning with completion tracking and certification.
0.8×
8.3.11
Social and collaboration features
Whether the platform supports employee engagement through comments, forums, peer recognition, polls, and community spaces.
0.8×
8.3.12
Workplace tool integration
How deeply the platform integrates with Microsoft Teams, Slack, and Google Workspace for embedded content and notifications.
1.0×
8.3.13
Content lifecycle and archival
Whether the platform enforces content freshness with automated review dates, stale flagging, and archival workflows.
0.8×
8.3.14
Internal analytics and engagement
Whether the platform measures internal content effectiveness with departmental views, search analytics, and adoption dashboards.
0.8×
8.4Multi-Brand / Multi-Tenant
8.4.1
Tenant isolation
Content separation between brands/tenants, configuration isolation, brand-level settings, data isolation guarantees
1.0×
8.4.2
Shared component library
Cross-brand reusable content blocks, global templates with brand overrides, design system support, shared media library
1.0×
8.4.3
Governance model
Central admin capabilities, brand-level autonomy balance, approval hierarchies across brands, global policy enforcement
1.0×
8.4.4
Scale economics
Per-brand cost increment, operational overhead per additional brand, licensing model for multi-brand, shared infrastructure efficiency
0.8×
8.4.5
Brand theming and style isolation
Whether each brand maintains its own visual identity through theme tokens applied at the tenant level while sharing components.
1.0×
8.4.6
Localized content governance
Whether translation and compliance workflows can be configured at the brand-plus-locale intersection.
1.0×
8.4.7
Cross-brand analytics
Whether content performance can be viewed both per-brand and in aggregate across the entire portfolio.
0.8×
8.4.8
Brand-specific workflows
Whether approval chains, review stages, and scheduling can be configured independently per brand while remaining centrally auditable.
0.8×
8.4.9
Content syndication and sharing
Whether corporate content can be syndicated to child brands with controlled override points for local adaptation.
1.0×
8.4.10
Regional compliance controls
Whether compliance rules like GDPR consent and data residency can be configured per brand or region with publishing guardrails.
0.8×
8.4.11
Design system management
Whether a federated design system can be maintained centrally with brand-level extensions and version-controlled updates.
0.8×
8.4.12
Cross-brand user management
Whether user roles and permissions can be managed centrally across brands while allowing autonomous brand-level administration.
1.0×
8.4.13
Multi-brand content modeling
Whether content types can be shared globally but extended per brand without forking the base model.
0.8×
8.4.14
Portfolio-level reporting
Whether executive reporting spans the brand portfolio with freshness tracking, SLA adherence, and cost allocation.
0.8×
9
Regulatory Readiness & Trust

Platform-level regulatory compliance, security certifications, data governance operations, and accessibility of the authoring interface

11 items
9.1Data Privacy & Regulatory
9.1.1
GDPR & EU data protection
Whether the vendor has documented GDPR compliance as a data processor — DPA availability, SCC coverage, and DSR automation tooling.
1.0×
9.1.2
HIPAA & healthcare compliance
Whether the vendor offers a Business Associate Agreement and has published HIPAA-compliant configuration guidance for healthcare deployments.
0.8×
9.1.3
Regional & industry regulations
Compliance posture beyond GDPR — including CCPA, FedRAMP, LGPD, PIPEDA, APPI, and sector-specific regulatory certifications.
0.6×
9.2Security Certifications
9.2.1
SOC 2 Type II
Whether the platform holds a current SOC 2 Type II report from an accredited auditor, covering the in-scope cloud infrastructure.
1.0×
9.2.2
ISO 27001 / ISO 27018
Whether the platform holds ISO 27001 and/or ISO 27018 certifications that are actively maintained through annual surveillance audits.
0.8×
9.2.3
Additional certifications
Additional compliance certifications the platform holds beyond SOC 2 and ISO — such as PCI DSS, CSA STAR, FedRAMP, or HITRUST.
0.6×
9.3Data Governance
9.3.1
Data residency & sovereignty
Whether customers can contractually and technically restrict where their data is stored and processed to specific regions or jurisdictions.
1.0×
9.3.2
Data lifecycle & deletion
Whether the platform provides tools for content retention policy automation, right-to-erasure workflows, and deletion confirmation certificates.
0.8×
9.3.3
Audit logging & compliance reporting
Whether the platform logs admin actions, content changes, and authentication events with sufficient retention and fidelity for compliance audits.
0.8×
9.4Platform Accessibility
9.4.1
Authoring UI accessibility
Whether the authoring interface meets WCAG 2.1 AA for keyboard navigation, screen reader support, and color contrast ratios.
1.0×
9.4.2
Accessibility documentation
Whether the vendor publishes a VPAT or Accessibility Conformance Report documenting accessibility compliance for enterprise procurement.
0.6×
10
AI Enablement

Platform-native AI capabilities: content generation, agentic workflows, semantic search, personalization, developer extensibility, and AI governance

15 items
10.1AI Content Creation
10.1.1
AI text generation & editing
Whether the platform generates or suggests text — copy, summaries, rewrites — using AI as a native part of the authoring experience.
1.0×
10.1.2
AI image & media generation
Whether AI can generate, transform, or enrich visual assets and media inside the platform without external tooling.
0.8×
10.1.3
AI translation assistance
Whether AI accelerates translation workflows natively inside the platform while preserving brand voice and content structure.
0.8×
10.1.4
AI metadata & SEO automation
Whether AI automatically generates SEO-critical metadata — titles, descriptions, alt text, tags — to reduce manual editorial overhead.
0.8×
10.2AI Workflow Automation
10.2.1
AI-assisted content operations
Whether AI assists with routine content operations — tagging, routing, scheduling, bulk enrichment — without requiring manual editor effort.
0.8×
10.2.2
Agentic workflow automation
Whether the platform supports AI agents that autonomously execute multi-step content workflows end-to-end without constant human hand-holding.
1.0×
10.2.3
Content intelligence & insights
Whether AI surfaces actionable insight about content performance, gaps, and health to guide editorial priorities.
0.8×
10.2.4
AI content auditing & quality
Whether the platform can audit large content volumes for quality, brand compliance, and accessibility problems using AI rather than manual review.
0.8×
10.3AI Search & Personalization
10.3.1
AI/semantic search
Whether the search layer understands semantic meaning and query intent, and whether content is indexable for RAG and LLM applications.
1.0×
10.3.2
AI-powered personalization
Whether the platform uses AI/ML to determine which content to serve to which audience in real time, beyond static rule-based segmentation.
1.0×
10.4AI Platform & Extensibility
10.4.1
MCP server availability
Whether the platform exposes a Model Context Protocol server so AI agents can natively read, write, and orchestrate content operations.
0.8×
10.4.2
Bring your own AI model/key (BYOM/BYOK)
Whether organizations can supply their own LLM API keys or connect custom models rather than being locked into the platform vendor’s AI provider.
0.8×
10.4.3
AI developer extensibility & agent APIs
Whether the platform provides APIs, SDKs, and tooling purpose-built for AI agent consumption and LLM application development.
0.8×
10.4.4
AI governance, safety & audit trails
Whether the platform provides audit trails, brand guardrails, and safety controls to govern AI-generated content before it enters the publishing pipeline.
1.0×
10.4.5
AI observability & usage analytics
Whether teams can monitor AI usage, costs, and quality trends within the platform to manage AI operations at scale.
0.6×

Confidence Levels

Each scored item carries a confidence level indicating the quality of evidence available.

HIGH

Verified directly from official documentation, changelogs, or hands-on evaluation.

MEDIUM

Assessed from public sources, community reports, or partial documentation.

LOW

Inferred from limited or indirect evidence. Treat with caution.

INFERRED

No direct evidence found. Score estimated from analogous features or category norms.

Use it, just credit us. This framework is open and reproducible. If you adopt it for your own platform evaluations, please attribute it to the DXP Scorecard at dxpscorecard.com. Found an error or have a correction? Submit feedback All substantive corrections are reviewed and applied before the scorecard is updated.