Every acquisition has a financial ledger.
It also has an employment ledger.
The first is visible before signing. Purchase price, debt, EBITDA, cash flow, synergies, returns, and transaction costs are modeled, challenged, and negotiated.
The second is harder to see.
It contains the people who operate the business, the skills they carry, the relationships they maintain, the institutional knowledge they hold, the obligations attached to their employment, and the locations in which those capabilities exist.
That ledger can determine whether the value thesis survives integration.
This matters in a market where M&A activity is recovering unevenly. Boston Consulting Group reported that global M&A value rose 15% during the first eight months of 2026, while the recovery remained concentrated in larger transactions and smaller deals continued to lag longer-term norms. BCG also identified execution—not simply capital or buyer appetite—as an increasingly important constraint on transactions moving forward.
Execution eventually reaches people.
The question is whether the people required to deliver the deal’s value have been identified with the same discipline as the financial assumptions.
The Workforce Is Part of What Is Being Acquired
A buyer does not acquire a company as an abstract legal entity.
It acquires an operating system.
People design the products. Engineers maintain the technology. Sales teams hold customer relationships. Procurement teams understand suppliers. Plant managers know how production actually works. Finance teams understand reporting and controls. Local executives know regulators, customers, vendors, and the informal relationships that rarely appear in a data room.
Some of that knowledge is documented.
Much of it is not.
This creates a familiar problem in M&A: the organization chart is precise, while the capability map is incomplete.
Headcount tells a buyer how many people are employed.
It does not necessarily tell the buyer what those people make possible.
Two employees with the same title may carry very different strategic value. A ten-person team may contain knowledge that cannot be reproduced by hiring ten replacements. A facility may appear overstaffed while carrying specialized capabilities that support an entire product line.
The employment ledger therefore has to go beyond counting people.
It has to identify what the workforce enables.
From Headcount to Capability
Cost synergies often begin with headcount.
That is understandable. Labor is measurable, and overlapping functions can create an obvious opportunity for consolidation.
But headcount is only the first layer of workforce analysis.
A more complete employment ledger should identify at least five dimensions:
People.
Who works for the target, where are they located, and what functions do they perform?
Capability.
Which employees possess technical, managerial, commercial, or institutional knowledge that is difficult to replace?
Continuity.
Which people, teams, or relationships must remain intact for the business plan to work?
Obligations.
What employment contracts, retention arrangements, pensions, benefits, collective agreements, regulatory requirements, or other commitments affect the workforce?
Geography.
Where are critical capabilities concentrated, and what happens to the local operating system if those capabilities are disrupted?
This changes the question.
Instead of asking only, “How many positions can be eliminated?”
The buyer asks:
“Which capabilities must survive for the value thesis to work?”
That is a more useful integration question.
The Geography of a Workforce
Peter Dicken’s discussion (Global Shift: Mapping the Changing Contours of the World Economy (6th edition) of employment reinforces why location belongs in the workforce analysis.
In Global Shift, he argues that changes in employment are geographically uneven. The development of global production networks affects where jobs and incomes are distributed, while firms continually reconfigure operations across national boundaries. The result is an uneven geographical division of labor, with different places experiencing different employment effects.
That observation has a direct implication for acquisitions.
The workforce is not distributed evenly across the enterprise.
Critical skills may be concentrated in one city.
Manufacturing expertise may reside in one plant.
Customer relationships may depend on a regional team.
Engineering knowledge may be concentrated in a particular research center.
A company may have thousands of employees across multiple countries but depend disproportionately on a much smaller group in a handful of locations.
That concentration may be invisible in total headcount.
It becomes visible when the employment ledger is mapped against the value thesis.
The People Behind the Synergy
Consider a buyer acquiring two businesses with overlapping finance, human resources, procurement, and information technology functions.
The obvious synergy case is consolidation.
The buyer can eliminate duplication, combine teams, standardize systems, and reduce cost.
That may be the correct decision.
But the same logic becomes dangerous when applied mechanically to operating capabilities.
Suppose the target’s engineering team appears larger than necessary after the transaction.
A headcount model may identify excess capacity.
A capability analysis may reveal that the team holds specialized knowledge of a product platform that represents a significant portion of the acquisition thesis.
The apparent redundancy is therefore different from functional duplication.
One is a cost opportunity.
The other may be an operating risk.
This distinction is particularly important when integration timelines are aggressive.
Employees do not experience a transaction as a spreadsheet exercise. They experience a change in ownership, reporting lines, responsibilities, incentives, systems, location, and perceived career prospects.
Some will leave.
Some will stay.
Some will become more important after integration.
Others may become unnecessary.
The buyer needs to know which is which before the organization begins making decisions that are difficult to reverse.
Retention Is a Value Question
Retention is often treated as a human-resources issue.
In many transactions, it is a value-creation issue.
If the value thesis depends on a small number of people with scarce technical knowledge, customer relationships, regulatory expertise, or institutional memory, losing those people can change the economics of the transaction.
The relevant question is therefore not simply whether employees are likely to remain.
It is:
Which departures would change the value thesis?
That question allows retention planning to become more precise.
Not every employee requires the same retention strategy.
Not every position carries the same transition risk.
The buyer can identify critical individuals and teams, determine where knowledge is concentrated, establish appropriate continuity measures, and distinguish essential retention from broad-based retention spending.
This is where the employment ledger becomes useful before closing.
It connects people to the assumptions already embedded in the investment thesis.
What the Spreadsheet Does Not Capture
Dicken’s treatment of employment also cautions against reducing workforce effects to a single number.
He examines technological change, globalization of production, outsourcing, offshoring, and trade competition as overlapping forces affecting employment. His conclusion is that employment changes cannot be explained by a single cause. More importantly for the geographic argument, the distribution of employment effects matters because jobs created and jobs lost may occur in different places.
The same principle applies within an acquisition.
A transaction may eliminate positions in one location while creating positions elsewhere.
A headquarters function may be consolidated while a technology center expands.
A manufacturing facility may close while another facility receives new investment.
A buyer may reduce administrative headcount while increasing engineering or commercial capacity.
The aggregate employment number can therefore conceal a significant redistribution of capability.
For dealmakers, that matters because the locations affected by those changes may also contain the relationships and infrastructure on which the business depends.
The employment ledger and geographic map are therefore connected.
The first identifies the people and capabilities.
The second identifies where those capabilities reside.
When Cost Synergy Becomes Capability Destruction
Cost reduction is often one of the clearest sources of M&A synergy.
But a cost reduction creates value only if the business can continue to perform the activities that remain strategically necessary.
This is where integration discipline matters.
Before eliminating a role, a buyer should understand:
What does this person or team actually do?
Which processes depend on that knowledge?
Which customers or suppliers depend on the relationship?
Is the capability duplicated elsewhere?
Can it be transferred?
How long would replacement take?
What happens if the capability leaves before the knowledge is transferred?
Does the role support a current operation or a future growth thesis?
These questions are especially important for specialized employees.
A buyer can replace a position faster than it can replace accumulated knowledge.
It can replicate a process more easily than it can rebuild a relationship.
It can relocate an office more easily than it can recreate the network of institutional knowledge built around it.
The cost of losing capability therefore may appear long after the headcount saving has been recorded.
That timing creates one of the more difficult problems in integration.
The financial benefit is immediate.
The capability loss may emerge later.
The Employment Ledger Before Closing
The employment ledger should begin before the integration team receives the keys.
At diligence, the buyer should be able to answer a series of practical questions.
1. Who carries the value?
Identify the people and teams directly connected to the transaction thesis.
2. Where are they?
Map those capabilities geographically.
3. What knowledge is documented?
Separate transferable institutional knowledge from knowledge that resides primarily with individuals or teams.
4. What relationships depend on them?
Identify customer, supplier, regulatory, technical, and internal relationships that could be disrupted.
5. What happens if they leave?
Assess the time, cost, and operational consequences of replacement.
6. What must remain intact through integration?
Identify capabilities that cannot be disrupted while systems, reporting structures, facilities, or operating models change.
7. Which workforce changes are genuine synergies?
Distinguish functional duplication from capabilities that merely appear duplicative when viewed through an organization chart.
This is not a request to preserve every role.
It is a request to understand what the buyer is changing before changing it.
Integration Starts With a Capability Thesis
The best workforce planning begins with the same discipline as the financial model.
Start with the investment thesis.
Then identify the capabilities required to deliver it.
Then identify the people and locations carrying those capabilities.
Only then should the organization determine which roles can be consolidated, redesigned, relocated, or eliminated.
This sequence matters.
If headcount reduction comes first, the organization may discover afterward that it removed a capability required to generate the projected revenue, protect a customer relationship, maintain a product, or complete an integration.
If the capability thesis comes first, workforce decisions become more precise.
The buyer can reduce duplication without confusing duplication with strategic capacity.
That is the difference between workforce cost management and workforce value management.
The Employment Ledger Is an Integration Instrument
The employment ledger ultimately changes the meaning of integration.
Integration is often described as the process of bringing two organizations together.
A more useful description is the process of preserving, combining, transferring, and rebuilding the capabilities required for the combined business to perform.
That includes people.
It also includes what people know, whom they know, where they work, and what depends on their continued presence.
Dicken’s analysis of global production networks makes a similar point at a broader geographic scale. Economic activity is embedded in networks, and the consequences of changes within those networks are distributed across different places and groups. Employment effects are therefore not captured adequately by aggregate numbers alone.
M&A creates its own network of consequences.
The buyer changes ownership.
Integration changes the organization.
Those changes alter where capabilities reside and who carries them.
The employment ledger makes that movement visible.
What Must Survive for Value to Land?
Article 1 established the geographic question: Where does deal value land?
The operational question is more immediate:
What must survive for that value to be realized?
The answer will rarely be “everyone.”
It will also rarely be “headcount reduction.”
It will be a specific combination of people, capabilities, relationships, systems, facilities, and knowledge.
The buyer’s responsibility is to identify that combination before integration begins.
That is where the employment ledger becomes more than a workforce exercise.
It becomes part of the value-creation model.
A transaction creates the possibility of value.
People and capabilities determine whether the operating business can deliver it.
And those capabilities exist somewhere.
Take the Question Into Execution
A workforce does not appear as a line item in the purchase price.
Its skills, relationships, institutional knowledge, location, and continuity can determine whether the value thesis survives integration.
The 2026 Future of Dealmaking Summit, November 16–17 in New York, brings M&A professionals together for financing, restructuring, and M&A thought leadership sessions, as well as M&A Connects networking and one-on-one meetings.
Leave a Reply