Signing feels like the finish line. The lawyers have stopped redrafting, the money has moved, and the promoter who sold is thanking everyone at dinner. For the buyer, though, this is where the actual work starts. The reasons for doing the deal, such as more customers, more capacity or lower costs, exist only on paper until people on both sides change how they work.
Integration is the hardest part of most acquisitions. Most failures come from a short list of predictable gaps, and planning and plain discipline close them.
A worked example
Take a Gujarat packaging maker that has just bought a smaller competitor with a plant near Nashik in Maharashtra. The reasons for the deal were clear: the Nashik plant's customers in Pune and Mumbai, spare capacity close to those customers, and savings in paper procurement by buying for both plants together.
Failure one: nobody owns the integration
During the deal, the promoter, the CFO and the outside advisers were fully engaged. After closing, the promoter returns to running the Gujarat business, the CFO turns to the year end audit, and the advisers' engagement letters have ended. Integration becomes a set of good intentions spread across busy people.
Name one integration lead with the authority to make decisions and the time to do the job, ideally someone who was involved in diligence. Give them a small team with members from both companies, and a fixed weekly review with the promoter.
Failure two: the plan starts after signing
Many buyers write the integration plan after closing, when they finally have full access. By then the first weeks have passed, and the seller's staff have already filled the silence with rumour.
Draft the plan during diligence. Every important finding, such as an old ERP, a plant manager everyone depends on or a customer contract that renews in three months, should create an item in the integration plan as well as a line in the diligence report. By signing, the buyer should know what happens on Day One, what happens in the first hundred days, and what can wait until year two.
There is one legal caution here. Before closing, and especially before any approval needed from the Competition Commission of India, the buyer must not start running the target or exchanging sensitive commercial information beyond what the law permits. Integration planning can go ahead in that period. Ask your lawyer where the line sits for your deal.
Failure three: Day One basics are missed
Day One is about whether salaries get paid, invoices go out and suppliers deliver. In the Nashik example, the questions are practical:
- Who signs cheques and approves payments from tomorrow, and have the bank mandates been updated?
- Does payroll run as usual this month, on the same dates?
- Do GST invoices, e-way bills and purchase orders carry the right details?
- Who tells the top twenty customers, and what exactly do they say?
- Who tells the shop floor, in Marathi, what is changing and what is not?
A short Day One checklist with an owner for each line prevents most early embarrassments.
Failure four: key people leave
In mid sized Indian businesses, a few people often carry much of the knowledge: the plant manager, the senior accountant, the sales head who has known the purchase managers at key customers for fifteen years. If they leave in the first six months, the buyer is left with machines and a customer list, and the relationships behind them walk out of the door.
Identify these people during diligence. Speak to them personally soon after closing. Give them a clear role and, where it is warranted, a retention arrangement tied to staying through the integration period. Any change to their terms of employment should be handled with labour law advice.
Failure five: customers drift
Competitors read the same news. When a business changes hands, they call its customers within days, suggesting that service will suffer under the new owner. Some customers also use the moment to renegotiate prices.
Plan customer communication carefully. Senior people should call or visit the largest customers personally, explain what changes and what does not, and give a named contact. Track customer orders weekly for the first few months, so that a drop shows up quickly enough to act on it.
Failure six: savings are counted but not owned
The valuation assumed savings from buying paper for both plants together. On paper, that saving belongs to everyone, which means it belongs to nobody. Months later the two plants are still buying separately from different mills because the purchase heads have their own relationships and no one asked them to change.
Every saving or growth item in the deal model should become a line in the integration plan with an owner, a date and a measure. If no one is willing to own it, that is useful information about whether it was realistic.
Failure seven: systems are merged too early or too late
The Gujarat buyer runs SAP. The Nashik plant runs Tally with spreadsheets around it. One temptation is to move the plant onto SAP in the first month, which can disrupt invoicing and stock control just as customers are watching. The opposite temptation is to leave it for years, which means the buyer never gets consolidated numbers it trusts.
A common middle path is to keep the target's systems running for the first months, agree a standard monthly reporting pack in the buyer's format, and plan the system move for a quieter period with proper testing.
Failure eight: culture is treated as a soft topic
Culture sounds vague until it shows up as concrete friction. The Gujarat business may decide quickly with the promoter in the room; the Nashik plant may be used to waiting for its former owner to sign everything. Shift patterns, leave rules, bonus customs and festival holidays may all differ. None of these is wrong. Each causes resentment if it is changed without explanation.
Talk about these differences openly, decide which ones need to be the same and which can stay different, and explain the reasons to the people affected.
Failure nine: attention fades in year two
The first hundred days get energy because everyone knows they matter. By the second year, the integration lead has gone back to a day job, the weekly review has become monthly and then stopped, and the remaining items, often the harder ones such as moving systems, aligning pay structures or closing a duplicate warehouse, quietly fall away.
Treat year two as a planned phase with its own short list of milestones and an owner. Review the original deal case honestly at the end of the first year: which assumptions held, which did not, and what that means for the remaining plan. A buyer who does this learns something useful for its next acquisition as well. A buyer who skips it tends to repeat the same mistakes on the next deal.
What good integration looks like
The fixes share a pattern:
- An integration lead with authority, and a small cross company team.
- A plan drafted during diligence, organised as Day One, the first hundred days and year two.
- A decision log so that people do not reopen settled questions.
- A short set of measures reviewed every week at first, then every month: customer orders, key staff retention, cash, and progress on the main savings.
- Honest communication, repeated more often than feels necessary.
Where you need professional advice
Integration is mostly management, but several steps have legal or tax consequences. Changes to employment terms, transfers of staff between entities and changes to shift or leave rules need labour law advice. Changes to GST registrations, invoicing entities or the merging of legal entities need your CA. Anything that happens before closing, particularly where a Competition Commission of India approval is involved, needs your deal lawyer's view. The Nashik example is illustrative, and none of this is legal or tax advice.
How Synerger helps
Synerger's integration area turns the plan into something people can actually follow. Milestones are set for Day One, the first hundred days and year two, with Gantt style tracking, owners and dates. Risks are identified and reported as they arise, performance is measured against the deal's goals, and integration playbooks give a starting structure so the team is not inventing the checklist under pressure. Because the plan sits in the same record as diligence, findings flow straight into integration tasks. The judgement about what to change, and when, stays with the people running the business.
To see how the plan, milestones and risk tracking fit together, read about Integration on Synerger.