[Octavian Mihalcovici]

One of the most critical yet often overlooked aspects of a merger or acquisition is setting an appropriate integration budget. Underestimating these costs can derail integration efforts, while overestimating might reduce the deal’s financial appeal.

Key questions to discuss:

How do you calculate the integration budget for an acquisition?
What percentage of the deal value is typically allocated to integration?
What categories (e.g., IT integration, HR alignment, cultural initiatives) consume the most budget in your experience?
How do you handle unexpected costs during integration?
From my knowledge, IT systems harmonization and cultural integration often require a significant portion of the budget. However, I am keen to learn how others approach this planning process and track spending to ensure alignment with strategic goals.

Please share your insights, strategies, and best practices for managing and calculating integration budgets. Are there any tools or frameworks you recommend for accurate cost estimation? Let’s discuss!

[jeffreestar]

One way I often apply is to use phased budgeting and project management software Granny Game to track costs in areas such as HR, IT, and operations. This helps keep the budget close to reality and avoid overspending.

[Daniel]

We use a metric of integration budget per pound of annual revenue of the acquired company to determine a baseline expected integration cost for budget approval. We then ask the workstream leads to submit a budget request using a generic budget model we have built. Inevitably they ask for a lot more but we compare to previous integrations to sense check their asks and identify any drivers of why a budget item might be different this time around.

Primary reasons for difference is location – if its far away from our main centres there will be more travel, if it is a lower cost location then certain costs such as software licensing will be relatively more expensive than average, higher cost location then things consultants will be more expensive.

For us the usual culprits are software licensing (parallel licensing periods), travel depending on location and legal and professional fees (particular if in a location we dont already operate).

So having a number of integrations under you belt helps create a baseline to compare and then compare it per workstream and per ledger/category and understand integration cost drivers

[Author]

Posts