Two businesses can look compatible on a spreadsheet and still be difficult to operate together.
They may serve similar customers but use different pricing methods. Their financial statements may look comparable, but their accounting systems may recognize activity differently. Each may depend on an owner who makes undocumented decisions.
Buying the second business does not resolve those differences. It makes them the buyer’s responsibility.
Before closing, the acquisition plan needs an operating plan behind it.
Start with the reason for the acquisition
What does the buyer expect to gain?
More customers? A new territory? Skilled employees? Production capacity? A product the existing company cannot offer?
The answer should guide what gets combined and what remains separate.
Bain’s integration guidance distinguishes acquisitions intended to expand an existing business from those intended to add different capabilities or markets. The central point is that integration should reflect the transaction's purpose.
A buyer acquiring a company for its specialized service should examine whether imposing different processes would damage that capability. A buyer expecting administrative savings needs to identify which work can actually be consolidated.
“Combine the businesses” is too broad to serve as an operating instruction.
Follow a customer order through both businesses
One useful diligence exercise is to trace a transaction from the first inquiry through final collection.
Who prepares the quote? Who approves exceptions? How is work scheduled? What confirms completion? Who sends the invoice and follows up when payment is late?
Then compare the two businesses.
This can reveal differences that a software inventory misses. Both companies may use reputable systems, yet employees may enter information differently or rely on workarounds that financial statements won't show.
The question is whether the combined operation can complete the work accurately—and who will be responsible when it cannot.
Put a cost and a timetable behind expected savings
Consider a hypothetical acquisition expected to save $120,000 annually through shared administration.
Suppose achieving those savings requires $80,000 in conversion and transition spending, and the savings don't begin until month seven. The first year would produce approximately $60,000 of savings before that spending, leaving a negative $20,000 transition effect.
That simplified example excludes financing, taxes, and other changes. It illustrates why an annual savings estimate is incomplete without timing and implementation costs.
Bain’s work on systems integration similarly emphasizes reassessing integration estimates and allocating sufficient resources.
For each expected benefit, identify:
The action required to produce it.
The person responsible.
The implementation cost.
The expected start date.
The evidence that will show whether it occurred.
Until those details exist, the benefit remains an assumption.
Find the responsibilities that currently belong to the seller
An organization chart may show employees and titles without revealing how much depends on the departing owner.
Who settles customer disputes? Who knows which supplier will extend terms? Who can price unusual work? Who keeps a key employee from leaving?
If the answer is repeatedly “the seller,” the transition needs more than a general promise to help.
The buyer should examine the proposed handover’s scope, availability, duration, and cost. Employees also need to know who can make decisions after ownership changes.
A seller’s willingness to stay involved helps only when the arrangement matches the work that needs to transfer.
Define what must work on the first day
Some integration decisions can wait. Payroll, customer service, payment collection, and essential access need a workable plan from the start.
A first-day review should establish who controls banking and approvals, how employees will be paid, how customers receive support, and which systems people can use.
It should also identify changes deliberately deferred. Keeping a system temporarily can be reasonable when its replacement would create unnecessary disruption.
Planning before closing still requires appropriate boundaries. The FTC cautions that exchanges of competitively sensitive information and premature coordination can create antitrust risks, particularly between competitors. Counsel should establish suitable safeguards for diligence and integration planning.
Use the operating plan to evaluate the deal
An integration review may change the required cash reserve, the transition agreement, the timetable, or the price a buyer can justify.
It may also reveal that the buyer lacks the management capacity to operate another business successfully.
Those findings belong in the acquisition decision.
Before committing, ask: Can we explain who will run the combined operation, what must change, what it will cost, and how we will know it is working?
If those answers remain unclear, the acquisition model still has unfinished work.