Informatica, MuleSoft and Data 360 are not competing for the same budget line. Each answers a different question — and together they produce the one thing an AI agent cannot function without.
For years, enterprise technology strategy has been dominated by a deceptively simple objective: get all the data together.
Today, that is no longer enough.
In the age of Agentforce and autonomous AI, an enterprise must answer three much more important questions.
- Can I trust my data?
- Can my systems securely communicate and act?
- Can I transform trusted, connected information into context at the moment a human or an AI agent needs it?
This is how I have come to think about the relationship between Informatica, MuleSoft and Data 360. They are sometimes discussed as though they overlap. They do. But overlap does not mean redundancy.
I see them as three specialized layers of the modern intelligent enterprise.
Informatica establishes trust. MuleSoft establishes connectivity. Data 360 establishes context and activation.
Together they create something far more powerful: trusted context for action. And increasingly, that context is not consumed only by people. It is consumed by AI agents.
The Trusted Context Architecture. Four layers, each answering a different question, ending in governed action.
Informatica: Establishing Trust
The question underneath every AI conversation
Before we discuss AI, agents, personalization or automation, we have to begin with something much less glamorous. Is the underlying data actually trustworthy?
Every large enterprise has accumulated decades of data across ERP systems, CRM platforms, warehouses, lakes, departmental applications, acquisitions, legacy databases, spreadsheets and external sources. The problem is not simply moving that data. The harder questions are the ones underneath it.
- What does this data mean?
- Where did it come from, and who owns it?
- Is it accurate? Is it duplicated?
- What is its lineage?
- Which customer, patient, provider, employee, product or supplier does it actually represent?
- Are we permitted to use it for this particular purpose?
This is where Informatica plays its foundational role. Its strengths in enterprise data integration, cataloging, metadata management, quality, lineage, governance, privacy and Master Data Management give an enterprise something AI desperately needs: a trustworthy understanding of its own data.
What is true, what does it mean, and can I trust it?
That question grows in weight as AI moves from generating answers to making decisions and taking actions. Bad data used for a dashboard is inconvenient. Bad data used by an autonomous agent is consequential.
MuleSoft: Establishing Connectivity
The nervous system of the enterprise
Trusted information sitting inside a governed repository still cannot transform an enterprise by itself. Something has to connect systems, applications, services, APIs, workflows and increasingly agents.
That is the role of MuleSoft, and it solves a fundamentally different problem from Informatica. If Informatica establishes what the enterprise knows, MuleSoft lets the enterprise communicate and transact.
Its API-led architecture is the connective tissue between systems. An EHR needs to communicate with Salesforce. Salesforce needs to communicate with an ERP. A scheduling application needs to reach a contact center. An AI agent may need to call an external service, retrieve information and initiate an operational transaction. Those are not data-management problems. They are connectivity and orchestration problems.
How do I securely connect the systems that know something with the systems that need to do something?
I describe MuleSoft as the nervous system of the enterprise. A nervous system does not determine whether every piece of information is correct, and it does not decide the meaning of every signal. Its job is to transmit signals reliably and rapidly so the different parts of the organism can work together. That distinction matters.
Data 360: Establishing Context
Proximity to action
Salesforce Data 360, formerly Data Cloud, should not be viewed as merely another place to consolidate enterprise data. That undersells it. Its strategic value is its proximity to action.
Data 360 connects structured and unstructured information, harmonizes it, resolves identities, creates unified profiles, generates insights and makes that information available to Salesforce applications, workflows and Agentforce.
Its value is therefore not I have the data. It is I have the right context available at the moment of engagement. That is an enormous distinction.
Consider a patient contacting a healthcare organization. We do not simply need a database containing that patient’s information. We need to understand:
- Who is this person?
- What has happened previously?
- What is happening now?
- What are they likely to need next?
- What permissions govern how their information can be used?
- What action should the human or the AI agent take?
That is context. And context is what turns data into intelligence.
The Architecture
Four layers, four questions
| Layer | Platform | Primary role | Core question |
|---|---|---|---|
| Trust | Informatica | Identity, quality, governance, lineage, metadata, mastered entities | Can I understand and trust this data? |
| Connect | MuleSoft | APIs, system integration, orchestration, secure transactions | Can my systems and agents communicate and act? |
| Contextualize | Data 360 | Harmonization, identity resolution, unified context, activation | Can I put the right information in context at the moment it matters? |
| Act | Agentforce | Reasoning, workflow participation, recommendation, action | Can intelligence safely do useful work? |
The signature model
Trust → Connectivity → Context → Intelligence → Action
This is not a literal sequential pipeline. Modern architectures are rarely that simple. Data 360, for example, can access external platforms through zero-copy patterns rather than requiring all enterprise data to be physically moved into Salesforce.
The model is conceptual. It tells us which problem we are asking each technology to solve. That prevents a common architectural mistake: trying to make every platform solve every problem.
Why the Informatica Acquisition Matters
An architectural gap, not a product gap
Salesforce’s acquisition of Informatica is more interesting than simply adding another product portfolio. It closes an architectural gap.
Salesforce already had extraordinary strengths across CRM, customer engagement, workflow, applications, analytics, integration, Data 360 and increasingly Agentforce. Informatica extends that data strategy farther into the enterprise. Its metadata, catalog, governance, quality, privacy, integration and MDM capabilities provide visibility and trust across systems well beyond Salesforce itself.
This matters most for Agentforce. An AI agent needs more than access to data. It needs to understand what the data represents, whether it can be trusted, where it originated, whether the agent is authorized to use it, what systems it may interact with and what actions it is permitted to take.
The acquisition should be understood through the lens of agents and trusted context, not through the lens of ETL.
From Systems of Record to Systems of Action
What AI actually changes
Enterprise architecture has historically revolved around systems of record. CRM became the system of record for customers. ERP for finance and operations. The EHR for clinical care. Data warehouses for analytics.
AI introduces a different requirement. We are moving toward systems of action.
An agent does not merely retrieve a record. It interprets information. It reasons over context. It invokes tools. It communicates with other systems. It recommends or initiates action. That means the architecture supporting AI must simultaneously provide trusted information, governed access, connectivity, context and action.
No single traditional technology category solves that problem. The combination begins to.
Healthcare Makes the Distinction Obvious
Where the stakes stop being commercial
I see this clearly because I approach technology first as a physician and a healthcare operator, not simply as a technologist.
Imagine an AI agent helping manage a patient with diabetes. That patient’s relevant information might exist across the EHR, claims, laboratory systems, pharmacy systems, Salesforce Health Cloud, wearable devices, call-center interactions, scheduling, marketing engagement, social determinants data and external clinical documents.
Connecting those systems does not create intelligence. Mastering the patient identity does not create intelligence. Placing everything into a data platform does not create intelligence.
Intelligence emerges when we can establish all of the following at once.
- This is the right patient.
- This is trusted information about that patient.
- These systems can securely communicate.
- This is what is happening with the patient now.
- This is the relevant context.
- This is what we should do next.
And critically: this is what we are permitted to do.
The future of enterprise AI will depend as much upon governance of action as governance of data.
Data Governance Is Becoming AI Governance
A new question, reaching into every old discipline
Traditional data governance asked a familiar set of questions. Who can see this data? Where did it originate? Is it accurate? How should it be classified? How long should it be retained?
Agentic governance adds a new dimension. What is an AI agent allowed to do because of what it knows?
That is a profound change, and it reaches into every discipline we already had.
- Lineage becomes relevant to explainability.
- Data quality becomes relevant to AI reliability.
- Identity becomes relevant to personalization.
- Consent becomes relevant to agent behavior.
- API governance becomes relevant to agent actions.
- Master Data Management becomes relevant to determining which real-world entity the agent is actually reasoning about.
Data governance is evolving into AI governance.
The Trusted Context Architecture
Truth alone is no longer sufficient
For years we spoke about the single source of truth. That idea remains important. But in an AI-driven enterprise, truth alone is insufficient. AI needs context.
The same laboratory value can mean very different things depending upon the patient. The same customer transaction can mean very different things depending upon history. The same operational event can require completely different actions depending upon permissions, identity, timing and business circumstance.
Competitive advantage therefore moves from possessing data to creating trusted context at scale.
- Informatica helps establish enterprise truth.
- MuleSoft makes the enterprise accessible and connected.
- Data 360 turns enterprise information into actionable context.
- Agentforce converts that context into intelligent action.
Salesforce provides the environment where humans, applications, data and increasingly autonomous agents come together. That is far more consequential than another data-platform acquisition. It is the emergence of a new enterprise architecture.
Govern what you know.
Connect what you have.
Understand the context.
Then allow intelligence to act.
That is the real power of Informatica, MuleSoft, Data 360 and Agentforce working together.
