DiscoverCX
Get demo
Guide · 10 minute read

What is a CDP?
And why CCMS isn't enough anymore.

A content delivery platform picks up where a traditional CCMS stops — adding a real-time API, a customer-facing portal, and AI-ready output so one source of truth can serve every modern channel.

CCMS → CDP, the short version

A CCMS stops at file output. A CDP keeps your content live, typed, and queryable.

CCMS = authoring + storage + workflow + file outputs

CDP = authoring + storage + workflow + real-time API + portal + AI-ready output

The four channels that broke CCMS

Traditional CCMS were designed when "content delivery" meant PDFs and a help center. Then four new channels showed up — and none of them fit:

  1. Customer portals. Self-service experiences that need search, personalization, cases, and community — all backed by structured content but rendered as a real product, not a doc site.
  2. In-product help. Help drawers and copilots embedded directly in your software, requiring API access to the content (not iframes to a docs site).
  3. Salesforce Knowledge / Einstein. Same content surfaced in agent consoles, customer Experience Cloud, and Einstein-powered chat — all needing structured input, not PDFs.
  4. AI assistants and RAG. Grounding LLMs in authoritative content, where stale or untyped data produces hallucinations.

Each new channel demanded structured, real-time, queryable access. CCMS tools that output only files force you to bolt on a delivery layer per channel — a tax that compounds with every new surface.

The CDP architecture

A CDP is four layers in one platform:

  • Author — DITA, Markdown, HTML in the editor of choice.
  • Manage — Git-backed repository, versioning, workflow, audit, translation.
  • Deliver — Real-time REST + GraphQL API, typed schemas, semantic JSON, SDK.
  • Discover — Customer portal with search, personalization, cases, community.

See the four-layer architecture in detail on the platform page.

When to upgrade

You need a CDP (and a regular CCMS isn't enough) when any of these are true:

  • Your content has to feed three or more channels (docs, portal, Salesforce, AI, in-product)
  • A buying committee asks "can you power our AI assistant?"
  • Customer success is copy-pasting docs into Salesforce
  • You're rebuilding a custom portal because no CCMS-vendor portal fits
  • Stale-cache rebuild windows are causing compliance or correctness problems

FAQ

CDP — frequently asked

What is a content delivery platform (CDP)?+

A content delivery platform unifies structured authoring, a content repository, and real-time multichannel delivery in one system. Where a traditional CCMS stops at file output (PDF, HTML), a CDP keeps content live, typed, and queryable through a delivery API — so a single source can power docs sites, portals, in-product help, Salesforce Knowledge, and AI assistants concurrently.

Isn't this just a 'headless CCMS'?+

Headless CCMS is a piece of it — the delivery API. A CDP includes that plus the customer-facing portal layer (search, personalization, cases, community), the AI-readiness layer (semantic JSON, knowledge graph), and the integration layer (Salesforce, ServiceNow, Atlassian). Headless CCMS gives you the pipes. A CDP gives you the destinations.

Why do I need real-time delivery?+

Two reasons. (1) Compliance and correction speed — when a policy or product spec changes, your portal, Salesforce, and AI assistant should reflect it within seconds, not after a nightly rebuild. (2) AI grounding — when your AI assistant cites a topic, the version it cites needs to be the version actually live. Stale caches are a trust problem.

How is this different from a DXP (digital experience platform)?+

DXPs (Adobe AEM, Sitecore, Optimizely) are page-and-experience oriented — built for marketing journeys. CDPs are content-and-component oriented — built for technical and customer content that has to feed many surfaces. DXPs assume a CMS underneath. CDPs replace the CMS for structured content use cases.

Where does this leave my existing CCMS?+

If your CCMS only outputs PDF and HTML, you'll bolt on a delivery layer (custom or third-party) and eventually replace the CCMS when bolt-ons get unmanageable. If your CCMS already speaks API + supports modern integrations + has a portal — you're already on a CDP. We built DiscoverCX as a CDP from day one, so there's nothing to bolt on.

Does a CDP make sense for a small team?+

Yes — if your content lands in more than one place. A 3-person docs team feeding a docs site, Salesforce Knowledge, and an AI assistant benefits from a CDP more than a 30-person team feeding only PDFs. The economic case scales with channels, not headcount.

See the CDP architecture live.

Walk through Author → Manage → Deliver → Discover with a solution engineer in 45 minutes.

Request a demoRead about the platform