October 19, 2026 — I view integration planning before signing as a discipline of deal design. Its purpose is not to simulate control of a business that has not yet been acquired. Its purpose is to determine whether the operating case is sufficiently concrete to support the price, the terms, and the commitments a buyer is prepared to make.
Signing fixes more than a price
An acquisition agreement does not merely establish who will own an asset. It begins to fix the economic and practical conditions under which the investment case must be delivered: consideration, timing, access to information, transition obligations, risk allocation, employee matters, customer dependencies, and the remedies available when an assumption proves incomplete.
That is why I believe integration planning should begin before signing. If the plan starts only after the agreement is executed, the buyer may discover that its most important operating questions can no longer influence the transaction it has agreed to undertake. The price has been set. The allocation of risk has been negotiated. The scope of transition support may be vague or absent. The timetable may bear little relationship to the actual sequence of operational work.
This does not mean a buyer should attempt to manage a target before it owns it. It should not. Until closing, the businesses remain separate, and all planning must respect the legal and commercial boundaries applicable to the transaction. But restraint is not the same as postponement. A well-run pre-signing process can define hypotheses, identify dependencies, assign provisional accountability, and expose the decisions that will be required when ownership changes.
The relevant distinction is simple: pre-signing integration planning is not execution. It is preparation to execute responsibly.
A synergy estimate is not yet an operating plan
In an investment memorandum, value creation often appears as a concise bridge from current earnings to a future result. The categories are familiar: procurement, sales-force effectiveness, pricing, footprint optimization, systems rationalization, cross-selling, or overhead reduction. These can be valid sources of value. But categories are not initiatives, and initiatives are not cash flow.
For each material source of value, I would want the integration plan to answer several practical questions:
- What is the baseline? The plan should identify the actual revenue, cost, headcount, process, or asset base from which improvement is expected.
- What changes operationally? A saving cannot rest only on the observation that two businesses perform similar activities. It needs a defined change in process, supplier relationship, organization, system, or commercial practice.
- Who has the decision right? An initiative without an accountable owner is usually an intention disguised as a plan.
- What must happen first? Data access, customer consent, systems readiness, retention, contract assignment, or a management decision may be prerequisites rather than details.
- What does delivery cost? One-time spending, leadership capacity, disruption risk, and delayed benefits belong in the same analysis as the gross opportunity.
- What evidence would prove the thesis wrong? A credible plan gives decision-makers permission to reduce, defer, or abandon an initiative when the facts do not support it.
This discipline is not administrative. It is underwriting. Boston Consulting Group’s 2025 work on merger synergies similarly argues that integration planning should be linked directly to diligence so that estimates reflect operating realities and are owned by the people expected to deliver them. (bcg.com)
I do not regard a benefit as fully underwritten merely because it is plausible. It should be discounted until its baseline, dependencies, timing, cost, and ownership have been tested. If those elements cannot be established before signing, the appropriate response may be to lower the value attributed to the opportunity, seek more information, alter the terms, or decide that the risk is not acceptable.
The plan therefore has an important negative function: it identifies value that should not be paid for in advance.
The plan should change the agreement
The most useful pre-signing plans do more than create a list of post-closing workstreams. They reveal which elements of the transaction documentation matter to the operating case.
Consider a carve-out. The headline financial statements may show a profitable business, but the integration plan may reveal reliance on a seller’s enterprise-resource systems, payroll processes, procurement arrangements, insurance programs, product approvals, customer-service teams, or data environment. The question is not simply whether a transition-services arrangement exists. It is whether the services are sufficiently specific, durable, measurable, and aligned with the actual time required to establish independent capability.
The same principle applies outside carve-outs. A plan may show that the economics depend on retaining particular technical, commercial, or operational leaders; securing contractual consents; preserving a customer-facing process while systems are migrated; or maintaining a supplier relationship through a defined period. These are not post-closing inconveniences. They are deal facts.
I would separate the planning output into three categories before signing.
First, value initiatives. These are the actions expected to improve earnings or strategic position. They should be tied to a quantified baseline and a realistic implementation sequence.
Second, continuity obligations. These are the capabilities that must continue without interruption: invoicing, service delivery, product quality, customer response, vendor payment, employee administration, and decision-making authority. Continuity rarely receives the same attention as synergies, yet it is often the condition for realizing them.
Third, irreversible choices. These may include a system migration, facility decision, organizational redesign, brand transition, leadership change, or customer-contract approach. The plan should identify which choices must be made quickly, which can be sequenced later, and which should remain reversible until better evidence is available.
An acquisition agreement should not become a catalogue of management aspirations. Legal documents have their own purpose and structure, and counsel must determine the appropriate treatment of each issue. But the commercial team should be able to explain how the agreement supports the operating case—and where it does not.
Day one depends on decisions made beforehand
Day one is often described as a communications milestone. It is more accurately a test of continuity and authority.
Employees, customers, suppliers, and managers do not experience an acquisition as an abstract change in ownership. They experience it through concrete questions: Who can approve spending? Which commitments remain in force? Where does a customer escalate an issue? What happens to an open order? Which system is the source of record? Who makes a decision when the legacy organizations disagree?
Those questions cannot be answered well through a generic first-100-days checklist. They require a decision architecture prepared in advance.
That architecture need not presume every appointment or final organizational choice before signing. It should, however, define the roles required, the decisions that cannot wait, the information needed to make them, and the escalation route when facts are unclear. In private-equity integrations, McKinsey has emphasized identifying and ranking a limited set of critical decisions before close, alongside establishing comparable financial and full-time-equivalent baselines. (mckinsey.com)
The finance baseline deserves particular attention. Without a common definition of revenue, gross margin, labor, central costs, working capital, and implementation expense, post-closing performance can be measured against a moving target. A reported saving may be a reclassification. A delayed project may be mistaken for a failed one. A benefit may be counted by multiple teams. McKinsey has likewise recommended developing pre-close baselines that map comparable costs and business processes across the organizations being combined. (mckinsey.com)
I would rather enter closing with a small number of clear operating measures than with a large integration presentation. The measures should distinguish recurring value from one-time actions, gross opportunity from net benefit, and realized results from management estimates. They should also make visible the cost of disruption. A plan that reports only savings and not lost customers, missed service levels, delayed collections, or leadership turnover is incomplete.
Early planning is a form of downside protection
The usual argument for pre-signing integration planning is speed. Speed matters, particularly when a business requires immediate stabilization or when value depends on timely action. But speed is not the deeper reason to plan early.
The deeper reason is that the plan forces the buyer to confront the downside while it still has choices.
I would want to see the operating case tested against adverse but plausible conditions: a delayed systems migration; the departure of a key executive; lower-than-expected customer retention; a supplier refusing to revise terms; a slower-than-expected commercial launch; or a transition service ending before the replacement capability is ready. These are not predictions. They are tests of resilience.
A deal whose value depends on every integration workstream proceeding exactly as intended is not robust. The planning process should identify the few assumptions that matter most, establish early warning indicators, and clarify what actions are available if those assumptions weaken.
This can affect price, timing, diligence priorities, transition requirements, and the amount of capital reserved for implementation. More importantly, it can prevent a buyer from confusing a favorable base case with an adequate margin of safety.
The most valuable pre-signing plan is not the one that promises a frictionless integration. It is the one that makes friction visible while the buyer can still respond.
The appropriate output is a decision-ready blueprint
A review-ready pre-signing integration plan does not need false precision. It should not pretend to know every individual role, every system configuration, or every future customer decision. It should be detailed where the investment case is fragile and concise where flexibility is valuable.
In my judgment, the minimum useful blueprint includes:
- a statement of the deal’s operating logic, including what should be integrated, what should remain distinct, and why;
- a value bridge with initiative-level baselines, owners, timing, costs, and dependencies;
- a continuity map covering the activities that cannot fail at closing;
- a critical-decision calendar for day one, the first month, and the first quarter;
- a people plan that identifies indispensable capabilities and decision coverage rather than treating retention as a generic objective;
- a systems and data map that identifies the sources of record, migration dependencies, and interim controls;
- a downside register that names the assumptions most likely to impair value; and
- a measurement cadence that reports realized operating outcomes, not only the completion of tasks.
This blueprint should be revised as diligence advances. Its purpose is not to create the appearance of certainty. Its purpose is to convert uncertainty into a set of explicit choices.
Signing should confirm preparation, not begin it
I do not expect an integration plan to eliminate uncertainty before signing. No serious acquisition process can do that. New facts will emerge after closing, and a capable owner must adapt without losing discipline.
But there is a meaningful difference between uncertainty that has been identified and uncertainty that has been ignored. The first can be priced, structured, monitored, and managed. The second often reappears as an avoidable surprise after the buyer’s flexibility has narrowed.
For that reason, I believe integration planning belongs in the period before signing. It is part of the work that determines what is being bought, what must be protected, what can credibly improve, and what should remain contingent. A signed agreement should reflect an operating case that has been tested against reality—not a hope that reality will become clearer once the transaction is complete.
Sources reviewed
- Synergy Planning Should Start Sooner Than You ThinkBoston Consulting Group
- Winning at private-equity integrationsMcKinsey & Company
- The CFO needs to be very involved in merger integrations for companies to capture the most valueMcKinsey & Company