An acquisition can begin with a clear account of the capability a company wants to obtain and then move into an integration discussion dominated by a different set of measures. Factories, reporting lines and visible overlap are easier to count than application knowledge or the way people solve a customer's unusual requirement. Those tangible measures deserve attention. The problem arises when they become the whole account and the original reason for the transaction is no longer being examined. I want the acquisition purpose to remain present after the decision to acquire.
The fictional assembly-engineering business brought into Tsuravelle Industries in 2016 had JPY 18.5 billion annual revenue, 70% from customer-specific projects. Its application capability mattered to the industrial direction we were developing. I supported retaining that capability and JPY 420 million in integration preparation rather than assume that factories with apparently overlapping activities were interchangeable resources. The case does not supply a transaction price or an invented return calculation. It concerns how we described the work needed to make the acquisition's strategic reason survive the integration proposal.
## Carry the acquisition reason into the integration question
The footprint was a legitimate starting point because physical resources affect how an industrial business works. It could not establish every relationship on which the acquired contribution depended. Customer-specific projects involved knowledge about applications and requirements that needed their own account. I wanted the integration discussion to explain which parts of that work could be combined, which needed continuity and who was qualified to judge the practical implications. A factory map alone could not answer those questions, even if it accurately described the locations and assets.
The colleagues arguing for consolidation were concerned about pace and value. They wanted the institution to see a clear consequence from bringing the businesses together. I understood why a recommendation to preserve capability could sound like a reason to postpone difficult choices. My response needed to be more specific than a general defence of the acquired business's culture. It had to connect the application work with the customer purpose of the acquisition and identify the evidence required before changing the way that work was organised.
The 70% customer-specific revenue figure provided context, not a complete valuation of the capability. It did not prove that every existing arrangement was necessary or that consolidation would inevitably damage the business. It showed why the project character of the work deserved attention in the integration account. The appropriate engineering, operating, commercial and employment owners needed to assess actual proposals. My strategic role was to make sure the institutional discussion asked about the contribution we intended to obtain before rewarding a simpler footprint as if it were the same result.
## Preserving capability is not the same as preserving everything
There is an important distinction between retaining a capability and leaving every practice unchanged. The former concerns what the business needs to be able to do. The latter concerns the arrangements through which it currently does it. Those arrangements may need to evolve. I would not use the acquisition rationale as a permanent shield against integration, nor assume that keeping teams separate is the only way to protect knowledge. The responsible owners need to examine alternatives with enough understanding of the work to explain what each change might affect.
In this case, the JPY 420 million preparation expense remained visible. It was part of the work required to understand and organise the contribution, not a saving or a measure of value already realised. The expense could be uncomfortable to discuss when the institution wanted an immediate consolidation story. Leaving it out would make the strategic choice appear easier than it was. We accepted more work and a less simple early account because the evidence did not yet justify treating the acquired factories as interchangeable additions to our existing resources.
The choice also preserved uncertainty about subsequent performance. An integration plan that respects the intended capability can still encounter difficulties, and a strategic recommendation cannot establish future operational results. I would not claim improved margins, customer retention or productivity without their own verified measures. The narrower outcome here was a plan that represented the customer-specific character of the acquired work and the preparation required. That is worth describing without inflating it into an all-purpose account of acquisition success.
The practical disagreement helped clarify the contribution. Consolidation sponsors needed evidence that continued complexity served a purpose; capability advocates needed to explain the purpose without relying on sentiment. The strategic account could bring those questions together. It could ask what change would make the combined business more capable of the customer work it intended to pursue, rather than assume either that all overlap was waste or that every difference deserved indefinite protection. The judgement lay in the relationship between purpose and proposed change.
## Choose measures that do not quietly change the purpose
After a transaction, the institution's chosen measures can redirect attention. If progress is described only through reduced footprint or fewer organisational units, colleagues will understandably concentrate on those outcomes. That may be appropriate in some acquisitions. It may be incomplete in one whose rationale includes a particular application capability. I would ask whether the integration account gives the board a way to understand how that capability is contributing, with the responsible management explaining the evidence rather than a strategist inventing a convenient numerical proxy.
This question does not require every valuable activity to remain unmeasured. It asks that the measure fit the purpose and that its limitations remain visible. A count of factories can accurately describe consolidation without proving that the customer proposition has improved. A project-revenue share can describe the acquired business without valuing its knowledge. Using each figure for the question it can support is more useful than expecting one headline to settle the entire transaction story. The account becomes clearer when those boundaries are part of the explanation.
For a leadership profile, I would therefore describe the acquisition through the choice I helped the institution make and the evidence that choice required. I would retain the consolidation argument, the preparation expense and the professional authorities around the work. All details here are fictional. A real account would need permission and verification, particularly around customer-specific knowledge. The lesson I would carry forward is that integration should test and develop the acquisition reason, not quietly replace it with whichever aspect of the combined footprint is easiest to count.