Post-Acquisition Integration: The 90-Day Governance Playbook PE Sponsors Expect

McKinsey's 2025 Global Private Markets Report identified over 18,000 portfolio companies held beyond traditional holding periods. Longer holds amplify operational risk. And the single largest concentration of operational risk in any PE platform occurs in the first 90 days after an acquisition closes.

Most integration plans fail because they start with the wrong question. The typical plan asks: "What systems do we need to connect?" The correct question is: "What governance architecture does the acquired entity need to operate within the platform's control standards by Day 90?"

The difference matters. Systems integration can take six to twelve months. Governance installation can be completed in 90 days — and it is what the sponsor is actually evaluating when they assess whether an acquisition is "on track."

What Sponsors Actually Measure in the First 90 Days

PE sponsors do not measure integration success by whether two ERP systems are connected. They measure it by whether the acquired entity can produce a consistent monthly operating report, in the platform format, by the end of the first quarter. That is the functional definition of "integrated" in most sponsor relationships — the acquired entity is governable, reportable, and visible within the existing control infrastructure.

This means the integration plan must prioritize four things above all else: KPI alignment, reporting cadence installation, financial governance conformity, and leadership onboarding into the platform operating rhythm. Everything else — system migration, process harmonization, cultural integration — is important but secondary to these four governance foundations.

Phase 1: Day 1–30 — Control Foundation

KPI Definition Alignment

The acquired entity almost certainly defines its KPIs differently than the platform. "Revenue" might include or exclude intercompany transfers. "Headcount" might count or exclude contractors. "EBITDA" might use a different add-back convention. These definitional mismatches must be identified and resolved in the first two weeks — before the first combined operating report is produced.

The deliverable is a KPI reconciliation document that maps each acquired entity metric to the platform standard definition, identifies gaps, and assigns an owner responsible for producing the reconciled number by the first reporting cycle.

Reporting Cadence Installation

By Day 14, the acquired entity's leadership team should know exactly what reports are due, in what format, on what date, to whom. This is not a technology implementation — it is a governance communication. The acquired entity's Controller or CFO needs a reporting calendar, a template package, and a named platform counterpart who reviews submissions.

Financial Governance Baseline

The platform's approval matrix, spending authority thresholds, and capital expenditure process must be communicated and acknowledged by the acquired entity's leadership by Day 30. This does not require system integration. It requires a governance document, a signoff, and a verification mechanism.

Phase 2: Day 31–60 — Operating Rhythm

Phase 2 is about enrollment — the acquired entity's leadership team participates in the platform's operating cadence for the first time. The weekly ops call. The monthly operating review. The KPI submission cycle. This is where governance installation becomes operational reality.

The most common failure in this phase is passive participation. The acquired entity's team attends the meetings but does not contribute data, does not present their section of the operating review, and does not own their KPI narrative. Active participation must be explicitly required and tracked. If the acquired entity's GM is not presenting their P&L section of the monthly review by Day 45, the integration is behind schedule.

Integration Blocker Escalation

By Day 45, the integration plan will have encountered blockers — data that cannot be produced in the required format, a system that cannot generate the required report, a role that does not exist in the acquired entity's org structure. These blockers must be surfaced through a formal escalation process, not absorbed silently by the integration team. A documented integration blocker log with owner, severity, and resolution timeline is essential. The sponsor will ask about blockers in the first quarterly review — having a documented, managed list is fundamentally different from having no list at all.

Phase 3: Day 61–90 — Verification and Handoff

Phase 3 answers one question: Can the acquired entity operate independently within the platform's governance infrastructure? The test is not whether they can produce a perfect report. The test is whether the process runs without the integration team holding their hand.

The deliverables at Day 90 are concrete. A completed KPI reconciliation with the acquired entity producing platform-standard metrics independently. Two or more monthly operating reports submitted on time and in the correct format. An acknowledged financial governance framework with no open compliance gaps. An integration blocker log with all critical items resolved or formally escalated to senior leadership with a remediation timeline.

Integration Complete — What It Actually Means

Integration complete does not mean systems are merged. It does not mean cultures are aligned. It does not mean every process is harmonized. It means the acquired entity can be governed, reported on, and held accountable within the same control infrastructure as every other entity on the platform. That is what the sponsor is evaluating — and it is achievable in 90 days if the integration plan prioritizes governance over systems.

The firms that execute this well gain a compounding advantage. Each subsequent acquisition deploys the same governance installation playbook. The timeline compresses. The blocker list gets shorter. The operating review format is already standardized. The acquired entity's leadership team knows what to expect because the onboarding process is documented, repeatable, and institutional — not dependent on which operating partner happens to be available.

The best integration plans are boring. They are a checklist, a calendar, and a set of governance documents that install the same control architecture every time. The sponsor never remembers the integration that went smoothly. They remember the one that didn't — and that memory affects every subsequent capital allocation decision.