90-day post-close kit.

The Window That Closes Faster Than Most Operators Realize

Every PE-backed portfolio company in its first year post-close has a specific window. The window starts on Day 1 and closes somewhere between Day 90 and Day 180, depending on the operator and the operation.

Inside the window, the team expects operating change. The acquisition signaled that things would be different. New operating disciplines are absorbed culturally because the team has already absorbed the cultural shift of new ownership. Decisions move faster because everyone is recalibrating.

Outside the window, the team has settled into the new normal — which usually means the prior owner's operating system with minor adjustments. The operating workarounds the team had been using under prior ownership have become ingrained. Cultural absorption of new discipline becomes much harder. The window has closed.

The 90-Day Post-Close Kit is the engagement-tier kit built around this window. It runs at the portco in the first 90 days post-close, installing the operating overlay — cadence, decision rights, dashboards, OKR tree — before the integration debt accumulates and the window closes.

This essay covers why the window matters, what happens to portcos that miss it, and what makes the kit's compressed 90-day install land instead of producing the standard slow integration that mid-market PE has been running for years. The kit guide covers the structural mechanics; this is the operator narrative.

What the Deal Team Doesn't Know to Tell You

The deal team's 100-day plan is usually structurally optimistic in three specific ways. Each one is addressable; the addressability requires recognizing the pattern first.

The plan models operating capacity that doesn't yet exist. The plan assumes the portco's existing leadership team can execute against the deal thesis at the pace the model requires. Often the team can; often the team needs structural support before it can. The plan doesn't usually specify what that support looks like or who provides it.

The plan defers integration debt. The plan focuses on the visible operating priorities — revenue growth, cost synergies, customer expansion. The operating-system gaps that would compound over the first year — decision rights ambiguity, cadence drift, dashboard inconsistency — get less attention because they're not in the deal-thesis numbers. The compounding cost shows up at month 9-15, when the operating-system gaps have produced delivery failures the original plan didn't anticipate.

The plan assumes the GM has bandwidth to build the operating system while running the operation. Most GMs don't. The bandwidth to install foundational operating infrastructure is the same bandwidth required to execute on the operating priorities; the two compete. Without external support, the GM picks one or the other. Usually they pick the operating priorities and defer the operating-system work, which produces the integration debt the plan didn't model.

The kit is the structural fix for all three. It provides the operating capacity. It addresses the integration debt before it compounds. It augments the GM's bandwidth so the operating system and the operating priorities both get built in the same 90-day window.

The Kit's Sequencing Logic

The 90-Day Post-Close Kit runs in three sequenced phases. The sequencing matters because installing the kits in the wrong order produces installs that don't take.

Days 1-14: Diagnostic and alignment. Two-layer Ops Health Check (new GM + a senior leader from the prior team). Perception-gap report. Alignment with the sponsor on scope and outcomes. Schedule for the install sequence. This phase is critical because the diagnostic surfaces which operating-system gaps are most expensive — which informs the sequencing of the subsequent phases.

Days 15-30: Cadence and decision rights. Decision Rights Matrix install (two working sessions). Cadence Calendar install (one working session). First occurrence of each new forum happens within this window. The kit runs these first because they're the foundation that the subsequent installs depend on. Operations that try to install dashboards or OKR trees without first establishing decision rights and cadence produce installs that don't anchor.

Days 31-60: Metric architecture and dashboards. OKR / KPI tree built with leadership. Function dashboards designed and instrumented. Channel protocol published. Weekly retro launched. The dashboards begin producing operating data; the cadence begins exercising the data; the operating system begins running on numbers instead of narrative.

Days 61-90: Refinement and handoff. Three weeks of operating the new system. The operating partner observes, surfaces friction, refines the install. The team experiences the cadence under at least one real operating stress (a missed target, a customer escalation, a process failure) — the test is whether the new system handles it without breaking. Final two weeks: handoff. Documentation transfers to the portco's operating wiki. Operating partner steps back. 30/60/90-day follow-ups scheduled.

The 90 days is compressed deliberately. The window is the constraint; trying to spread the work over 6 months produces installs that don't land because the team has already settled into the post-close workarounds before the new system arrives.

What Gets Deferred (And Why)

