Non-standard systems, hidden liabilities, and complex processes planted by an acquired company's leadership slow integration and make those leaders hard to replace.
An example
Integration of a newly acquired logistics software firm onto a large business software company's finance and billing systems had a nine-month deadline. In month two, the integration director's team found that the acquired firm's general ledger mapped revenue through 340 custom fields only its finance chief understood. In month four, a set of customer contracts surfaced with auto-renewal terms and service credits the data room had summarized in a single line. In month six, the acquired firm's chief executive proposed extending his team's retention bonuses and adding a two-year consulting agreement, since nobody else could run the migration. The deal model had assumed $8 million in shared-services savings by the first anniversary. When the anniversary came, less than a third had been realized.
Why it works
Buried complexity makes keeping the acquired leaders look better, because only they can explain the ledger mapping, the contract traps, and the custom code. The deal's promised synergies look worse as each saving runs into an undocumented dependency. And integrating becomes costly: hidden liabilities surface as litigation, write-downs, or regulatory exposure months after close, and non-standard systems need consultants and custom work. The landmines hold when diligence misses what is buried, the acquirer won't take short-term pain to force standardization, deal terms reward the planters, and the planters intend to stay.
The thinking behind it
Oliver E. Williamson Opportunism and asset specificity, from Markets and Hierarchies (1975) and The Economic Institutions of Capitalism (1985): some parties seek self-interest with guile, including through incomplete or distorted disclosure, and specialized assets make the parties dependent on each other. Custom systems only the acquired team understands create that dependence, and buried liabilities are incomplete disclosure. His remedy is governance: escrows, milestones, and audit rights that safeguard the transaction.
George A. Akerlof Asymmetric information, from The Market for "Lemons": Quality Uncertainty and the Market Mechanism (1970): when the seller knows what the buyer cannot tell, the buyer bears the hidden risk. Diligence inspects what is visible while the outgoing team controls what stays buried. Structures that pay the acquired team only for a clean integration change who benefits from the information gap.
Warning signs
Acquired systems stay non-standard and undocumented past agreed milestones. Only the acquired team can explain how the core processes work. Contract terms and liabilities surface months after close that the data room summarized or left out. Requests for retention extensions, consulting agreements, or larger earn-outs arrive alongside each new complication, and the synergy timeline slips with each one.
How to defend yourself
Assume buried complexity and plan for it before close.
- Scope diligence to look for it: system customizations, contract terms, undisclosed liabilities, dependence on single people.
- Tie earn-outs, clawbacks, and retention to integration milestones, so the acquired team gains from a clean integration.
- Hold an indemnification escrow against undisclosed liabilities, and secure post-close audit rights.
- Make documentation of custom systems and processes a condition of retention payments.
- Budget time and money for what you cannot see.
After close, be willing to take short-term operating pain to force standardization. That removes the planters' hold.
How a leader shuts it down
Handovers of every kind (an acquisition, a contractor exit, an executive departure) are points where the outgoing party controls what stays buried. Design incentives that reward a clean handover, give the receiving team audit rights, and refuse to let indispensability become a negotiating position. Reward leaders who document their systems.