The Amplification Effect: why AI multiplies the data errors already in your portfolio

The problem is not the model

Every week, another portfolio company somewhere comes to its board with an AI initiative. A new forecasting engine. An automated churn predictor. An AI-assisted pricing layer. The ambition is real, the vendor is credible, and the business case looks compelling on paper.

Then, six months later, the project stalls. Not because the model was wrong. Because the data feeding it was.

This is not a fringe outcome. It is what happens whenever a model is pointed at data nobody has checked. The failure mode is rarely the algorithm. It is the foundation underneath it.

The gap between what AI leaders achieve and what most portfolio companies actually get from AI is not a model gap. It is a data gap.

What the Amplification Effect actually means

There is a comfortable assumption buried in most AI business cases: that the model will work with whatever data exists, smooth out the inconsistencies, and surface something useful anyway. That assumption is wrong, and it is expensive.

AI does not fix a shaky data foundation. It amplifies it.

Consider how it plays out. A portfolio company has a CRM that sales reps update inconsistently. Customer segments are miscoded. Deal stages mean different things to different teams. Individually, these are nuisances. A finance director knows to discount the pipeline report by a certain percentage. A head of sales knows which reps are reliable and which are not. The errors sit quietly, managed by institutional knowledge.

Then an AI layer goes on top. Now those errors are not sitting quietly. They are being read as signal. The model is learning from them, weighting them, and distributing its conclusions across every downstream decision, with the implied authority of a model behind them. The finance director no longer knows to apply a discount. The output looks precise. It is not.

Garbage in, garbage amplified. The phrase, and the idea behind what we call the Amplification Effect, is adapted from Dr. Gurpinder Dhillon, speaking on the Robots and Red Tape podcast.

The same dynamic shows up when AI agents go live before their data is ready: the build happens before anyone verifies that the data can carry it.

Where AI projects actually break

The cross-system gap

Most data quality conversations focus on individual systems. Is the CRM clean? Is the ERP accurate? But AI projects do not live inside one system. They pull from CRM, ERP, HRIS, and finance data simultaneously, and they break in the gaps between those systems, not inside any one of them.

A customer lifetime value model needs clean customer records from the CRM, clean revenue records from the ERP, and a consistent definition of what a customer actually is across both. If those definitions do not match, and nobody has checked whether they do, the model is doing sophisticated arithmetic on a flawed premise.

A green score inside one platform is not readiness. It is one system telling you it is happy with itself.

The readiness gap is wider than most assume

Only 8% of businesses say their data is fully ready to support AI at scale (Dun & Bradstreet AI Momentum survey of 10,000 businesses, November 2026). That gap, between strategic intent and operational reality, is where AI budgets go to die.

Very few organisations are ready to run AI agents in production, and the barrier is rarely model capability, compute or talent. It is the quality and lineage of the data.

The constraint is the foundation, not the build on top of it.

The exit dimension operating partners cannot ignore

The Amplification Effect is not only an operational problem. It is an exit problem.

Weak data and KPI reporting is a recurring finance problem at exit. Value-creation initiatives that cannot be traced clearly into reported EBITDA compress exit value when a buyer’s diligence team cannot verify the numbers. An AI initiative that ran on bad data does not just fail to create value. It can actively obscure the value that exists, because the outputs are not auditable and the inputs are not defensible.

A buyer’s operating partner will ask how the AI-driven pricing model was built and what data it was trained on. If the answer is uncertain, the multiple conversation gets harder.

For EU-domiciled or EU-selling portfolio companies, there is a compliance dimension layered on top: the EU AI Act sets data governance and documentation requirements for high-risk AI systems. That is not a problem to leave until the rules bite. The build time is now.

The survey before the build

A structural engineer does not start a renovation by knocking down walls. They survey the building first. They find out what can carry load and what cannot, before any capital is committed to the build on top.

Committing AI budget to a portfolio company without knowing whether the data can support it is the same bet, just more expensive when it stalls at month six.

DataTruth is the survey before the build. A Truth Score Read compares exports from two or more of the company’s systems, record by record, and says in a signed memo whether the data can actually carry the AI plan. The output is one board-ready number, the Truth Score™ (a score out of 100 for how far the data can be trusted), with a Leverability read on the AI in question (which AI ideas you can use now, after fixes, or not at all) and the cross-system red flags. It scores the gaps between CRM, ERP and HR, which is where AI projects actually break, and produces a banded score that an operating partner can drop into an IC deck to compare companies on a single scale.

Every platform vendor now ships some version of a readiness score. But a vendor score tends to point to buying more of that vendor. DataTruth sells no AI, no software and no implementation, and never fixes what it finds, so it has no stake in what the answer is.

Clarity before capital. That is the sequence that protects the multiple.

Before the next AI budget

If you have an AI initiative in the portfolio and you are not certain the data can carry it, a Truth Score Read tests it against the company’s own records before the budget is committed.