An acquisition is paid for on the day the agreement is signed, but the value has to be earned afterwards. None of what the price assumes, whether more customers, a new product or lower costs, arrives automatically. It arrives, or fails to arrive, in the months after closing, through hundreds of small decisions about systems, people, customers and ways of working.
This is where many acquisitions quietly lose what they were bought for. The best salespeople leave because nobody told them what would happen to their customers. The core business slows down because its leaders are busy with integration meetings. Nobody intended this. It happened because integration was treated as a project to complete rather than a set of choices to make.
This article sets out a practical approach: start from the reason you bought the company, decide what to integrate and what to leave alone, plan the first hundred days and keep measuring whether the value is realised.
Start from why you bought it
Every acquisition rests on a deal thesis: a short explanation of why this company is worth more as part of yours than on its own. It might be access to new customers, a product that would take years to build, a skilled team or savings from combining purchasing, premises or back-office functions.
Before anyone starts planning integration, write the thesis down in a few sentences. Be specific about where the value is supposed to come from. "Strong strategic fit" is not a thesis. "Their service team gives us local presence in three regions where we lose tenders today" is.
The thesis matters because it tells you what to protect and what to change. If you bought the company for its customer relationships, the people who hold those relationships are the most important asset in the deal, and anything that unsettles them is a risk. If you bought it for cost savings, then combining functions quickly is the point, and delay is the risk. The same integration step can be right in one deal and destructive in another.
A useful test: for each part of the acquired business, ask whether integrating it helps deliver the thesis, harms it, or makes no difference. Most of the time you will find that only a few areas really need to change, and that some areas should be actively left alone.
Three ways to integrate
There is no single right level of integration. In plain words, most acquisitions follow one of three patterns, or a mix of them for different parts of the business.
- Absorb. The acquired company becomes part of yours. Its products, systems, processes and often its brand are folded into your own. This fits when the value lies in scale and cost savings, and when the acquired company does broadly the same things you do.
- Preserve. The acquired company keeps running largely as it was, with its own brand, leadership and ways of working. You connect only what is necessary: financial reporting, some governance and perhaps a few shared services. This fits when the value lies in something that integration could easily damage, such as a distinctive culture, a specialist team or close customer relationships.
- Combine. Both companies change. You take the best of each and build something new together, for example a joint product range or a shared service model. This is the most demanding pattern, because it asks people on both sides to give something up.
The common mistake is to choose one pattern for the whole company by default, usually absorb, because it feels tidy. In practice, a single acquisition can call for different treatment in different areas. You might absorb finance and payroll, preserve the sales team and the brand, and combine product development. Make the choice area by area, and make it based on the thesis.
Integrate what the deal needs. Protect what the deal paid for. Leave the rest alone until you have a reason to touch it.
The first day
Day one is short, but people remember it for years. Employees in the acquired company want answers to a few simple questions: Do I still have a job? Who is my manager? Does anything change on Monday? Customers want to know whether their contact person, prices and service will stay the same.
You will not have every answer on day one, and you should not pretend to. What you can do is be honest about what is decided, what is not yet decided and when people will hear more. A few practical points:
- Tell employees what will not change in the near term. This is often more reassuring than describing what will.
- Make sure every key customer is contacted directly, ideally by the person they already know, before they read about the deal elsewhere.
- Keep the basics working: pay, access to systems, phone numbers, email addresses, invoices.
- Give people a named person to ask, and a date for the next update.
Avoid announcing future structure unless the decisions are genuinely made. Promises that turn out to be wrong do lasting damage to trust.
The first month
The first month is about stability and learning. The acquired company should keep serving its customers without disruption, while the integration team builds a much better understanding of how it actually works.
Due diligence gives you a picture taken from the outside, under time pressure. Once you own the company, you can see how decisions are really made, who holds things together and which processes depend on a single person or an old spreadsheet.
Use the first month to:
- Confirm or correct the deal thesis with what you now know.
- Identify the key people, not only by title but by what they actually hold: customer relationships, technical knowledge, informal leadership.
- Map the critical customer accounts and agree how each will be looked after.
- Find the quick, visible wins that make life easier for people on both sides, such as access to a shared tool or a simpler approval process.
- Draft the integration plan for the first hundred days, area by area, with an owner for each.
Resist the urge to change things just because you can.
The first hundred days
By the end of the first hundred days, the big integration decisions should be made and the most important ones should be under way. People should know the structure they work in, who leads them and what is expected of them. The areas you chose to absorb should be well on the way, and the areas you chose to preserve should have clear boundaries.
A good hundred-day plan is short. For each area of the business it states the chosen approach (absorb, preserve or combine), the few concrete steps that will happen in the period, who owns them and how you will know they are done. It also states what will deliberately not happen yet, so that people do not fill the silence with rumours.
Speed matters here, but in a particular way. Uncertainty is expensive. The longer people wait to hear what will happen to their roles, the more of them start looking elsewhere, and the best ones find something first. So make the decisions about structure and roles quickly, even if the work of implementing them takes longer. A clear decision with a realistic timeline is easier to live with than an open question.
Protecting customers and key people
The two assets most easily lost in an acquisition are customers and key people, and they are often linked. Customers frequently follow the people they trust.
For customers, the rule is simple: nothing should get worse for them because of the deal. Say a company buys a smaller competitor with around two hundred customers, and the thirty largest account for most of the revenue. Each of those thirty should have a named owner, a personal conversation early on and a clear answer to what will change for them, if anything. Changes to prices, terms, systems or contact persons should be introduced carefully, with a reason the customer can understand, and never all at once.
For key people, start by finding out who they are. Titles are only part of the picture. Ask managers and colleagues who people go to for help, who the customers ask for by name, and who would be hardest to replace. Then talk to those people individually and early. Tell them why they matter, what their role will be and what is still open. Ask what they need.
Retention bonuses can help in the short term, but they rarely keep people who feel overlooked. What keeps people is a role that makes sense and a new owner who understands what they contribute.
Culture as working habits
Culture is often blamed when integration goes wrong, but the word is usually too vague to be useful. Telling two organisations to "align their cultures" or to "live the shared values" changes very little.
It helps to treat culture as concrete working habits. How are decisions made, and by whom? How much does a manager need to approve? How are meetings run? How quickly are emails answered? How do people disagree? How formal is the tone with customers? How much freedom does a salesperson have on price?
Seen this way, the differences become specific, and you can decide which habits matter for the deal thesis. If the acquired company wins customers because its people can make quick decisions on the spot, then imposing your approval process will destroy something you paid for. If its habit of informal record-keeping creates risk, that is a habit worth changing, with a clear explanation of why.
A simple exercise: ask a small group from each company to describe how a typical piece of work is done, such as a customer request or a purchase. Comparing the two descriptions often reveals more than any survey.
Governance: a small team with clear owners
Integration needs a structure, but a lean one. Large steering committees and long status reports slow decisions down.
A workable model looks like this:
- An integration lead with real authority and enough time to do the job properly. This is a demanding role, and it should not be added on top of a full-time job.
- A small integration team with one owner per area, drawn from both companies where possible. Each owner is responsible for the plan and the decisions in their area.
- A short weekly meeting where owners report progress, raise problems and get decisions made. The focus is on what needs deciding, not on reporting everything that has happened.
- A clear escalation path to one senior sponsor who can settle disagreements quickly.
- A simple decision log, so that everyone can see what has been decided, by whom and when.
Include people from the acquired company in the team. They know how their business works, and their involvement signals that integration is done with them, not to them.
Measuring whether value is realised
The deal thesis should translate into a small set of measures that show whether the value is arriving. If the thesis is about customer access, track retention of the acquired customers and new sales into the target group. If it is about cost savings, track the actual savings against the plan, net of the costs of integration. If it is about a team or a capability, track retention of the key people and whether the capability is actually being used.
Add a few early warning signs: unplanned departures, customer complaints, delivery delays and the performance of the core business. That last one is easy to forget, and a dip in the core business can wipe out the gains from the acquisition.
Review the measures monthly in the first year, and be honest when something is not working. It is better to adjust the approach in month four than to discover in month eighteen that the thesis was never delivered.
Common pitfalls
A few mistakes come up again and again:
- Integrating everything. Treating full integration as the default, even where it destroys what made the acquired company valuable.
- Moving too slowly on people decisions. Leaving roles and structures open for months, so that uncertainty drives away the people you most wanted to keep.
- Moving too fast on customer-facing changes. Changing prices, systems or contact persons before customers have any reason to trust the new owner.
- Distracting the core business. Pulling the best leaders into integration work without backfilling their day jobs.
- Losing sight of the thesis. Measuring integration by tasks completed rather than by value realised.
Where to start
If you are about to close an acquisition, or are already in the middle of one, start with these steps:
- Write the deal thesis in three or four sentences, and share it with everyone who will work on the integration.
- For each area of the acquired business, decide whether to absorb, preserve or combine, and write down why.
- List the key customers and key people, and give each one a named owner on your side.
- Appoint an integration lead with real time and authority, and a small team with one owner per area.
- Choose three to five measures that show whether the thesis is being delivered, and review them every month.
Done this way, integration stops being a long list of tasks and becomes a set of deliberate choices about where the value is and how to keep it.