The kit's discipline includes explicit deferral of three categories of work that operators sometimes want to include in the post-close engagement.

A3 / PDCA improvement cycles are deferred to month 4-6. The continuous-improvement discipline requires the foundation (cadence, dashboards, decision rights) to be stable before it can land. Operations that try to install A3 cycles in the first 90 days produce shallow cycles that don't compound.

Three-workflow AI install is deferred to month 6-9. AI deployment requires trusted data, which the dashboards need at least a quarter to validate. Operations that try to install AI workflows in the first 90 days produce deployments that amplify the data problems the dashboards are still surfacing.

Portfolio rollout playbook contributions are deferred to month 6+. The portco can become a learning input to the platform-level playbook after the install has stabilized. Operations that try to feed the portfolio playbook from a portco still in install mode produce inputs that are too noisy to be useful.

The deferral discipline is intentional. Installing too much in the first 90 days produces breadth without depth — the new system gets adopted nominally and abandoned operationally because the team cannot absorb the change. Three months for the foundation; the rest builds on top.

What "Good" Looks Like at Day 90

Healthy installs share four properties at the 90-day mark.

The cadence is running without the operating partner. The GM and leadership team are running their own working sessions, retros, and dashboards. The operating partner has stepped back to observer and is no longer scripting the meetings.

The Decision Rights Matrix has been exercised on real decisions. At least five decisions in the first 90 days have routed according to the matrix, including at least one where the CEO deferred to a named owner whose call would not have been the CEO's preference. The deferral is the validation that the matrix is real.

The dashboards have produced their first material catch. A red KPI surfaced a problem early, the corrective action protocol ran, and the issue was addressed before it became a quarter-defining event. This catch is the operating ROI on the install — it pays for the engagement within the first quarter.

The team is using the new system without external prompting. Channel protocol is being followed. Retro is being run. Dashboards are being refreshed. The behavior change has taken hold without ongoing reinforcement from the operating partner.

The Conversation With the Sponsor

The kit's outcomes are visible to the sponsor at the first post-install quarterly board review. The conversation that surfaces is structurally different from a standard post-close board conversation.

Standard post-close board conversation: The sponsor asks diagnostic questions about the operating health, the GM provides narrative answers, the sponsor extracts confidence based on the narrative. Most of the meeting is the sponsor probing for issues the operating data doesn't yet surface.

Post-install board conversation: The sponsor opens to a one-page operating dashboard with five KPIs per function, a decision-matrix update, a cadence calendar, and an OKR tree. The diagnostic questions are answerable in seconds with reference to the operating data. The meeting moves from "is this portco okay" to "how do we accelerate the strategic priorities."

The shift in conversation type is the most underappreciated benefit of the kit at the platform level. Operating partners running the kit across multiple portcos report that the first board conversation with the installed operating system reframes the sponsor's read of the portco from "watching closely" to "operating well, ready for the next phase."

The shift compounds. Subsequent quarterly reviews stay in the strategic-acceleration mode rather than reverting to diagnostic. The sponsor-portco relationship matures faster than it would have under standard post-close support.

What to Do at Day 1

If you're a new GM landing at a PE portfolio company in the first 90 days post-close, the kit's install path is concrete.

Take the Ops Health Check on Day 4. Solo. The baseline tells you what you've inherited.

Have the prior owner's senior leader take the assessment separately, Day 7-10. The two-layer report surfaces the perception gap that tells you which operating-system pieces were being carried personally by the prior owner.

Engage the kit by Day 14. The 90-day window is real; engaging by Day 14 leaves 76 days for the actual install. Engaging later compresses the install in ways that hurt the take rate.

Commit to the deferral discipline. No A3 cycles, no AI deployment, no portfolio rollout contributions in the first 90 days. The discipline is what makes the foundation install land.

The kit guide at /playbooks/ninety-day-post-close-kit covers the structural detail. This essay is the operator narrative for why the window matters and what makes the compressed 90-day install land instead of producing standard slow integration. If you're in or about to be in this situation, the kit is the engagement that protects months 4-12 of your bandwidth from being consumed by integration debt that should have been addressed in the first 90 days.

90 days. One portco. The operating overlay installed before the integration debt accumulates. The GM gets back twelve months of bandwidth that would otherwise have been spent compensating for operating-system gaps.