Mergers and acquisitions often sound glamorous in press releases, but the reality inside the due diligence war room is usually anything but. Last quarter, we advised on a deal where a PE firm was purchasing a highly profitable mid-market logistics company. The financials were pristine, the customer retention was excellent, and the executive team was locked in. It looked like a very solid deal.
Then, the technical due diligence began.
The Ghost in the Machine
The entire operation of the company - from dispatch routing to international freight customs - ran on a monolithic ERP system deployed in 2011. Over 15 years, it had been heavily customized by a single internal developer, who had since retired. There was zero documentation. The source code for the custom modules was lost on a decommissioned laptop. The database was a tangled web of undocumented SQL triggers.
When the acquiring firm's architects requested the API documentation to plan the post-merger integration, the room went silent. There was no API.
The Valuation Haircut
The PE firm realized that integrating this company into their portfolio would require a total ground-up rebuild of the ERP system, taking an estimated 18 months and significant CAPEX, plus the massive operational risk of migrating a live logistics network. They immediately demanded a significant reduction in the purchase price.
The Lesson
EBITDA and revenue growth will get you to the negotiating table, but technical debt will cost you at the finish line. If your core systems are undocumented, unscalable, or reliant on "tribal knowledge," your valuation is built on sand. Modernize your infrastructure before the auditors show up, or be prepared to pay the price at the closing table.