Where we win, where we lose, and why
No vendor fits every customer. Three scenarios where Dx5 is the cleanest answer, two where we fit with caveats, and two where another vendor is the honest call.
The credibility test most vendor pages fail
Most vendor pages position the vendor as the answer to every question, so experienced buyers discount the claims automatically. Naming where another vendor fits better is rarer, and more useful to read.
We would rather lose an evaluation we are a structural mismatch for than win it and watch the implementation stall.
Three scenarios where the architecture fits structurally
Each of these is won by a specific structural property, not by a feature count. The property is named on the card, with the customers already running that pattern.
One platform, not two
Components live in the SharePoint you already run, so there is no parallel store, identity model or audit perimeter to procure and certify. Removes six to twelve months before content work starts.
Microsoft-365 regulated enterprise · MagVenture, LSEG
Experts never leave Word
The authoring surface is the tool SMEs already use, with DITA applied behind the scenes. No XML editor to roll out to people who author a few hours a year, which is where most programs stall.
SME-heavy author population · medical writers, regulatory, engineering
Every deployment, one product line
SharePoint Online, national clouds, SharePoint Server on-premise, hybrid and air-gapped. SaaS-only vendors are disqualified on the first call in these environments.
Sovereign, on-premise or air-gapped · EASA, Canadian Nuclear Safety Commission, EDA
Two scenarios where we are right with conditions attached
These are the scenarios where DitaExchange is the better answer than most alternatives but where the case requires a condition to hold. If the condition holds, we are the cleanest fit; if it does not, the comparison opens up.
Migration from a desktop authoring tool FrameMakerMadcap Flarelegacy desktop authoring The organization has run a desktop authoring tool (typically FrameMaker, sometimes MadCap Flare or older equivalents) for years.
Why we win, with caveat for organizations that are also on Microsoft 365, the Word-based authoring path is the lowest-friction migration. SMEs move from a familiar tool (Word, used outside FrameMaker) to the same tool with a CCMS ribbon.
The caveat the technical-writing team that was using FrameMaker loses FrameMaker.
Cross-language, cross-jurisdiction labeling at large pharma Global CCDS / SmPC / USPI estate, multi-region regulatory affairs Large pharma with global labeling estate. CCDS feeding SmPC, USPI, local pack inserts and patient information leaflets across 20+ markets and as many languages.
Why we win, with caveat the SharePoint-native architecture, the component-level approval posture, and the structured-content publishing pipeline match the four capabilities a CCMS has to deliver for SPL / IDMP / eCTD.
The caveat large pharma typically has a regulatory information management (RIM) system already in place, Veeva Vault RIM or equivalent.
Two scenarios where we are the structural mismatch
These are the scenarios where DitaExchange is the wrong answer. We are happy to say so on the first call. The CCMS field has credible answers for both patterns; we are not one of them.
Not on Microsoft 365, no plan to move there Google Workspacepure cloud-native stacksnon-SharePoint substrates The organization runs on Google Workspace, on a pure cloud-native stack with no Microsoft estate, or on a sovereign content platform that is not SharePoint.
Why we are the wrong answer the SharePoint-native architecture forces a Microsoft commitment that does not exist today and that the organization has actively decided against.
Who is the better answer a cloud-native DITA CCMS that matches the customer's existing substrate. Heretto is a strong fit for software-documentation and developer-content organizations on a cloud-native stack.
Vendor-operated-everything preference Customers who would rather not own the content substrate The customer prefers a SaaS posture where the CCMS vendor takes operational responsibility for the platform as well as the application. The IT department would rather not own the substrate;
Why we are the wrong answer the SharePoint-native architecture deliberately puts the substrate in the customer's hands. Identity is the customer's Entra ID;
Who is the better answer any cloud-native SaaS DITA CCMS. Heretto, Paligo, and MadCap IXIA's cloud deployment (IXIA CCMS) all fit this preference cleanly.
How to use this page
Find the row that matches your situation. It tells you what the first conversation with us will be about, and how quickly it gets to the architecture.
| If your situation matches | What the early-stage conversation looks like |
|---|---|
| One of the three "where we win" scenarios | We are likely the structural fit and an early-stage conversation will land on architecture quickly. The six structural questions in Choosing a CCMS are the next step. |
| One of the two "where we are the better answer with caveats" scenarios | The conversation will need to test whether the caveat holds for your organization. We are happy to do that openly; the worst outcome is to discover the caveat does not hold in month three of an implementation. |
| One of the two "where another vendor is the honest answer" scenarios | We will say so on the first call and point you towards the vendors who are the structural fit. The links in the cards above are reasonable starting points; the field has more options than we have written about. |
| None of these seven patterns cleanly | The conversation is worth having anyway: the seven cover most of what we see, but not all of it. |
Frequently asked questions
Our documentation is tightly coupled to PLM, ERP and CAD data. Are we in the wrong place?
Probably. Bluestream XDocs has narrowed to a manufacturing-first position, with integrations into the industrial stack: PLM, ERP, CAD, parts catalogs. If that coupling is the priority, their focus is a genuine advantage and we do not claim to match it. We fit the same manufacturer better when the content carries regulatory weight as well as product weight, and the estate is standardized on Microsoft 365.
Managed translation at industrial scale is the center of our program. Does that change the answer?
Yes. RWS is a language-services company, and Tridion Docs is coupled to RWS translation memories and managed translation at volume. For an estate translated into many languages that is a real strength. Dx5 reduces translation cost the way any component CCMS does, by translating an approved component once and reusing it, and it works with the supplier you already have. If translation operations are the program, weight Tridion.
Our deliverables are heavily designed print. Who is better at that?
Quark. Decades in typesetting, and QuarkXPress alongside the publishing platform, give it strength in complex layout that we do not match. Dx5 publishes Word, HTML and XML from the component library, which suits regulatory and technical output well and design-led output less well. If the page design is the deliverable rather than a rendering of the content, that is a Quark conversation.
Discovery and search across a large content estate is our priority. Is that a fit?
Weight Contiem. Where retrieval across a large estate is the requirement, its semantic-search capability is a genuine differentiator. We take a different bet on the same problem: DxChecker enforces terminology, metadata and cross-reference rules at the source, so what feeds search is consistent before anything retrieves it. That is a different capability, not a cheaper version of the same one.
Our shortlist includes MadCap IXIA for the depth of its DITA tooling. How do you answer that?
We do not out-tool the specialist DITA vendors and do not try to. MadCap IXIA, formerly IXIASOFT, has a long track record in DITA tooling and a large enterprise reference base. Dx5 covers the standard capabilities: components, content references, conditional profiling, controlled vocabulary, audit trail. What we compete on is the Microsoft-native footprint and Word as the authoring surface, not toolchain depth.
Honest scope first, vendor pitch second
Tell us which of the seven scenarios you match and we can say straight away whether the conversation is worth having. The wrong vendor is a five-minute call, not a two-month cycle.
