March 22, 2026 · Caelon
How to Structure a 100-Day Integration Plan That Actually Works
The 100-day integration plan is a standard artifact in PE-backed acquisitions. Every operating partner has a template. Every platform CEO has built one at least once. The format is consistent: a phased timeline with task categories, owners, and deadlines arrayed across Day 1, Day 30, and Day 100 milestones.
The format is not the problem. The problem is that the plan is disconnected from the diligence work that preceded it.
The handoff boundary
An advisory team runs diligence for 6-8 weeks. They produce a quality of earnings report. They flag findings across financial controls, revenue recognition, customer concentration, HR, IT, and operations. This work product represents hundreds of hours of analysis.
The deal closes. The diligence team considers their work complete.
The integration team opens a blank spreadsheet. They build a plan from scratch. They may recall some of the major findings. They will not recall most of them. The working capital adjustment from QoE Section 4.2 does not appear on the integration checklist. The customer concentration risk flagged in the commercial diligence does not generate a retention task. The IT finding about homegrown ERP does not trigger a migration workstream.
The information existed. It did not cross the boundary.
This is not a people problem. The diligence team and the integration team are often the same people at a 12-person platform company. The problem is that diligence outputs and integration inputs are treated as separate artifacts with no structured connection between them.
The cost of disconnection
| Diligence Finding | What Should Happen at Close | What Actually Happens |
|---|---|---|
| Working capital normalized at $200K above seller estimate | Day 1 task: verify WC calculation, assign CFO | Finding filed in QoE folder. Variance discovered at month 6. |
| Top 3 customers = 48% of revenue | Day 1 task: retention outreach plan with owners | Generic "customer communication" added to plan. No specificity. |
| ERP is homegrown, no audit trail | Day 30 task: migration assessment and timeline | IT assessment starts at Day 60 when someone remembers. |
| Two key employees have no non-competes | Day 1 task: retention conversations with specific terms | Discovered as a risk at month 4 when one employee leaves. |
| Revenue recognition policy inconsistent with platform | Day 30 task: align policies, restate if needed | CFO catches it during first consolidation. 80-hour fix. |
Each row represents real value at risk. Not hypothetical risk — the kind that shows up as a $200K surprise, a departed employee, or an 80-hour emergency project.
What a linked plan looks like
The integration plans that work share one structural property: every major task traces to a specific diligence finding.
Not "migrate to our ERP" as a generic line item. Instead: "Working capital adjustment flagged during QoE — seller ERP does not track WIP accurately. Migrate to platform ERP by Day 60. Parallel operation Day 15-45. Owner: CFO. Source: QoE Section 4.2, financial controls assessment."
This traceability produces three outcomes:
Completeness. If every diligence finding generates at least one integration task, nothing is forgotten. The finding has an owner, a timeline, and a status.
Context preservation. At month 6, when someone asks why the ERP migration was prioritized over branding alignment, the answer is in the system. The decision traces to a finding. The finding traces to a risk. The risk has a dollar amount.
Defensibility. When the PE sponsor reviews the integration plan, every task maps to evidence. Priorities are derived from diligence, not guesswork.
The phasing structure
Day 1: Stabilization
The acquired company's general manager arrives on Day 1 with a new owner. The team is uncertain. The worst response is a 200-line spreadsheet.
Day 1 tasks should address three categories: communication, access, and compliance.
- All-hands announcement with clear messaging on what changes and what does not
- System access provisioned in both directions
- Hard-deadline compliance items: insurance binders, bank signatories, regulatory notifications
Nothing else. No ERP migration. No branding alignment. Stabilize.
Day 2-30: Foundation
This is where diligence findings drive the plan. Each finding rated High or Critical during diligence generates a corresponding task in the first 30 days.
- Financial controls alignment, linked to QoE adjustments
- Key employee retention conversations, linked to HR findings
- Concentrated customer outreach, linked to commercial diligence
- IT assessment with migration recommendation, linked to technology findings
Day 31-100: Execution
System migrations. Process alignment. Vendor consolidation. Synergy capture initiatives.
The differentiator: every task in this phase ties to a measurable outcome from the deal model. Not "consolidate insurance" as a wish. Instead: "Consolidate commercial liability policies. Projected savings: $45K/year per deal model assumption 3.2. Owner: COO. Deadline: Day 75."
The compounding opportunity
The aspect of 100-day plans that receives the least attention is their potential to improve across deals.
A platform company doing 3-4 add-ons per year generates a substantial dataset of finding-to-task mappings. The integration challenges that surprised the team on deal #1 should be anticipated items on deal #2. By deal #4, the plan should substantially auto-generate from the diligence findings, because the system contains a library of precedent: "Last time we acquired a company with homegrown ERP, migration took 90 days. Allocate accordingly."
Most platform companies never reach this state. Each plan starts from a blank sheet. The institutional knowledge lives in people's heads — subject to turnover, recency bias, and the limits of human memory.
The firms that build compounding integration playbooks will execute faster, capture more synergies, and reduce the marginal cost of each subsequent acquisition. The firms that do not will continue to treat every deal as if it were their first.
Caelon connects diligence findings to integration tasks automatically, with Day 1/30/100 execution tracking and playbooks that compound across acquisitions. Request a demo.