An acquisition is announced with a number, a rationale and a slide. The number is negotiated over months by people who are good at negotiating. The rationale is written by people who are good at writing rationales. Neither tells you much about whether the deal will be worth its price. That question is settled later, in the unglamorous months when two organisations have to share customers, systems, reporting lines and decisions. In 2026, with capital expensive and boards under pressure to show that acquisitions have earned their premium, the executive accountable for that phase is emerging as a distinct and closely scrutinised role.

The argument is not that deal-making skill is irrelevant. It is that the qualities that get a transaction signed β€” conviction, speed, the ability to hold a room β€” are poor predictors of whether value appears afterwards. What separates strong integration leaders is more prosaic: they are appointed before close, they hold clearly assigned decision rights, they secure the people the deal was actually bought for, and they are honest enough to tell a board when the original case no longer holds.

The case for naming the owner before close

Integration leaders are still frequently appointed after completion, once the transaction has been announced and the work of combining the two businesses has begun. By then the synergy case has been built, the assumptions have been fixed and the operating model has been sketched. The person who must deliver all of it inherits a set of commitments they did not test and did not choose.

That handover is where a great deal of value quietly leaks. An assumption about combining two sales forces may look reasonable on a spreadsheet and unworkable once the account lists are compared. A cost target may depend on consolidating a system whose migration was never scoped. The earlier such problems are surfaced, the cheaper they are to fix; the later they appear, the more likely they are to be reported as an overrun rather than resolved as a design question.

Boards are increasingly asking a simple question during diligence: who owns delivery? A named executive in the room while the case is being built arrives at Day One with ownership of the numbers rather than custody of them. That distinction shapes everything that follows.

Decision rights and the route to resolution

Few integrations fail because of one catastrophic decision. They drift, through a hundred small ones that nobody is empowered to make. Two business units claim the same customer. Two functions claim the same system. A pricing question waits for a committee that meets fortnightly. Each delay is individually defensible and collectively corrosive.

The integration leader's contribution here is structural rather than charismatic. It is to establish, before close, who decides what: which questions sit with the integration leader, which with business unit heads, which with functional owners, and which must escalate to the chief executive or the board. It is also to make the escalation path fast enough to be used. A route to resolution that takes six weeks will not be used; people will simply work around it, and the two organisations will settle into parallel arrangements that become permanent.

The test of a well-designed decision structure is not whether it prevents disagreement. It is whether disagreement is resolved in days by someone with the authority to close it.

The people and customers the deal depended on

Many acquisitions are, in substance, purchases of capability: a team of engineers, a group of account owners, a specialist function whose expertise is the reason for the premium. Those people are also the most mobile. Rivals call early, often while the transaction is still in diligence and the news has begun to circulate, and they call with a simple offer of certainty.

Retention therefore starts before Day One. What matters to most specialists is not only compensation but clarity: who they will report to, whether their work will continue, how much autonomy survives, and what happens to the projects they care about. A leader who can answer those questions plainly, weeks before completion, is doing more for the deal than one who arrives with a retention budget after the first resignations.

Customer continuity deserves the same early attention. The first visible sign of a poorly led integration is usually attrition in the accounts that funded the transaction β€” a quiet drift of orders, a re-tender, a relationship that cools because the people who owned it were distracted, reassigned or lost. Protecting those relationships through the transition is not a communications task. It is a delivery task, and it belongs to the executive accountable for the case.

Cost, revenue and the honesty to revise the case

Cost synergies and revenue synergies behave differently and should be reported separately. Cost savings sit largely within the acquirer's control and tend to arrive on a timetable: headcount, procurement, facilities, duplicated overhead. Revenue synergies depend on customers and on behaviour across two organisations that did not previously work together. They arrive later, they are harder to attribute, and they are far easier to overstate in the original case.

Reporting both against a stated baseline, with the same rigour the board applied to the investment case, is what turns integration from a programme into an accountability. That means the same shape of information the board approved: what was promised, what has been delivered, what has slipped, and why.

The hardest part is the last one. Original cases acquire sponsors, and sponsors have reputations attached to them. A leader who defends an assumption that has plainly failed is protecting themselves at the company's expense. The stronger position is to say, in plain terms, that the market has moved or the assumption was wrong, and to set out what the deal is now worth on revised terms. Boards can absorb a changed case. They struggle to absorb a case that was quietly abandoned without anyone saying so.

An accountability that outlasts the announcement

Integration reporting delegated to a project office tends to become a programme update: milestones, workstreams, status colours. Useful, but not what directors need. What they need is a single named executive who carries the delivery of the case over a multi-year horizon, appearing before them with the same regularity as the businesses that missed their plans.

For a category built around individual leadership expertise, this is where the role is most clearly tested. The integration leader is judged not on the announcement but on the years after it: whether the customers stayed, whether the specialists stayed, whether the conflicts were settled quickly, and whether the board was told the truth about what the deal had become. Deal value is decided after signing. The leaders who decide it well are rarely the ones who negotiated it.

← PreviousBack to Articles