In an acquisition, what is being acquired is on paper: contracts, systems, client portfolios, assets. What is not on paper is who keeps it all running. In most acquisitions, a significant part of the value sits with a limited number of people who carry knowledge, client relationships or decision-making that is recorded nowhere else. Identifying those people is not a personnel assessment. It is a question about roles: which function is so interwoven with the operation that its loss leaves a demonstrable gap.
The term key person suggests a hierarchy, but the question that matters is functional: what happens if this role is empty tomorrow. For a sales director who personally maintains all major client relationships, the answer is clear. For a controller who is the only one who knows how three systems connect to each other, the answer is less visible but just as real. Key roles are therefore not only found at the top of the org chart. They sit wherever knowledge, relationships or approval authority have accumulated without a second person able to take over.
Mapping this requires a view of the organisation apart from the hierarchy: who has client contact that has not been handed over to a team, who manages a process that is documented nowhere, who makes decisions that formally belong to someone else but in practice end up with one person. That last point is precisely why it is difficult to keep roles clear across two organisations: a key role in one organisation can overlap with a key role in the other, and that overlap is rarely spotted in advance.
A merger or acquisition almost always brings together two people who have filled the same function: two CFOs, two heads of operations, two account managers for the same client. Both can be key people, and both can simultaneously feel that their position is at stake. That is a different question from who carries the value; it is the question what you do when two people have the same role and how you resolve that without the organisation grinding to a halt for weeks over uncertainty. With this overlap, the role must be assessed structurally, independent of who currently holds it.
Mapping key people has only one practical purpose: knowing where the risk of departure is greatest, and limiting that risk before it materialises. Uncertainty about one's own position is a direct trigger for key people to leave, often well before the integration becomes visible to the rest of the organisation. Why this happens specifically in this phase is described at the uncertain months in which people leave. When two corporate cultures also diverge strongly, that departure risk grows, something that deserves separate attention at key people in an acquisition with different cultures and at the question why people leave when those cultural differences are at play.
The departure of a key person is rarely the problem in itself. The problem is what leaves with that person: client relationships that were not handed over, a process no one else can carry out, a decision that suddenly no one can make. That risk can be limited, but only if it has been made visible in advance. How you do that, and which steps actually prevent knowledge from leaving with the person, is described at how you prevent knowledge from leaving with someone.
A list of key people is not an endpoint. It is input for the synergy baseline, for the Day 1 plan and for the Day 100 plan: which roles need certainty in the first week, which dependencies arise when two people serve the same client, and which knowledge must have been transferred before someone can be affected by a departure. Without that overview, integration planning becomes a guess about who will and will not stay, rather than a structured assessment of where the risk lies.
It is also one of the places where the standing question applies of whether something should be merged at all. Not every key role needs to disappear into a combined function; sometimes keeping two separate roles is the way to keep both client relationships or both knowledge domains intact. That trade-off is separate from what looks more efficient on paper.
Once it is clear which roles carry the value, a follow-up question arises that goes beyond acquisition and integration: which part of the work in those roles is routine enough to automate, and which part requires the judgment that only that person has. The work scan from FTE TO AI calculates per task which part of the work can be taken over by AI, making visible where a key role is truly irreplaceable and where the dependency mainly lies in work that could also be organised differently.
Vraag maar wat er op Day 1 moet staan, of wat integreren juist kapotmaakt.
Answers come from this site’s knowledge base. Not tailored advice, and not a scan of your company.