Ben Werth, Chief Executive Officer of Semarchy, posted a response to the SAP-Reltio acquisition announcement on LinkedIn that is worth reading in full if you follow the master data management space. Werth congratulates the Reltio team, acknowledges the pattern forming across the market, and then makes a case for why independent vendors still have ground to stand on. The LinkedIn post does a lot of work in a short space. It is also a reminder that the strategic question being raised here is not small.

Two Acquisitions. One Clear Signal.

SAP announced on March 27, 2026 that it has agreed to acquire Reltio, a cloud-native master data management platform built around entity resolution and what Reltio calls a "golden record" system of context. The deal is expected to close in Q2 or Q3 of 2026. Terms were not disclosed.

Less than ten months earlier, Salesforce agreed to acquire Informatica for approximately $8 billion. That transaction closed in November 2025. Between those two dates, the independent master data management vendor landscape contracted meaningfully at the top.

The stated rationale from SAP is straightforward: Reltio will be folded into SAP Business Data Cloud, the data platform SAP launched in early 2025 as the foundation for AI-driven decision-making. SAP has said Reltio will also remain available as a standalone offering. The integration is meant to feed SAP's AI tools, including Joule and Joule Agents, with trusted, unified data across both SAP and non-SAP systems.

That framing is worth holding onto. SAP is not acquiring Reltio to sell more master data management licenses. SAP is acquiring Reltio because agentic AI needs a data substrate it can trust, and building that substrate from scratch across heterogeneous enterprise environments is genuinely hard. Reltio solved a real problem. That is why SAP bought it.

What Werth Is Actually Saying

Werth's post opens with a clean acknowledgment of the pattern: two recognized names in master data management absorbed by platform giants in under six months. He calls it validation of the importance of data management. That framing is fair. Platforms do not spend billions acquiring categories they think are commoditizing.

But the sharper argument in the post is about roadmap gravity. Werth writes that SAP has said Reltio will remain available as a standalone offering "for the foreseeable future," and takes that at face value. He then adds: "The natural gravity of acquisition means Reltio's roadmap will increasingly reflect SAP's priorities. Informatica's will reflect Salesforce's." That is not a criticism of either acquirer. It is a structural observation about how acquisitions work over time, and it is accurate.

For customers whose data environments are neither SAP-centric nor Salesforce-centric, that gravity is the risk to model. Not whether Reltio keeps a standalone commercial option. Whether the engineering investments, the roadmap sequencing, and the product decisions over the next three to five years reflect the acquired company's customer base or the acquirer's platform strategy.

The Constraint Underneath the Announcements

Both acquisitions are solving the same problem from the platform side: enterprise AI applications are only as reliable as the data they consume. An AI agent that operates on fragmented, inconsistent records produces unreliable outputs. Golden records, entity resolution, and data governance are not back-office concerns anymore. They sit on the critical path for every agentic deployment.

SAP and Salesforce have both concluded that they cannot afford to leave that layer to a third-party vendor whose roadmap they do not control. That is the business logic driving both deals. It is also the constraint that independent master data management vendors now have to work around, or work with, depending on their positioning.

Werth's post argues that independent vendors who stay out of that gravitational pull can serve enterprises who need master data management to work across heterogeneous environments, not just within a single platform's orbit. The argument holds if the independent vendor can demonstrate a credible alternative to both the platform depth that SAP and Salesforce are building and the roadmap certainty those platforms now offer their existing customers.

The DataOps Argument

One section of Werth's post is worth examining on its own terms. He frames Semarchy's differentiation around what he calls DataOps and AI Data Engineering: the idea that governed data assets should be managed the way software assets are managed, with version control, continuous integration and delivery pipelines, integrated development environment support, and AI-assisted design as part of the core platform rather than add-ons.

This is a real architectural choice. Master data management platforms built for the pre-cloud era were largely workflow tools for data stewards. The engineering discipline around data pipelines, governance lineage, and deployment automation has matured considerably since then. Whether that maturity is table stakes for enterprise buyers in 2026, or whether it is a competitive differentiator, depends on what problems those buyers are actually trying to solve.

For regulated enterprises scaling agentic AI, the accountability question is not trivial. If an AI agent makes a decision based on master data, the audit trail for that decision has to exist. Who certified that data version? What governance policy applied at consumption time? Werth's argument is that the answer to those questions requires the same rigor applied to software deployments. That is a defensible position.

What the Remaining Field Looks Like

The market for enterprise master data management still has independent vendors. Some specialize by industry vertical. Some compete on time-to-value and deployment simplicity. Some are building toward the data product model Werth describes, where governed data assets are packaged, versioned, and made available for self-service consumption by applications and AI agents alike.

What changed with these two acquisitions is that the platform comparison is now more complex. A chief information officer evaluating master data management in 2026 has to ask not just which platform has the better technology today, but which vendor's priorities most closely match their own enterprise architecture for the next five years. If that architecture runs heavily on SAP, Reltio inside SAP Business Data Cloud may end up being exactly the right answer. If it does not, the calculus shifts.

The honest version of that question is: whose roadmap am I buying? Every acquisition announcement says the product will remain available. The harder question is whether the engineering investment will follow the acquired product's existing customers or the acquirer's strategic priorities. History on that question is mixed.

The Right Response to Consolidation

Werth's response to the SAP-Reltio announcement is itself worth noting as a model. When two competitors get absorbed by platform giants in under a year, the instinct for remaining independent vendors is often to say nothing and hope customers do not notice the landscape shifted. Werth did the opposite. He named the pattern, acknowledged what customers are losing, and made a public case for where independent platforms fit in the new picture.

That is the right move, regardless of whether you agree with every argument in the post. Enterprises evaluating master data management in 2026 need vendors who think out loud about market structure, not vendors who wait for the dust to settle before deciding what they believe. How a vendor responds when competitors disappear is a reasonable signal for how they will behave when their own customers face uncertainty. Werth chose to engage. That tells you something.

Sources

SAP SE. "SAP to Acquire Reltio: Make SAP and Non-SAP Data AI-Ready." SAP News Center, 27 Mar. 2026, news.sap.com.

Reltio. "A New Chapter for Reltio: SAP to Acquire Reltio to Help Make Enterprise Data AI-Ready." Reltio Blog, 27 Mar. 2026, reltio.com.

Salesforce. "Salesforce Completes Acquisition of Informatica." Salesforce News, 18 Nov. 2025, salesforce.com.

Werth, Ben. LinkedIn post. 30 Mar. 2026, linkedin.com.