Is $10 trillion in spend data a moat or an AI risk?

Legacy tech equates a $10T proprietary dataset with competitive advantage. But in procurement, outcomes depend on data quality, user adoption, and platform design, not volume alone.

‍

For years, enterprise software vendors have viewed data accumulation as a competitive advantage. In the AI era, that belief has only grown stronger, with larger datasets increasingly positioned as a foundation for better decisions and outcomes.

‍

Vendors, like Coupa for example, have made this claim concrete: agents informed by trillions of dollars in business spend deliver better data, better decisions, and better outcomes.

‍

The quality of an AI agent is only as good as the data feeding it, and data quality is shaped by how it was captured, when it was captured, and on what infrastructure. Those factors matter as much as headline volume, and they raise questions that spend data volume alone cannot answer.

‍

This article breaks down why the quantity of spend data and the quality of AI-driven outcomes are not synonymous and what procurement leaders should be asking instead.

‍

Quantity ≠ Quality

Data quality is not a function of volume. As IBM notes, data quality is assessed through dimensions such as accuracy, completeness, consistency, timeliness, uniqueness, and validity, not raw scale.

‍

That distinction matters here. A large dataset can still be unreliable if it was captured inconsistently, structured unevenly, or assembled over years of changing procurement processes or behavior.

‍

In other words, more data does not automatically mean better decisions. In procurement, the real question is not how much data a vendor has, but whether that data is clean, current, and fit for how teams operate today.

‍

The legacy tech problem

Much of legacy procurement data was built over years of ERP integrations, supplier onboarding, taxonomy decisions, and workflows that were not intentionally  designed for today's AI-driven operating model. As those processes evolved, the underlying data often remained fragmented, inconsistently structured, and shaped by older business rules rather than current reality.

‍

Procurement data is notoriously difficult to standardize. Industry definitions of spend analysis explicitly describe the need to cleanse, normalize, and classify spend data before it can be reliably analyzed.

‍

Coupa's own integration documentation puts it plainly. Connecting procurement workflows across ERP systems means navigating constraints that don't travel well between platforms: supplier names that must be globally unique in one system but not another, payment terms that are optional on one side and mandatory on the other, identifier fields that one system stores as alphanumeric and another expects as numeric. 

‍

Their documentation also acknowledges that "in many cases, a manual reconciliation may be necessary to correct any missing or mismatched data between the two systems." That's not an edge case caveat. It's the stated norm. 

‍

The question procurement leaders should ask isn't how much data does a vendor have? but how was it captured, how consistently was it structured, and does it reflect today's procurement reality, or the habits of a previous era?

‍

‍Can legacy tech buy its way out of legacy?

Legacy tech is buying its way out of legacy because architectural limitations and talent gaps prevent them from building AI fast enough, while agile competitors are threatening their comfortable moats. Technical debt and AI’s ability to minimize switching costs are making legacy software providers acquiring tools they know they can’t build themselves.

‍

Coupa CEO Leagh Turner put it plainly when announcing the Tonkean deal: "To deliver the promise of increasingly autonomous execution…you need three main things: industrial-grade and unified orchestration, best-in-class buyer and supplier workflows, and clean, trusted data."

‍

Integration challenges

Integrating legacy tech into modern systems requires significant data transformation to align older ERP structures, master data, and business rules across platforms.

‍

Key challenges include:

• Data constraint mismatches: Legacy systems enforce different rules (e.g., unique supplier names) than modern platforms, causing integration failures
• Master-data synchronization: Suppliers, cost centers, and projects don't align cleanly across systems
• Error-handling complexity: Integration failures require explicit mechanisms to catch data mismatches
• Custom integration overhead: Organizations must choose integration technology, decide on in-house vs. outsourced support, and manage lifetime maintenance costs

‍

This matters because outcomes don't come from data sitting in a platform. They come from successful platform adoption. A system that requires months of implementation, external consultants, and acquisitions to function as promised creates the adoption barriers that compromise ROI. No dataset, however large, produces better decisions if the teams it's meant to serve have already found workarounds.

‍

Complexity kills adoption, and adoption is what drives outcomes

Gartner projects that by 2027, 40% of enterprises will demote or decommission autonomous AI agents due to governance failures, which is almost inevitable when a platform was never fully adopted in the first place.

‍

Outcomes are driven by process adoption, and when it fails, governance fails with it, purchasing decisions made outside the platform don't get captured or fed back into the system. The dataset grows, but its accuracy doesn't. In short, that’s not a moat, that’s drift. 

‍

Final thoughts

The $10T figure is striking, but procurement leaders are asking sharper questions: not just what a vendor has built, but what it signals about where this is going.

‍

The real shift is toward systems built for clean data at intake, high process adoption, and architecture designed for how procurement actually operates today. Better decisions come from clean data captured at intake, processes teams use consistently, and platforms built for modern procurement rather than retrofitted to keep pace with it.

‍

The opportunity for procurement leaders is clear: prioritize data quality, adoption, and architecture. That's what turns spend data into a genuine competitive advantage in the AI era.