"We're Going All-In on One Vendor" Still Needs a Dependency Map

Angle

A knowledge-graph review this week had to formally document that Salesforce Data 360 is a prerequisite for Salesforce Marketing Cloud Next functioning usefully in the same stack — Marketing Cloud has no profile store of its own and can't execute sends without Data 360 upstream. Buyers who choose 'go all-in on one vendor' specifically to reduce integration risk often stop asking dependency questions once the vendor is chosen, but a single-vendor suite is still a system of internally dependent parts (the same pattern shows up in Adobe's AEP-plus-Journey-Optimizer stack and Oracle's Unity-plus-CX suite) — and if one layer lags or migrates, the layers built on top of it are blocked regardless of which company's logo is on the contract.

Key decision this helps with

Within a chosen vendor's suite, which layers are load-bearing prerequisites for which other layers, and has that internal dependency chain been mapped the same way an integration risk assessment would map dependencies across separate vendors?

Tradeoffs the article will map

• Single-vendor procurement (one contract, one support relationship, marketed as lower integration risk) vs. composable procurement (more visible integration points, but each dependency is a deliberate, contract-visible decision rather than an implicit one)
• Treating a vendor's own internal architecture as a black box the vendor manages vs. asking the vendor directly which internal layers are prerequisites for which, before an outage or migration in one layer becomes a surprise in another

Open questions / uncertainties

• Whether vendors' own internal dependency chains are getting more or less coupled as 2026's platform-bundled-AI-decisioning pattern collapses the CDP and CEP layers further into single systems (Oracle Unity is cited as one example)
• Whether procurement processes anywhere systematically ask vendors to disclose internal-layer dependencies, or whether this remains an unasked question by default

Knowledge-graph nodes this draws from

• vendor.salesforce-data-360
• vendor.salesforce-marketing-cloud
• vendor.adobe-experience-platform
• vendor.oracle