The 90-Day Post-Acquisition Integration Playbook

The first 90 days after an acquisition are where most of the value either gets locked in or quietly slips away. The work that happens in this window determines whether the investment thesis becomes real or stays as a slide deck. I have been on the inside of 22 of these integrations, mostly inside a PE-backed group, and the same patterns show up every time.

This is the playbook I wish someone had handed me on day one of my first integration. It will not make a bad deal good. But it will help you avoid the avoidable mistakes that destroy value in the first quarter after close.

Why 90 Days

The 90-day window is not arbitrary. It is the period when goodwill is highest, attention is focused, and the people involved still expect change. After day 90, the new normal sets in. Decisions get harder. Resistance hardens. Quick wins stop being quick.

If the integration drifts past 90 days without clear progress, the cost of getting back on track usually doubles. I have seen integrations stretch to 18 months when they should have been settled in three. Each extra month adds friction, distraction, and lost margin.

What "Integration" Actually Means

Integration is a vague word that covers very different things. Before you start, get clarity on which of these models you are running:

Absorption. The acquired business is folded into the buyer's structure, systems, and brand. Highest synergies, highest disruption.

Preservation. The acquired business runs largely independently, with minimal changes. Lowest disruption, lowest synergies.

Symbiosis. The acquired business keeps its identity but integrates back-office, finance, IT, and key processes. Most common in PE deals.

Holding. The acquired business is left alone except for financial reporting. Used when the value creation thesis is purely operational improvement, not integration.

Most of what follows assumes a symbiosis model, which is where most mid-market PE acquisitions land.

Days 1 to 14: Stabilise

The first two weeks are about not breaking anything. Resist the urge to make big changes. Focus on continuity, communication, and information.

Day 1: Send the announcement to staff before they read about it on LinkedIn. Tone matters. Be honest about what is changing and what is not. Confirm payroll will run on time. This is the single most important signal of stability you can send in week one. Brief all customer-facing teams on the messaging. Customers will ask. Have answers ready.

Days 2 to 7: Run individual conversations with the top 10 people in the acquired business. Listen more than you talk. Take notes. Do not make promises. Map the critical systems: payroll, finance, customer support, sales, deployment. Who runs them? What could break in the first 30 days? Establish a single integration management cadence. Weekly leadership calls, daily working sessions for the first fortnight.

Days 8 to 14: Publish the integration plan internally. People need to see the shape of what is coming. Vagueness breeds anxiety. Confirm the org structure for the next 90 days. It does not have to be the final answer. It does have to remove uncertainty about who reports to whom. Schedule customer conversations with the top 20 accounts. Reassurance from leadership in the first month is worth far more than any marketing email.

Days 15 to 45: Diagnose and Decide

Once the immediate stability work is done, the next month is about understanding what you have actually bought and making the decisions that will shape the next year.

Operational diagnosis. Get into the systems. Look at the actual financials, not the deal model. Reconcile any differences. Audit the technology stack. What is legacy? What is modern? What is fragile? Where are the dependencies? Review the sales pipeline. Stress test the assumptions in the deal model. If revenue is going to slow down, you need to know now. Map the customer book. Who are the high-value customers, the at-risk customers, the loss leaders?

People decisions. Identify the people you need to keep. Build a retention conversation with each of them in the first 30 days. Do not wait for the bonus cycle. Identify the gaps. Where is the team thin? What needs hiring in the first 90 days? Make the hard people decisions early. If someone does not fit the new structure, the right thing to do is say so quickly. Dragging it out hurts everyone.

Quick wins. Find three or four operational improvements that can be delivered in the first 60 days. These build credibility for the broader integration. Examples that often work: consolidating duplicate vendor contracts, simplifying internal reporting, fixing one obvious customer experience issue.

Days 46 to 90: Execute and Prove

The final third of the playbook is about delivery. By now, the diagnosis is done, decisions are made, and the team knows what is coming. The work shifts from analysis to execution.

Technology integration. Run the major IT decisions: identity, email, productivity, file sharing, communications. Move with discipline. These are unglamorous but they unlock everything else. For SaaS-heavy businesses, consolidate the contracts that overlap. Most acquired businesses have shadow IT that nobody has mapped. Do not try to migrate the core product platform in the first 90 days unless it is actively breaking. Bigger architecture changes belong in months 4 to 12.

Financial integration. Bring the acquired business onto the buyer's reporting cadence. Standardised monthly close, single chart of accounts, single FP&A model. Connect the systems where it matters. Payroll, billing, expense management. Not everything needs to migrate at once. Set up the management information that the deal sponsors need to see synergy delivery against the model.

People and culture. Run an all-hands at the 60-day mark. Be honest about progress, friction, and what is next. People remember leadership that levels with them during change. Roll out shared values, recognition processes, and any cultural norms that matter to the buyer's operating model. Celebrate the early wins publicly. Stories travel further than dashboards.

Customer and commercial. By day 90, the top 50 customers should have heard from someone senior on the buyer's side. If they have not, you are behind. Pricing decisions can wait until month 4 or 5 in most cases. Early price changes are the fastest way to break trust. Cross-sell opportunities should be mapped but not aggressively pursued in the first quarter. Build the relationships first.

What Good Looks Like at Day 90

By the end of the first quarter, a well-run integration has:

• A clear, agreed integration plan in place with progress tracked weekly.
• All critical systems either integrated or on a credible plan.
• The top 50 customers spoken to and reassured.
• A retained team with the people who matter most still in their seats.
• Three or four quick wins delivered, creating credibility for the rest of the work.
• A clean, weekly management information pack going to the deal sponsors.
• The first synergies showing up in the numbers, even if they are modest.

What it does not have:

• A detailed five-year IT transformation plan (that is months 4 to 12 work).
• Major redundancies executed in week one (that almost always backfires).
• A new brand or website (way too early).
• Aggressive cross-selling (relationships first).

Where Most Integrations Go Wrong

Across the 22 integrations I have been part of, the failure modes cluster around the same few mistakes:

1. Trying to do too much too fast. Buyers underestimate how much disruption people can absorb. Pace yourself. The integration is a marathon disguised as a sprint.

2. Underinvesting in communication. People will fill silence with the worst possible interpretation. Over-communicate. Then communicate more.

3. Letting the integration become an IT project. It is not. It is a leadership project that has technology underneath it. Treat it like an IT project and you lose the people work.

4. Skipping the diagnosis. The temptation is to come in with a fixed plan from day one. Do not. The first two weeks should be mostly listening.

5. Neglecting the mid-tier. The senior leadership and the front line both get attention. The middle layer is where work actually gets done, and it is where most integrations lose momentum.

How I Help

I work with PE firms and their portfolio companies as a fractional CTO during the integration window. Sometimes it is hands-on technology leadership for the first 90 days while the permanent CTO is hired. Sometimes it is advisory support to an existing team that needs more bandwidth. Sometimes it is just a second opinion on the toughest calls.

I have advised on £300m+ of PE and VC investment decisions and led 22 integrations from the inside. If you are in the planning stage of an acquisition or mid-way through an integration that is not landing, get in touch.