The last decision, and the one most often skipped, is how tightly to integrate. Make it deliberately, before close, from the deal's own rationale. Left to emerge on its own, it gets made by whoever happens to be in the room during the first messy month. The foundational framework, still the standard one, comes from Haspeslagh & Jemison (Managing Acquisitions, 1991). It crosses two questions. How much strategic interdependence between the two organizations does the deal's value case actually require, from low to high? And how much organizational autonomy does the acquired business need to keep the value you paid for intact, again from low to high? Four archetypes fall out:
- Absorption: low autonomy need, high interdependence need. You integrate fully and fast into the acquirer's systems, org and processes. It's the right posture when the deal's entire thesis is cost synergy. Duplicate functions have to merge, or the promised savings simply don't exist.
- Preservation: high autonomy need, low interdependence need. Leave the acquired business substantially alone and integrate only what's strictly necessary (shared compliance, treasury, basic reporting). It's right when the deal was bought for the target's distinct culture, brand or way of working, and heavy-handed integration would destroy the very thing you purchased.
- Symbiosis: high need for both interdependence and autonomy. This is the hardest quadrant to execute. Specific capabilities, such as a shared technology or a shared customer channel, have to be woven together quickly. Meanwhile the acquired team's structure, identity and working rhythm stay substantially intact for an extended transition, and the two converge gradually as trust and shared results build up. Talent- and technology-driven acquisitions end up here more often than dealmakers expect.
- Holding: low need for both. There's little to no operational integration, and the parent is essentially a financial owner. It suits pure portfolio diversification with no operational synergy thesis at all. That's rare in a strategic acquisition (as opposed to a financial-sponsor one), so if it really is the deal, say so plainly.
Advertisement
What goes wrong if you pick the wrong archetype?
Why can't this be left to emerge? Because if the synergy case underwritten in diligence assumed full cost integration, only an Absorption archetype can deliver it. Choose Preservation instead, for comfort or to dodge a difficult conversation, and the promised synergies simply won't materialize, however good the tracker is. The reverse fails too. Force Absorption onto a Symbiosis-shaped, talent-dependent deal and you risk losing the people who were the entire point of the transaction before the ink on the retention agreements is even dry. Worked Example 6 walks through that tension on a talent-and-technology acquisition, including what it costs, in hard rupees, to get the archetype wrong.