How to build an acquisition integration plan
A transaction can close successfully and still lose value immediately afterwards. A disciplined integration plan protects continuity, converts the investment thesis into accountable action and gives leaders reliable financial visibility from Day One.
Where Finance Excellence Lives.
Executive summary
- Begin with the value case: define what the acquisition must deliver before redesigning structures or systems.
- Give the integration office authority: it should resolve dependencies and accelerate decisions—not merely collect status reports.
- Separate stabilisation from transformation: Day‑One continuity, first‑100‑day control and long-term operating-model integration require different priorities.
- Place finance at the centre: align accounting policies, cash control, reporting, purchase accounting, synergy baselines and integration costs early.
- Measure outcomes, not activity: completed tasks matter only when they protect revenue, control risk or capture value.
Start with the value case—not the organisation chart
The plan should translate the acquisition thesis into a small number of measurable value drivers: revenue growth, geographic reach, capability, technology, purchasing leverage or cost reduction. Each driver needs a validated baseline, accountable owner, delivery milestones and a decision rule for revising assumptions.
Finance should validate the baseline before synergy targets are locked. Align the treatment of revenue, overhead, inventory, capitalised costs and working capital so leadership is comparing like with like. This is where insights from quality of earnings and financial due diligence should flow directly into integration planning.
“Integration is not a race to standardise everything. It is a controlled sequence of decisions that protects the business while converting the deal thesis into measurable value.”The CFO HQ perspective
Build the plan around three phases
Day One: continuity and confidence
Employees need clarity on leadership, payroll, benefits and immediate changes. Customers and suppliers need reassurance that service, contracts and contacts remain intact. Finance must control cash, delegated authority, purchasing, customer collections, tax filings and close responsibilities. The checklist should reflect the target’s operating reality rather than a generic template.
First 100 days: control and momentum
Diagnose the close, chart of accounts, forecasting, controls, systems, contracts and key-person dependencies. Distinguish committed value—supported by a baseline, owner and executable plan—from opportunity, which remains a hypothesis. Establish one reliable performance view even if temporary manual consolidation is required. The goal is timely control, not a premature systems migration.
Operating-model integration: deliberate structural choices
Once stable, leadership can harmonise policies, consolidate entities, redesign processes, rationalise vendors and migrate systems. Full absorption is not always appropriate: a high-growth target may need commercial autonomy while finance, governance, risk and selected shared services are integrated. The degree of integration must follow the value thesis and customer requirements.
Give the integration management office authority
The integration management office (IMO) should set priorities, resolve cross-functional dependencies, identify risks and hold owners accountable. It needs a visible executive sponsor, an empowered integration leader and workstream leads across finance, commercial, operations, people, technology, legal and communications.
Use a concise governance rhythm: weekly workstream reviews for delivery and an executive steering committee for material decisions. Reporting should show milestones, value impact, integration cost, key risks, dependencies, decisions required and named owners.
| Workstream | Day‑One control | First‑100‑day outcome | Executive evidence |
|---|---|---|---|
| Finance | Cash access, authority, close ownership and payment control | Aligned reporting, policies, forecast and synergy baselines | Integrated pack, cash forecast and control log |
| Commercial | Customer ownership and communication | Revenue-retention and cross-sell plan | Pipeline, churn and account-risk view |
| People | Leadership, payroll and critical-role clarity | Targeted retention and organisation decisions | Critical-role coverage and attrition risks |
| Technology | Access, cyber and service continuity | Architecture, data and migration decision | Systems map, risk register and roadmap |
| Operations | Supply, delivery and safety continuity | Process ownership and performance baselines | Service, quality and capacity measures |
Define decision rights before Day One
Document a transitional authority matrix covering spending, contracts, hiring, pricing, customer commitments, policy exceptions and data access. State which decisions remain local, which require parent approval and which belong to the steering committee. This is particularly important when the acquired organisation previously operated through founder-led judgement.
Illustrative integration priority view
Critical
Critical
High
Sequence
Sequence
Illustration only—not a universal ranking. Priorities must be adapted to the transaction thesis, sector, regulation and target risk profile.
Put finance at the centre of value capture
Finance creates the common language that connects operational actions to enterprise value. The workstream should align accounting policies, reporting controls, purchase accounting, forecasts, integration costs and synergy tracking. Track receivables, inventory, payables and liquidity weekly during early integration; changes in billing or collections can create cash pressure even when reported profit appears healthy. See the working-capital optimisation guide and the guide to a faster monthly close.
Talent decisions also require financial discipline. Retention packages should be targeted, time-bound and linked to critical knowledge or value delivery. Broad commitments made under pressure can dilute the deal case without addressing the real risk.
Treat culture as a business risk
The practical test is not whether cultures are identical, but whether decision-making, accountability, customer service and risk escalation can operate together. Identify roles critical to revenue, product, operations and financial control. Communicate what is known, what remains undecided and when decisions will be made. A transparent process is more credible than unsupported assurances.
Growth acquisition with separate systems and concentrated knowledge
Situation: A buyer acquires a specialist services business whose founder controls key relationships, while financial reporting depends on spreadsheets and a separate ledger.
Response: The IMO protects customer ownership, establishes transitional decision rights, retains critical specialists, creates a manual integrated reporting pack and sequences ERP migration after close stability.
Decision impact: Leadership gains early visibility without disrupting sales, preserves key knowledge and makes the systems decision from evidence rather than timetable pressure. This example demonstrates the method and does not represent an actual engagement or guaranteed outcome.
Executive integration checklist
Does every workstream connect to a validated deal driver or risk?
Are decision rights, escalation routes and reserved matters explicit?
Can leadership see revenue, cash, cost, control and synergy performance together?
Can the internal team integrate while protecting business-as-usual delivery?
Review the wider M&A trends shaping the next deal cycle and our finance-led post-merger integration framework.
Protect value after the deal closes
The CFO HQ supports buyers and leadership teams with integration planning, finance mobilisation, reporting, synergy governance and interim execution capacity. Bring finance into the integration thesis before the timetable compresses.
Professional disclaimer: This article provides general strategic information only. It is not accounting, legal, tax, investment, employment or financial advice. Integration plans should reflect the specific transaction, jurisdictions, regulatory obligations, contracts, people risks, systems and evidence available.
