The First 100 Days After an Acquisition: What Actually Goes Wrong

Why the first 100 days define deal value

Most acquisition value is not lost in due diligence. It is lost in the 100 days after the deal closes, when attention shifts to the next transaction and the target business is left to "integrate itself".

The investment thesis was built on assumptions - synergies, cross-sell opportunities, operational improvements. Those assumptions do not materialise automatically. They require active management of a business that is simultaneously confused, anxious, and still trying to serve its customers.

Research consistently shows that between 50% and 75% of M&A deals fail to deliver their projected value. The integration period is where that failure happens - not in the boardroom where the deal was approved.

The five things that go wrong most often

1. The integration plan is too abstract

Integration plans written during due diligence tend to be high-level documents that describe outcomes rather than workstreams. They say things like "align finance functions by month three" without specifying who owns it, what that actually means for the finance team in the acquired business, or what the dependencies are.

By the time the deal closes and someone tries to use the plan as a working document, it is already obsolete.

2. Key people leave in the first 60 days

The people who know where things are, how the customer relationships work, and why the business does things the way it does are usually not protected. Retention packages are agreed for the senior leadership team but not for the operational managers and technical specialists who carry the institutional knowledge.

When they leave - and they will leave if nobody talks to them - the acquirer is left managing a business it does not understand using a plan that does not reflect reality.

3. Systems integration is underestimated

Every acquired business has a technology estate. Rarely is it compatible with the acquirer's. The standard approach - "we'll migrate them onto our systems" - routinely takes three times as long and costs twice as much as planned, and during the migration period nobody has reliable management information from either business.

The more dangerous version is when the integration team declares victory on systems before the data has been validated. The acquirer is now running the combined business on reports that are structurally unreliable.

4. Culture is treated as a soft issue

The acquired business has a way of working. Its people have a reason they joined that business rather than the acquirer. When integration is communicated as "we're standardising everything onto our model", the implicit message is that the acquired business's ways were wrong. That message lands faster and harder than any formal communication.

Turnover accelerates. Customer relationships deteriorate. The revenue assumptions in the investment thesis start to look optimistic.

5. There is no clear integration owner

In most integrations, responsibility is distributed across the CFO, HR director, and IT director of the acquirer - all of whom have day jobs. Nobody has explicit accountability for the integration as a whole, so decisions are deferred, issues escalate slowly, and the acquired business's management team is never quite sure who to call when something needs resolving.

Day One readiness: what good looks like

Day One is the day the deal closes. It is not the day integration starts - integration work should have been underway for at least six weeks before close. Day One is when the combined business becomes a legal and operational reality, and the people in the acquired organisation wake up as employees of a different company.

On Day One, the acquired business needs to know:

• Who their new line manager is and whether that has changed
• What is changing immediately and what is not changing yet
• How to get answers to questions (a named contact, not a generic inbox)
• What the plan looks like for the next 90 days
• That their customers will receive a consistent message

What it does not need on Day One: a detailed systems migration plan, a new HR policy handbook, or a presentation about the acquirer's values. That can come later. Day One is about stability and trust.

Days 1-30: stabilise before you integrate

The first 30 days are not for integration. They are for stabilisation. The acquired business needs to keep operating while trust is established and the integration team builds a realistic picture of what it has actually acquired.

The gap between what due diligence revealed and operational reality is almost always larger than expected. Diligence is conducted on documents and management representations. Reality is found in the operational detail - the workarounds, the informal processes, the customer relationships that live in one person's head.

In days 1-30 the integration team should be:

• Listening, not announcing. Running structured conversations with operational managers, not presenting the integration plan to them.
• Mapping dependencies. Which customers, contracts, systems, and people are genuinely critical to continuity?
• Identifying blockers. What is already going wrong that nobody flagged in due diligence?
• Delivering visible quick wins. Small things that demonstrate the acquirer is investing in the business, not just extracting from it.

Days 31-100: integrate without breaking what works

From day 31, integration can begin in earnest - but sequenced carefully. The default error is to integrate everything at once because "it's more efficient". It is not. It creates compounding risk and means that when something goes wrong (and something will), you cannot isolate the cause.

Sequence by risk, not by convenience. Finance and reporting integration comes early because the acquirer needs visibility. Customer-facing systems and processes come late because disruption there costs revenue. HR policies can wait until the legal requirements are met.

The 100-day milestone

At day 100, the acquirer should be able to answer three questions with confidence:

1. Do we have reliable management information from the combined business?
2. Have we retained the people we identified as critical?
3. Are the revenue assumptions in the investment thesis still intact?

If the answer to any of these is no, that is not a failure of execution - it is a signal that requires an honest conversation with the board and a revised plan. The value creation plan does not care what the original integration timeline said.

Why independent oversight matters

The people responsible for the integration are usually also the people who approved the deal. That creates a structural conflict: nobody wants to be the first to say the integration is off track, because that implies the deal was wrong.

Independent integration oversight - someone who was not in the deal room and has no stake in the original assumptions - creates the conditions for honest assessment. It also creates accountability for the integration plan itself, rather than leaving it distributed across functional leads who each have other priorities.

For PE-backed businesses, the cost of independent integration leadership over 100 days is a small fraction of the deal value at risk. The question is not whether you can afford it - it is whether you can afford not to have it.