Strategy
Integration surprises cost 25-35% more. Here's what to audit first.
Most M&A due diligence stops at financials. Operational due diligence—examining systems, processes, talent concentration, and integration dependencies before close—is what separates deals that realize 80%+ of projected value from those that realize 50-65%. This checklist shows you what to examine and when.
Operational due diligence conducted 6-8 weeks before close examines the target's operational, financial, and commercial infrastructure across IT systems, process maturity, customer and supplier concentration, talent dependencies, and integration cost drivers. This practice surfaces hidden costs in system harmonization, customer migration, supplier renegotiation, and workforce decisions—allowing you to quantify integration spend before deal approval rather than discovering it after close, when remediation becomes reactive and expensive.
What good looks like
| Metric | Minimum | Strong | World-class |
|---|---|---|---|
| Deal Pipeline Conversion RateThe percentage of identified target companies or partnership opportunities that advance to letter of intent or binding agreement stage. | 12-18% | 18-28% | 28-40% |
| Post-Acquisition Value RealizationThe percentage of projected cost synergies and revenue synergies actually realized within 24 months of deal close. | 50-65% | 65-80% | 80-95% |
The spread between minimum (50-65% value realization) and world-class (80-95%) tells the story. That 30-point gap represents the difference between organizations that discover integration complexity after close versus those who quantify it before. Conversion rates rise from 12-18% to 28-40% for the same reason: disciplined operational screening eliminates low-fit deals before they consume resources and management attention. The driver in both cases is the same—operational due diligence that stress-tests integration assumptions rather than accepting the seller's operating model at face value.
Industry-Specific Benchmarks
These ranges are cross-industry. The figures differ materially by sector and company size.
Find benchmarks for your industry →Why the gap exists
The organizations realizing 80%+ of projected value share a discipline: they treat operational due diligence as a gate, not a courtesy. They spend 6-8 weeks—sometimes longer—examining how the target actually runs: which customer relationships are concentrated in one account manager, which suppliers are single-sourced, where processes remain manual or fragmented, which IT systems cannot talk to each other, which functions depend on parent-company shared services. They quantify the cost of fixing each gap before deal approval. Middle-tier performers conduct lighter due diligence, often compressed into the final weeks before close, focused on confirming financial statements rather than testing operational assumptions. They discover integration costs in the first 90 days post-close, when remediation options are constrained and disruption to ongoing business operations is highest.
The best performers also separate one-time integration costs from ongoing run-rate economics. They model what the business looks like at year-one stabilization—after systems are harmonized, duplicate functions are consolidated, and redundant processes are eliminated—distinct from what it costs to get there. This distinction changes deal economics: a target that looks expensive to integrate might be a better long-term fit than one that appears cheaper on first pass. Weaker performers often conflate integration costs with ongoing profitability, leading them to overpay for targets with low integration friction but also low strategic fit.
What leading organizations do
Pre-Close Operational Due Diligence: From Financial Audit to Operational Stress Test
Operational due diligence is not a vendor assessment. It is an intensive examination of whether the target can actually execute the financial projections driving deal economics—and what it will cost to make it capable if it cannot. Traditional due diligence focuses on whether the numbers are true: Did the target generate the revenue it claims? Are the expenses accurately recorded? Are there hidden liabilities? Operational due diligence answers a different question: Are the systems, processes, and people in place to sustain and grow that revenue at the margins the deal assumes?
Start with the operational DNA—the infrastructure that actually runs the business. This means site visits to manufacturing facilities, distribution centers, or regional offices; interviews with frontline operators, not just senior management; and validation of IT and process claims through technical assessment, not interviews alone. The roadmap for this runs three phases: discovery (documenting what exists), stress testing (modeling what happens when you integrate), and remediation planning (costing what it takes to fix). In a roll-up acquisition of regional operators or fragmented assets, this work is critical because the target likely operates independently with inconsistent systems, process maturity, and talent structures. You will find customer concentration (three customers representing 60% of revenue), supplier dependencies (single-source arrangements for critical inputs), undocumented processes (procedures that exist in one person's head), and IT infrastructure that cannot be integrated without wholesale replacement.
The output is a gap register: a list of integration costs with owner, timeline, and confidence level. This becomes your integration budget and your reality check on deal economics. Organizations that conduct this work reduce post-close integration cost overruns by 25-35% and improve the accuracy of deal economics by 40-50% because they are no longer discovering problems reactively—they are executing against a plan.
Leading Practice Report
Full detail: Pre-Close Operational Due Diligence
The full report covers:
- Expected benefits
- Core principles
- Key success factors
- Key metrics
- Risks and mitigations
- Implementation roadmap
Carve-Out Readiness: Ensuring Acquired Units Can Function Alone
When you acquire a subsidiary, division, or carved-out unit from a larger company, the target often lacks fully independent operational capabilities. Finance reports may flow to a parent-company consolidation process. IT infrastructure may depend on parent company data centers. HR and payroll may run through parent systems. Customer contracts may reference parent company obligations. These embedded dependencies are invisible during due diligence but become acute post-close when the unit must operate autonomously.
Carve-out readiness is the process of identifying these dependencies and eliminating them before or immediately after close. This means mapping which systems the target genuinely controls versus which it borrows from the parent; determining whether customer and supplier contracts transfer or require renegotiation; identifying which functions (compliance, audit, legal) the target must build from scratch; and establishing independent financial reporting and regulatory filing capability. In larger organizations, this requires dedicated resources—often a small carve-out team working parallel to the main integration effort. In smaller acquirers, it may fall to operations and finance leaders managing integration as an addition to their regular role.
Where carve-out planning succeeds, organizations reduce post-close operational disruptions by 40-60% because they stabilize business continuity while integration is happening rather than having to stabilize while also managing discovery of newly exposed dependencies. Revenue leakage from customer disruption, supplier non-performance, or missed compliance deadlines drops correspondingly. The alternative—learning post-close that a critical function was embedded in parent company operations—costs time, money, and often customer relationships.
Leading Practice Report
Full detail: Carve-Out & Standalone Readiness Protocol
Benefits, core principles, success factors, metrics, risks and the implementation roadmap.
Get the full report →Industry context
Roll-up acquisitions and platform builds face this most acutely because they acquire multiple smaller or regional operators, each with different systems and process maturity. A company acquiring three regional distributors will find three different IT platforms, three different customer relationship practices, three different inventory management approaches—and integration complexity scales faster than deal count. Private equity roll-ups depend almost entirely on this discipline because their return model assumes operational improvement and cost consolidation; underestimating integration cost or overestimating the speed of system harmonization directly reduces returns. In contrast, strategic acquirers integrating a competitor or complementary player into an established platform often have lower operational due diligence intensity because they are consolidating into proven systems and processes rather than building new ones. However, even strategic deals benefit from carve-out readiness assessment if the target was previously a subsidiary or division, because embedded dependencies create months of hidden friction.
Where to start
- List the functional and operational systems the target uses (finance platform, HR system, manufacturing execution system, inventory management, customer relationship management) and determine which ones the target owns versus which are provided by a parent company or landlord. This single exercise surfaces 70-80% of integration dependencies.
- Conduct customer and supplier concentration analysis: What percentage of revenue comes from your top 10 customers? Top 3? Do any single suppliers represent more than 15% of input costs? Are there single points of failure in distribution, production, or service delivery? Interview the sales team and operations leadership directly—don't rely on reports.
- Schedule site visits and technical assessments of IT infrastructure, manufacturing facilities, or distribution operations before the final weeks before close. Hire external technical resources (systems integrators, supply chain consultants) only if you lack internal expertise. The goal is to answer: What needs to be rebuilt, and what can we integrate as-is?
Ask us about operational due diligence frameworks for your specific deal structure—roll-up, carve-out, or platform consolidation—and how to resource it given your deal timeline and internal capability.
Start free with Ask Kepler →Advanced and emerging approaches
Advanced & Emerging Practices
Emerging practices are included with Ask Kepler Pro and Max.
Unlock these practices →