The engineer who owns the nightly master data job cares about one thing now: whether the job they are on call for sits on a release train aimed at Agentforce 360. Its survivorship rules decide which customer address wins, and the systems reading the output are a billing platform and a warehouse that nobody in the CRM team has ever logged into.
The release gives a partial answer. Salesforce says it will "rapidly integrate" the Informatica stack, including data integration, quality, governance and unified metadata for Agentforce, plus a single data pipeline with MDM on Data 360, embedding what it calls "this system of understanding" into the Salesforce ecosystem [4]. Four products are named as beneficiaries: Data 360, MuleSoft, Agentforce 360 and Tableau [5]. Every one of them is a Salesforce property [16]. Six Informatica capability areas crossed over in the deal, from catalog through privacy to MDM [11], and the roadmap language attached to them points inward.
Salesforce does say the wider metadata view pulls context and lineage across every system, not just Salesforce [6], and that Informatica will keep supporting and integrating with its partner ecosystem [7]. Set that beside Informatica CEO Amit Walia's own framing, which promises to accelerate the company's mission as the "Switzerland" of AI-powered data management and, in the next breath, sells the benefit of "a single vendor that unites applications, trusted data and AI agents" [8]. Both positions are in one quote [12], and only one of them will survive a prioritisation meeting.
There is also a clock. Salesforce expects accretion on non-GAAP operating margin and non-GAAP EPS within 12 months, which it says is a full year sooner than it committed at deal announcement [9]. Add the year back and the original commitment was roughly 24 months [10]. Pulling that in by half is a fine thing to tell investors and a useful thing for customers to read roadmap decisions against, because integration effort that serves Agentforce and margin arrives before integration effort that serves neither.
So here is the grid worth drawing before the account team calls. One axis: does the workload's downstream consumer sit inside Salesforce or outside it. Other axis: is the capability named in the four-product integration plan [5] or not. Inside and named, you are the customer this deal was built for. Inside and unnamed, ask for sequencing. Outside and named is the uncomfortable box, and MDM lives in it: the hub you run for non-Salesforce consumers is the thing being reshaped around Data 360 [4]. Outside and unnamed is benign neglect, where the honest ask is maintenance commitments, support response times, and a priced migration option you hope not to use.
Teams often assume their estate is Salesforce-centric because the CRM is where the executives look, but the pipelines tell a different and checkable story: count the downstream systems that read your golden records each week, and count how many of them are Salesforce-native. That ratio, not seat counts and not agent activity, tells you which box you are in and how specific the roadmap answer needs to be before your next renewal.
