ReadingResearchRadarInvestment framework
Sign in / Sign up
← Back to reading
NewsMaterial4 min readDisconfirmAI Editorial

Gaurav Chawla, Vice President of Infrastructure Solutions at Dell Technologies: 'Data Gravity' Causes Enterprise AI Pilots to Succeed but Fail at Scale

Gaurav Chawla, Vice President of Infrastructure Solutions in the Office of the CTO at Dell Technologies, introduces the concept of 'data gravity' to explain why enterprise AI projects succeed in pilot phases but fail during scaling due to hidden costs. He argues that the core obstacle is not model quality, but regulations, data sovereignty, and existing governance architectures that prevent data mobility, meaning AI requires context rather than larger data warehouses.

2026-11-12 10:53 GMT+8

A 2025 report from the Massachusetts Institute of Technology (MIT) indicates that up to 95% of enterprise generative AI pilot projects have little to no quantifiable impact on revenue. The report suggests that model quality is not the primary issue facing enterprises; rather, the gap lies in how AI is integrated into operational workflows. In other words, success in a pilot does not prove that the same system will run smoothly across the entire organization.

Gaurav Chawla, Vice President of Infrastructure Solutions in the Office of the CTO at Dell Technologies, recently proposed a mechanism to explain this gap in a column article: 'data gravity.' His core argument is that most enterprises, after introducing new AI platforms, mistakenly believe that simply aggregating data in one place will allow the intelligence layer above it to function naturally. This may seem reasonable during proof-of-concept stages, but it is almost impossible to achieve at an enterprise-wide scale.

The meaning of data gravity is that the larger the dataset, the higher the cost for the enterprise to move it. Specifically, regulations require certain data to be stored only in specific locations, data sovereignty rules restrict data storage to designated regions, and governance architectures built around specific datasets over the past decades give business units little motivation to migrate data to new platforms, sometimes even lacking legal or compliant pathways to do so. More critically, when attempts are made to separate data from the applications built around it, these applications may suffer severe and costly failures.

Sign in / Sign up
ReadingResearchRadarInvestment framework

Chawla points out that the impact of data gravity is often hidden during the proof-of-concept and pilot stages, as these projects operate only on small, pre-cleaned subsets of data. The true costs borne by enterprises emerge only after AI projects are applied to the vast majority of messy, real-world environmental data. Transmission fees are just one part; latency, bandwidth, security controls, and operational overhead generated after data is processed by AI further drive up overall costs.

The most dangerous aspect of this 'hidden tax' is its timing. Chawla emphasizes that costs often surface 12 to 24 months after procurement is completed and teams are assembled, by which time the initial results brought by AI have already been reported upward, procurement contracts are signed, team personnel are hired, and the company's development direction has been publicly committed externally. At this point, revisiting and modifying the architecture costs far more than designing for data gravity from the beginning.

Chawla believes that the value limitation of enterprise AI is half in computing power and half in data. Token usage and GPU efficiency can tell teams the cost of running models, but they cannot show whether the models possess the context needed to make good decisions. AI models never need raw data poured directly in front of them; what they need is context—the ability to find the correct records, cross-reference with policies, adhere to access rules, and operate based on the latest information, rather than relying solely on data snapshots taken at project initiation.

Therefore, the solution is not a larger data warehouse, but establishing an enterprise-level context layer. This utilizes controlled and consistent mechanisms to discover, connect, and retrieve data across systems and locations, enabling AI to avoid handing every data source to a central repository for processing. Metadata and vector information can assist AI in locating and inferring records restricted by regulations, sovereignty, and ownership that cannot be moved arbitrarily.

Chawla advises enterprises to answer four questions before executing major AI infrastructure investments: Which datasets are restricted from movement by regulations or contracts? Who holds governance rights over each dataset, and what happens when copies exist elsewhere? How do copies stay synchronized as source systems evolve? Can intelligent processing be deployed to the location where data currently resides, or does the architecture require all data to be centralized?

It should be noted that this framework comes from remarks by an executive at an infrastructure vendor, carrying a clear commercial stance. The 'context layer' described by Chawla remains conceptual, without providing specific implementation cases or quantitative effect comparisons. While 'data gravity' serves as an intuitively reasonable explanatory mechanism, its boundaries—such as at what scale or under which industry constraints this mechanism truly constitutes a bottleneck—have not yet been independently verified.

However, attributing the gap from pilot to scale-up to a named architectural constraint, rather than the vague 'data unready,' indeed provides practitioners with a more specific diagnostic starting point. The enterprises that stand to benefit most from AI in the future may be those that support the context required by AI agents when designing data architectures, without needing to move or centrally aggregate data across the entire organization.

Sources

  • techorange.comTechOrange 科技報橘↗
Continue researching →