Chemical acquisitions are frequently justified on technology: a formulation portfolio, a process capability, a pipeline. The valuation rests on the assumption that the capability transfers with the assets.
A meaningful part of it doesn't sit in the assets. It sits in a small number of people, and much of what they know was never written down.
Why technical people leave after a deal
Their project gets rationalised
Portfolio review is a normal part of integration, and it is also the fastest way to lose the person whose work was cancelled. The decision may be correct; the retention consequence is frequently unplanned for.
The reporting line stops making sense
Senior technical people often lose a direct route to decision-makers and find themselves several layers down a larger structure. For someone who joined a smaller business specifically for that access, this is a bigger factor than compensation.
The uncertainty period runs too long
People tolerate ambiguity for a while. What they don't tolerate is months of it with no communication. Competitors, and specialist recruiters, know exactly when those windows open.
Retention was aimed at the wrong people
Retention packages typically follow the org chart. Technical criticality frequently doesn't. The person holding the process knowledge for your highest-margin product line may be three levels below anyone the retention plan considered.
Identify criticality before completion
The useful exercise is narrow and quick. For each capability the deal thesis depends on, ask:
- Who actually holds the knowledge, not who manages the function
- How much of it is documented to a standard someone else could use
- How long it would take to rebuild the capability if that person left
- How replaceable they are in the external market, realistically
The answer is nearly always a short list, often a handful of people, and it rarely matches the top of the org chart. That list is the retention plan. Everything else is secondary.
What actually protects them
Speed and specificity of communication. Ambiguity is what moves people. Telling technical staff early what happens to their programme, even when the answer is imperfect, retains better than silence followed by good news.
Scope, not just money. Retention bonuses buy time; they don't buy commitment. What holds senior technical people is a credible answer about what they'll be working on, with what resources, reporting to whom. Money without that answer typically delays a departure to just after the payment date.
Knowledge transfer treated as a deliverable. If capability is genuinely deal-critical, documentation and structured handover should be resourced and tracked like any other integration workstream, not left as something people do when they have time.
A realistic view of restrictions. Non-competes vary enormously in enforceability between US states and European jurisdictions. Assuming a clause will hold is not a retention strategy.
The recruiter's view of the same window
It is worth knowing how this looks from the outside. Specialist recruiters in chemicals track acquisitions closely, because integration periods reliably produce unsettled technical people who were previously immovable. The window opens at announcement and stays open through the first year.
That cuts both ways. If you're acquiring, assume your critical people are being contacted. If you're hiring, these windows are when otherwise unreachable candidates become reachable, and it's a considerable part of why mapping the market continuously beats searching it reactively.
Common questions
Why do scientists leave after an acquisition?
Most commonly because their project is rationalised during portfolio review, because they lose direct access to decision-makers in a larger structure, or because the uncertainty period runs for months without clear communication. Compensation is rarely the primary driver.
How do you identify which technical staff are critical to a deal?
For each capability the deal thesis depends on, establish who actually holds the knowledge rather than who manages the function, how much is documented usably, how long the capability would take to rebuild, and how replaceable that person is externally. The resulting list is usually short and rarely matches the org chart.
Do retention bonuses keep critical scientists?
They buy time rather than commitment. Without a credible answer on future scope, resources and reporting line, retention payments commonly delay a departure until shortly after the payment date.
When are acquired technical staff most likely to be approached by competitors?
From announcement onward, and throughout the first year of integration. Specialist recruiters track acquisitions precisely because these periods make previously settled technical people reachable.
Integrating an acquisition?
We can help you work out which technical people the deal thesis actually depends on, and how reachable they look from the outside.
Book a Confidential Briefing →