Integration confusion after a deal gives an acquirer cover to let pre-merger commitments lapse and rewrite the acquired company's history, and the promises fade as their witnesses leave.
An example
During the sale of a regional fiber provider to a national carrier, the buyer's deal team promised the provider's head of field operations that his crews would keep their own scheduling system and that the regional office would stay open for three years. The promises were made at a dinner and in a slide that said operational autonomy where it works. Within six months, HR records had moved to the carrier's system, the intranet history page dated the network's construction to the acquisition, and the two acquired executives who had been at the dinner had taken their retention payouts and left. When the field operations head raised the regional office, the integration lead said those had been pre-close conversations and the combined company was one team now. He produced the slide. It said nothing about the office, which closed in the second year.
Why it works
Integration chaos makes insisting on old commitments look worse: records are in transition, the people who made the promises have moved on, and the old channels no longer carry weight. It also makes insisting costly, because naming what was lost sounds like resistance to the combined company and marks the acquired leader as stuck in the past. Real chaos gives better cover than manufactured chaos. The move also needs an acquirer that controls the systems of record before commitments get codified, early exits by the witnesses, vague deal language, and nobody with the authority to hold the commitments.
The thinking behind it
Murray Edelman Constructed accounts, from Constructing the Political Spectacle (1988): problems, leaders, and enemies are constructed and interpreted for the public, and whoever controls the interpretation shapes what people accept. After a merger, the acquirer writes the official history, the org charts, and the intranet. Commitments that never enter that account fade from it, which is why the defense puts them in documents the acquirer does not control.
George A. Akerlof Asymmetric information, from The Market for "Lemons": Quality Uncertainty and the Market Mechanism (1970): the side that holds information the other cannot check sets the terms. After close, the acquirer controls the systems of record and the acquired side's witnesses leave, so the facts about what was promised end up with one party. Written terms, copies held outside the acquirer's systems, and an ombudsman restore the balance of information.
Warning signs
Pre-close commitments are missing from the new systems of record: HR files, org charts, the intranet. The acquired company's executives who witnessed the promises leave early. Official histories start dating achievements from the acquisition. Anyone who cites a pre-merger promise is told the company is one team now. The promises that survive are the ones written down with specific terms.
How to defend yourself
Get every commitment written down with specific terms before close: board seats, office locations, roles, budgets, and dates. Vague promises such as cultural autonomy are the easiest to forget.
- Keep copies of the deal documents and side letters outside the acquirer's systems.
- Push for an integration ombudsman or an escrow tied to the commitments.
- Make sure several people on your side witnessed each promise, and that some of them are staying.
- Raise any lapse promptly, in writing, citing the document.
Speed matters: the faster the witnesses leave, the faster the new account settles.
How a leader shuts it down
If you are the acquirer, put the commitments you intend to keep into the integration plan with owners and dates, and honor them visibly, because every acquired employee is watching. Keep the acquired company's records and history intact. Appoint someone with authority to hear claims that commitments were dropped. Boards can ask for a periodic report on pre-close commitments and their status.