NEW: Scale AI Case Study — ~1,900 data requests per week across 4 business units Read now →
Contents
Salesforce
Salesforce became a major data ecosystem vendor by acquisition, not by building. Tableau (2019, $15.7B), MuleSoft (2018, $6.5B), and Informatica (2025, ~$8B) make Salesforce the largest roll-up in the data and integration market. The strategy: buy the leader in every category and extract rent through the Salesforce customer base.
Salesforce isn't usually thought of as a data ecosystem vendor, and yet by total acquisition spend in the data and integration space, it's the largest single buyer of the last decade. MuleSoft for $6.5 billion in 2018. Tableau for $15.7 billion in 2019. Slack for $27.7 billion in 2020-2021 (not a data tool, but worth mentioning for scale). Informatica for approximately $8 billion in 2025. That is more than $50 billion of acquisitions in eight years, much of it pointed straight at the data stack.
In plain English: Salesforce did not build any of its data products. It bought them. The strategy is "buy the category leader, integrate it loosely with the Salesforce customer base, and extract rent through the existing Salesforce enterprise relationship." That strategy has been spectacularly successful as a financial story (Salesforce is one of the largest software companies in the world) and considerably less successful as a product story (Tableau has visibly stagnated under Salesforce ownership, MuleSoft has lost ground to Fivetran and the in-warehouse ELT pattern, and Informatica is being absorbed primarily as raw material for Agentforce).
Salesforce was founded in March 1999 by Marc Benioff (a longtime Oracle executive) along with Parker Harris, Dave Moellenhoff, and Frank Dominguez. The original product was a SaaS-delivered customer relationship management system, sold under the slogan "No Software" — a then-radical pitch that you could run business-critical software entirely in a web browser without installing or hosting anything. Salesforce went public in June 2004 and grew through the 2000s into the dominant CRM platform in the world.
The acquisition era really started in the 2010s. Salesforce spent the early 2010s buying smaller technology companies (Heroku in 2010, ExactTarget in 2013) and the late 2010s buying very large strategic ones. The relevant acquisitions for this wiki:
Alongside the acquisitions, Salesforce also built (and rebranded several times) its in-house data platform. It started life as Customer 360, was renamed to Salesforce CDP, was renamed to Salesforce Genie, and is now called Salesforce Data Cloud. Data Cloud is a customer data platform built on top of Apache Iceberg that integrates with Snowflake, Databricks, BigQuery, and Redshift via "zero-copy" data sharing. The pitch is that Data Cloud lets Salesforce see your warehouse data without physically copying it, then activates that data in Marketing Cloud, Sales Cloud, and Agentforce.
Other Salesforce data and integration products that don't yet have a wiki page:
Salesforce's data strategy is extraordinarily consistent and easy to describe: find the unambiguous leader in a category that touches Salesforce's enterprise customers, buy it at a premium, and use the existing CRM relationship to upsell the acquired product. This is pure roll-up strategy, and it works because Salesforce already has the procurement relationship in place. Adding Tableau to a Salesforce contract is one signature; adding standalone Tableau is a multi-month procurement cycle. The financial logic is iron-clad even when the product logic is mediocre.
The recent twist is AI / Agentforce. Marc Benioff has, since roughly 2023, repositioned essentially all of Salesforce as an AI agent platform. The data acquisitions are being reframed accordingly: Tableau exists to give agents a visualization layer; Informatica exists to give agents clean enterprise data; Data Cloud exists to give agents unified customer context; MuleSoft exists to give agents real-time API connectivity. Whether or not this AI repositioning works commercially, it explains the recent acquisition pattern: Informatica in particular is an Agentforce purchase, not a data engineering purchase.
The data products inside Salesforce are, on the whole, stagnant or declining in product mindshare, even when they remain very profitable. Tableau is the clearest example. At the time of the 2019 acquisition, Tableau was the most exciting standalone BI company in the world, with visible roadmap leadership and a passionate community. Five years later, Tableau is still ubiquitous in Fortune 500 BI procurements and is still slowly losing the conversation to Power BI, to Looker, and to the modern-stack BI tools (Sigma, Hex, Mode, Omni). The pattern is what you'd expect from a category leader inside a roll-up: customers stay because switching is expensive, but new deals slowly tilt away.
Informatica is likely to follow the same pattern. The Salesforce thesis is not "make Informatica a more exciting product"; it is "extract Informatica's enterprise data into Agentforce." Whether that's good for Informatica customers depends on how heavily Salesforce invests in the existing ETL roadmap versus how aggressively it pivots the platform toward Agentforce-shaped use cases. The historical evidence is not encouraging.
The right way to think about Salesforce as a data vendor: it is a financial buyer with a captive distribution channel, not a product company. You buy Tableau or Informatica from Salesforce because you already buy from Salesforce. You don't buy them because you think they're moving faster than the alternatives.
TextQL Ana connects natively to Tableau (reading both Tableau workbooks and Tableau's published data sources as semantic context) and to Salesforce Data Cloud as a data source. For Salesforce-heavy customers, the most common pattern is using TextQL Ana to ground natural-language questions in Tableau's existing semantic models and dashboards, so that business users can ask questions of the same metrics their dashboards already display, without writing SQL or LookML.
See TextQL in action