You bought the business. Now integrate the operations.

Acquisitions in the lower mid-market are underwritten on financials. The model shows combined revenue, an assumption about cost synergies, and a return that justifies the price. The diligence that supports it is largely financial and legal.

Then completion happens, and the acquiring business discovers it now operates two companies. Two finance systems, two ways of quoting, two service standards, two cultures, and two groups of people watching to see which one is going to win. The synergy line in the model assumed they would become one. Nothing in the transaction made that happen.

The first ninety days set the pattern

Integration decisions made early are difficult to revisit, because people build habits around them and because reopening a decision reads as instability to a workforce already anxious.

The most common early error is deferral. Leadership, reasonably, does not want to disrupt a business it has just paid for, so it leaves the acquired company alone to keep performing. Six months later the two organisations have drifted further apart, the acquired team has concluded that nothing will change, and the integration is harder than it was on day one.

The opposite error is a wholesale systems migration in the first month, which consumes the attention of everyone who is also trying to keep clients served through a change of ownership.

Four decisions worth making deliberately

What is being integrated, and what is not

Full integration is not always the objective. Sometimes the acquisition was for a capability, a client base or a geography, and the acquired business is better left operating distinctly. That is a legitimate answer, but it has to be an answer rather than an omission, because the cost base in the model usually assumed otherwise. Decide explicitly which functions merge, which stay separate, and for how long.

Which system of record survives

Two CRMs, two finance systems, two job management platforms. The default is that the acquirer’s systems win, which is often right and is sometimes wrong: acquired businesses are occasionally better run in a particular function than the buyer. What matters more than the choice is making it early and completely, because running both indefinitely means nobody can report on the combined business without manual reconciliation. This is stack consolidation under time pressure, with the added complication that the people who understand each system have divided loyalties.

Whose process is the standard

Both businesses quote, deliver and invoice differently, and both believe their way is correct. Left unresolved, the combined business carries two service standards and clients experience whichever one their account manager came from. Resolving it requires someone to compare the two processes on their merits rather than by seniority of origin, and to document the result so it can actually be adopted.

Who the acquired team reports to, and when they find out

Uncertainty about reporting lines is the fastest way to lose the people the acquisition was meant to secure. The good ones have options and they exercise them when the future looks ambiguous. Reporting structure should be decided before completion and communicated within days of it, even if some elements are provisional.

The synergies in the model are operational changes. If nobody is accountable for making them, they are an assumption, not a plan.

Why key people leave in year one

Retention risk in the acquired business is usually understood in terms of the founder, whose commitment is secured contractually. The departures that cause more operational damage are one level down: the operations manager who knew how everything worked, the senior technician clients ask for by name, the administrator who held the scheduling logic.

These people rarely have retention agreements. They experience the acquisition as a loss of standing, watch decisions being made elsewhere, and leave with the undocumented knowledge that made the acquired business function. The acquirer then discovers how much of what it bought was held in individuals, which is precisely what operational due diligenceexists to establish and what financial diligence cannot see.

A workable sequence

Before completion, if access permits, map the acquired operation: systems, processes, and the people each depends on. This is the same exercise as an operational audit and it should inform the integration plan rather than the price, since the price is usually settled.

In the first month, resolve people questions. Reporting lines, role clarity, and direct conversations with the second tier about where they fit. Nothing else integrates if these people leave.

In the first quarter, unify reporting even if the underlying systems remain separate. Leadership needs one view of the combined business early, and a manual consolidation is acceptable while the systems question is worked through properly.

Across the first year, consolidate systems and standardise process, in that order, function by function, with a named owner for each. Assign the synergy assumptions in the model to those owners as targets. A synergy nobody is accountable for delivering is a number in a spreadsheet, and it will still be a number in a spreadsheet at the end of the year.