SAP announced on September 15, 2026, that Team Liquid is using SAP Business Data Cloud (BDC) to connect gameplay, wellness, biometrics, and operational data as it competes in World of Warcraft’s Race to World First, which began on August 18, 2026. The deployment extends a collaboration between SAP and Team Liquid that dates to 2018 and turns one of the most punishing events in esports into a live test of what connected data and AI can deliver when decisions cannot wait.
Why Race to World First Is A Data Problem
Most esports tournaments resolve in hours. However, Race to World First can require teams to compete continuously for weeks against the most complex raid encounters ever designed, with fatigue, stress, recovery, and coordination shaping outcomes. At the same time, coaches make calls in real time. As Benjamin Blau, Chief Process and Information Officer at SAP, wrote in a companion blog, at that level, performance is no longer just about mechanics. It is about endurance, and endurance creates a data challenge.
That challenge has been hard to solve because the relevant signals lived in separate systems. Combat logs, gameplay metrics, wearable-device data, wellness information, and scheduling context each offer insight. Analyzed in isolation, they leave coaches with an incomplete picture of how player condition and in-game execution influence one another. Blau’s framing is instructive. He noted that the next evolution of esports analytics isn’t collecting more data, but connecting it.
What Changes With SAP Business Data Cloud
SAP BDC gives Team Liquid a unified, AI-enriched analytics environment in which coaches, analysts, and performance experts see physical readiness, stress indicators, recovery metrics, scheduling context, and in-game performance together. Live data streams let the coaching staff monitor conditions as they unfold and catch early warning signals before they degrade performance, replacing the separate dashboards and spreadsheets that previously defined the workflow.
Joule adds AI-powered recommendations on top of that foundation, building on the Joule Agents that Team Liquid introduced in 2025. By analyzing trends across gameplay, wellness, and biometric data simultaneously, Joule can flag lengthening reaction times alongside elevated stress and suggest a recovery period before the next progression attempt. It can also compare a current tactic against historical results for the same roster configuration and surface alternatives that have performed better under similar conditions.
“SAP Business Data Cloud allows us to make decisions backed by data rather than intuition during one of the most demanding competitive periods of the year,” said Dr. Jesse Hart, Senior Director of Sports Science and Analytics at Team Liquid.
The Enterprise Parallel
SAP makes it clear that the esports story is a proxy for a broader enterprise challenge, and SAPinsider research shows how far most organizations remain from Team Liquid’s position. SAPinsider’s March 2026 SAP Business Data Cloud benchmark found only 3% of organizations have achieved a unified, governed data layer, while 38% remain in siloed or ad hoc integration states. Adoption is early: 45% are still evaluating SAP BDC, and just 4% have reached broad enterprise adoption.
The research also validates the design choice at the heart of the Team Liquid deployment. Enabling AI and agent-based use cases (26%) now ranks level with SAP S/4HANA transformation (26%) as a top driver for SAP BDC investment. SAPinsider concluded that organizations approaching the platform through an AI-first lens, rather than as a data warehouse replacement, are more likely to unlock transformative value. Where SAP BDC is in production, 43% of adopters report improvements of more than 25% in decision-making speed, and 38% report the same in operational efficiency.
SAPinsider’s 2025 Enterprise Data and Analytics research adds the human dimension. More than 40% of respondents have only partially integrated data across SAP and non-SAP systems, nearly four times the share with seamless, intelligent data availability. Only 11% have reached transformational maturity, with AI-enabled insights embedded into business processes. In enterprise terms, Team Liquid’s wearable and wellness feeds are non-SAP data. Making them work alongside operational data is exactly the integration gap most SAP customers still face.
What This Means for SAPinsiders
Connection beats collection. Team Liquid did not gain insight by gathering more metrics. It gained insight by relating datasets that previously sat apart. Enterprise architects should prioritize cross-domain data products, which 47% of SAP BDC adopters are already building, over incremental reporting.
Design for real-time decisions, not retrospective reports. The value in Race to World First comes from acting on live signals before fatigue affects results. CIOs evaluating SAP BDC should target use cases where latency carries a measurable business cost, such as supply chain disruption or the financial close.
AI amplifies expertise only on a governed foundation. Joule’s recommendations depend on trusted, unified data. With only 12% of organizations at the automated governance level required for AI-driven workloads, ERP program managers should sequence governance investment ahead of agentic AI ambitions.
