Where AI projects actually break: the cross-system gap PE firms keep funding through

The failure point nobody is auditing

Ask any operating partner where AI projects stall and you will hear the same answers: the model was not right, the vendor overpromised, the team was not ready. Rarely will you hear the honest answer, which is that the data could not hold the weight. And within that, the failure almost never sits inside a single system. It sits in the seams between them.

A portfolio company’s CRM holds customer revenue. Its ERP holds cost and fulfilment. Its HRIS holds headcount and compensation. Each system, audited in isolation, can look perfectly healthy. The CRM team will tell you their data is clean. The finance team will say the ERP is solid. But the moment an AI initiative tries to join those systems, to answer a question like ‘which customers are profitable net of fulfilment cost and sales headcount,’ the gaps appear. Customer IDs do not match. Product codes were reclassified mid-year. Headcount allocations live in a spreadsheet nobody has touched since the last CFO left.

This is where AI projects actually break. Not inside any one system. In the space between them.

Why the readiness gap is wider than most firms realise

The gap between AI adoption and AI value is striking. Almost every company now uses AI in some form; far fewer can point to value at enterprise level. The foundation explains much of it: 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). The gap between ambition and foundation is not a rounding error. It is the dominant story in enterprise AI right now.

None of that is about models or compute. It is about the unglamorous work of making sure a customer record in the CRM means the same thing as a customer record in the ERP, and that both of them are current, complete, and trustworthy enough to act on.

For PE-backed companies specifically, the stakes compound at exit. Weak data and KPI reporting is a recurring finance problem at exit. A buyer’s diligence team that cannot verify the numbers behind a value-creation story will discount the multiple. The operating partner who built the story knows it is real. The buyer, looking at inconsistent data across systems, cannot confirm it. That gap costs carry.

The Amplification Effect: why bad cross-system data gets worse with AI

There is a tempting assumption that AI will surface and fix data problems over time. The opposite is closer to the truth. AI does not fix a shaky data foundation. It amplifies it.

Errors that sat quietly inside one system, affecting one report, one analyst, one decision, get distributed across every downstream output the moment a model is trained on or connected to that data. They arrive with the implied authority of a model behind them. A mismatched customer ID that skewed one dashboard now skews every recommendation the AI produces, at scale, in real time, with confidence scores attached.

Plenty of companies deploy AI agents before their data is ready. That is not recklessness. It is a genuine blind spot: a cross-system view of data quality is rarely on the table when the commitment is made. They have a green light from each system individually, which is not the same thing.

Why a green score inside one platform is not readiness

Every major platform vendor now ships some version of a data health or AI readiness score. The problem is structural: a vendor score tends to point to buying more of that vendor. A CRM vendor’s score will tell you your CRM data is ready. An ERP vendor’s score will say the same about the ERP. Neither has any incentive to tell you that the join between them is broken, because fixing that join is not something either vendor sells.

The gaps between systems are exactly where AI projects break, and they are exactly what vendor-native scores are not designed to find. An operating partner who relies on those scores before committing AI budget is, in effect, asking each contractor to survey their own work before the renovation begins.

The survey before the build

The right sequence is straightforward in principle, even if it is rarely followed in practice. Before committing AI capital to a portfolio company, commission an independent read on whether the data can actually carry the plan.

That is what a Truth Score Read does. We compare exports from two or more systems, record by record: not each system in isolation, but the joins between CRM, ERP and HR, the places where customer, cost and headcount data are supposed to speak to each other. The output is a signed memo with the Truth Score™ (a score out of 100 for how far the data can be trusted), a Leverability read on the AI in question (which AI ideas you can use now, after fixes, or not at all), the cross-system red flags and a short fix list. The deeper AI Investment Review adds a remediation roadmap that tells the operating partner what needs fixing, in what order, before the AI build begins, written for the company’s own team or any outside firm. We never do the work.

The Truth Score is designed to be board-ready. An operating partner can put it in an IC deck and compare portfolio companies on one consistent scale. It is not a vendor’s self-assessment. It is an independent, defensible number that answers the question the investment committee should be asking before every AI initiative: is this company’s data foundation strong enough to support what we are about to fund?

The distance between a company that captures the upside from AI and one that abandons its AI programme mid-build is rarely model quality. It is data foundation. The survey before the build is how you find out which side of that line your portfolio company is on, before the capital goes in, not after.

The practical next step

If you are an operating partner with AI initiatives live or in planning across your portfolio, the question worth asking is simple: do you have an independent, cross-system read on whether the data can hold the weight? Not a vendor score. Not a self-assessment from the internal data team. An outside view, across the full stack, before the budget is committed.

If an AI proposal is on the table, a Truth Score Read tests it against the company’s own records before you sign. If the foundation is solid, you will know it. If it is not, you will know that too.