Salesforce is one of the most powerful CRM platforms ever built. Hundreds of thousands of organizations run their customer operations on it. And yet, consistently, across industries and geographies, a pattern repeats: organizations deploy Salesforce, invest significantly, and still cannot produce a reliable Customer 360 view. They still cannot connect the dots between what a customer did last week, what they need today, and what the business should do next.
This is not a Salesforce problem. It is a foundation problem. And understanding that distinction is, in my view, one of the most important things a CX practitioner can contribute to an enterprise technology programme.
as what flows into it
The premise of Customer 360 is simple: every team that touches a customer — sales, service, marketing, operations — works from the same complete, accurate picture. In practice, most organizations are nowhere near this. Customer data lives in multiple systems: a legacy ERP, a service platform, a billing database, a marketing tool, a spreadsheet maintained by one person in a department nobody talks to.
When these systems are not governed, records duplicate. Fields are populated inconsistently. The same customer appears three times under three different spellings of their company name. A service agent in one geography cannot see the account history visible to a sales rep in another.
This is where Master Data Management becomes critical. MDM is the discipline — and the technology — that governs how master records are defined, cleaned, deduplicated, and maintained across systems. Without it, no CRM platform, however sophisticated, can deliver a true unified view.
The most widely deployed MDM platforms in enterprise environments include Informatica (now part of the Salesforce ecosystem following its 2025 acquisition), Reltio, Stibo Systems, Semarchy, and IBM MDM — all recognized as Leaders in the 2026 Gartner Magic Quadrant for MDM. Each addresses the same fundamental challenge: ensuring that critical business data stays accurate, consistent, and reliable across every system that touches the customer.
MDM implementation is not a quick project. A full enterprise MDM deployment typically takes 12 to 24 months — longer in regulated industries where data governance requirements add complexity at every stage. The selection process alone, from requirements to vendor decision, commonly takes 3 to 6 months. Implementation, data migration, reconciliation, and adoption can extend well beyond the initial timeline.
This is not a failure of the platforms. It reflects the genuine complexity of harmonizing data that has accumulated across years of organizational growth, system changes, and operational decisions made in silos. The organizations that navigate this well treat MDM not as an IT project but as a business transformation — with executive sponsorship, cross-functional ownership, and a clear connection to the customer outcomes they are trying to improve.
tools do not design masterpieces
Consider a mechanical watch. The engineering inside a masterpiece timepiece — the gears, the escapement, the balance wheel working together in a space smaller than a coin — is a product not of tools alone, but of exceptional craft applied through the right tools. Salesforce is, in this analogy, the watchmaker's bench. Powerful, precise, capable of extraordinary outcomes. But the bench does not design the watch. The people do.
The most consistent failure pattern in enterprise CRM and chatbot programmes is not technology selection. It is the assumption that a programme manager or project manager can carry the full weight of design, system logic, business process, and stakeholder alignment simultaneously. Programme managers are essential — but they coordinate; they do not design the mechanism. What is needed is a carefully aligned set of professionals, each fluent in their domain and genuinely connected to the others.
These roles, working in alignment, are what makes a CRM transformation produce customer outcomes rather than just system deliverables. The investment in skilled, domain-fluent professionals is not overhead. It is the foundation on which everything else is built.
compromise — they are strategy
Enterprise CRM programmes fail most often not because the technology is wrong or the ambition is absent, but because organizations attempt to build everything at once. Full omnichannel. Complete Customer 360. End-to-end automation. All simultaneously. In a system that is not yet clean, with a team that is still learning, on a timeline that does not allow for iteration.
The Agile methodology — which most organizations now claim to follow — exists precisely to challenge this instinct. Start small. Prove value. Build confidence. Iterate. In the context of CX and CRM delivery, this translates directly into a sequenced approach that generates momentum rather than waiting for a perfect state that rarely arrives.
Each of these wins is modest in isolation. Together, they build the clean data, trained team, and proven integrations that make more ambitious programmes possible. And critically, they build the organizational confidence that sustains long-term transformation.
in an unready system?
Agentforce represents Salesforce's most significant AI investment — autonomous agents that act on behalf of sales, service, and marketing teams using the data and workflows inside the Salesforce platform. The capability is genuinely compelling. But the question worth asking before deployment is not "what can Agentforce do?" It is: "what will Agentforce read from?"
Bad data does not produce slightly worse AI results. It produces confidently wrong recommendations. An AI agent reading duplicate customer records, incomplete account histories, and inconsistently populated fields will act on that information — at scale, at speed, and without the human hesitation that might catch the error before it reaches a customer.
Agentforce readiness, as one implementation specialist put it, must be judged by the quality of the commercial system it is entering — not by whether the agent can technically be switched on. The sequence matters: clean data first, unified customer profile second, AI agents on top. Inverting that sequence accelerates the visibility of every existing problem rather than solving them.
For organizations whose focus is rightly on achieving omnichannel consistency and a reliable Customer 360 view, this is not a reason to avoid AI. It is a reason to sequence correctly. The foundation work — data governance, MDM, people alignment, incremental delivery — is not a delay on the path to AI. It is the path.
connecting every layer
In a computer's architecture, the bus is the communication system that connects the processor, memory, storage, and input/output devices. Remove the bus and each component still exists — but they cannot exchange information, cannot coordinate, cannot function as a system. They are parts without a whole.
CX plays exactly this role in a digital transformation programme. Not as the most technical layer. Not as the programme manager. But as the connective tissue that ensures every decision — data, system, people, delivery — is evaluated against a single consistent question: does this serve the customer?
A CX practitioner in a digital transformation programme is not the person who configures Salesforce. They are the person who asks: when a sales rep looks at this customer record, does it tell them what they need to serve that customer well? When a chatbot handles this intent, does the response earn trust or erode it? When we prioritize this sprint, are we building toward the customer outcome or toward the system milestone?
These are not soft questions. They are the questions that determine whether the technology investment produces a customer experience or merely a functioning platform. And they require someone in the room whose primary accountability is the experience — not the architecture, not the delivery timeline, not the budget line.
In network terms: every device on the LAN can be high-performing. Without the right network design, they cannot reliably communicate. CX is the network design.