The First 90 Days Post-Acquisition: What Nobody Documents.

The deal is done. The press release has gone out. The advisors have been paid. The founders shook hands and smiled for the camera. And on Monday morning, two organisations that have spent the past six months presenting their best selves to each other have to actually work together.

This is where most acquisitions fail. Not in the diligence. Not in the structuring. In the first 90 days — in the meetings, the miscommunications, the small decisions that signal to each side whether the other can be trusted, and the cultural fractures that, once visible, are extraordinarily difficult to close.

We document these 90 days differently from most post-merger integration frameworks. Most frameworks focus on systems consolidation, process alignment, and synergy tracking. All of that matters. What it misses is the human layer — the one that determines whether the business you bought is still intact six months after you bought it.

70% of M&A value destruction occurs in the first year post-close, not at signing. Day 3 is when experienced integration leads can identify the cultural fracture points. 6 months is the average time before key person departures become visible in performance data.

Everything that happens in the first ten days is a signal. The acquired team is watching everything. How does the acquirer communicate? Who has access to whom? Are the founders still respected, or have they visibly been sidelined? Is the first all-hands meeting conducted with genuine curiosity or with a roadmap presentation that makes clear decisions have already been made?

The most common mistake acquirers make in the first ten days is filling the silence with announcements. Announcements about structure, about branding, about reporting lines, about systems. All of these feel like progress to the acquirer. To the acquired team, they feel like occupation.

The founder stops being in the room where operational decisions are made within the first two weeks. This signals to the team that their previous leadership has been neutered — and that their institutional knowledge is not valued.

The first cross-company meeting is about reporting rather than about customers. This signals that the acquirer's primary interest is control, not value creation.

Key people don't know who to call for basic operational questions. Unclear authority structures in the first week create anxiety that compounds daily.

Acquirer employees refer to the acquisition as "the acquisition" rather than by company name. Small linguistic signal, significant cultural indicator.

"You didn't buy a balance sheet. You bought people who chose to build something together. The first ten days tell them whether that choice is still respected."

By day 11, the acquired team has formed an opinion. It may be provisional, but it exists. The decisions made in the following month either confirm or revise it. This is the window in which process and cultural integration decisions have the greatest impact — and the greatest risk.

The most consequential decision in this window is almost never about systems. It is about who decides what. Ambiguity about decision rights — who approves a new customer contract, who signs off on a hire, who has budget authority for what — creates paralysis in the acquired team and frustration in the acquirer. Both sides fill the ambiguity with assumptions that are usually wrong.

We recommend a Decision Rights Map be produced and distributed before day 15. Not a full org chart. A specific document that answers, for the 20 most common operational decisions, who decides, who is consulted, and who is informed. It is unglamorous. It is the single most useful integration document we've seen.

The other critical decision in this window: what stays, and what changes. Acquirers who change everything fast signal insecurity. Acquirers who change nothing signal lack of conviction. The businesses that integrate well make a small number of deliberate, explained changes early — and communicate clearly what will remain stable and for how long.

The most reliable predictor of integration failure is not financial — it is the departure of the person who held institutional knowledge that wasn't documented anywhere. Every SMB has one: the person who knows why the pricing model is structured that way, why that customer gets special treatment, why that process exists.

Identify them by day 10. Retain them before day 30. Because by day 60, if they've decided to leave, they're already interviewing.

By day 46, the early goodwill has been tested. The teams have had their first real disagreements. The systems integration project has hit its first serious obstacle. The customer who was told "nothing will change" has noticed something has changed. This is no longer the deal — this is the business. How you operate in this phase determines whether the acquisition creates or destroys value.

The two biggest failure modes in days 46–90:

Synergy acceleration before cultural stability. Acquirers feel pressure to demonstrate the synergies that justified the deal price. They push for cost savings, cross-selling initiatives, and process harmonisation before the two teams trust each other enough to collaborate on them. The result is resistance, workarounds, and the appearance of integration without the reality.

The 90-day review as verdict. Many acquirers conduct a formal 90-day integration review. The framing matters enormously. Reviews framed as performance assessments — "are we getting what we paid for?" — create defensiveness and political behaviour. Reviews framed as learning exercises — "what do we now understand that we didn't at day one?" — surface the information you actually need to manage the integration well.

The official integration documentation — the workstreams, the synergy tracking, the systems migration plan — exists in most acquisitions. What is almost never documented is the human intelligence that determines whether the integration succeeds.

Document these by day 30: the five people whose departure would be most damaging and why; the three customers who most need personal attention in the transition period; the two internal processes at the acquired company that work better than yours and should be adopted rather than replaced; and the one cultural practice of the acquired company that the acquirer team finds uncomfortable but that the acquired team considers non-negotiable.

That last one is the most important. Every acquisition has it. Finding it early, naming it, and deciding consciously what to do about it — rather than letting it fester into a culture war — is what separates integrations that work from those that don't.