Decision rights before systems: what Day 1 readiness actually requires
Ask a room what Day 1 readiness means and most of the answers will be about systems. Which ERP survives, when the two payrolls merge, whether the reporting pack can be produced on the old chart of accounts. Those are real questions, and they are almost never what stalls an integration. What stalls an integration is that nobody can say who decides.
The systems question is a decoy
Systems decisions are visible, expensive and easy to put on a plan, which is why they get attention first. Decision rights are invisible, cost nothing to document and are excruciating to retrofit. Integration planning across 10-plus global functions at a $50B pharmaceuticals producer identified $400M+ in synergies and held future-state finance spend below 1% of revenue, but the change that made the rest of it possible was more prosaic: decisions moved roughly 30% faster once the governance protocols, escalation paths and decision rights were written down.
Faster decisions are not a soft benefit in an integration. Every week a decision sits unmade, two organizations keep operating on two sets of assumptions, and the cost of reconciling them later compounds.
What actually needs writing down
The list is shorter than most integration playbooks suggest. Who owns each functional workstream, and who they escalate to by name rather than by title. Which decisions belong to the integration management office and which stay with the business. What threshold sends a decision up, and how long it can sit before it goes up automatically. And who signs, on the day, when two policies conflict and both are defensible.
Standing up the Americas PMO across three merged entities at an $8B global commercial real estate services business meant applying that structure to 75+ projects that had been running independently. Reporting lag fell more than 40% and onboarding cycles came down roughly 30%, not because the projects changed but because the path from question to answer did.
Synergy models need an owner inside finance
A synergy model maintained by the integration team and a forecast maintained by finance will diverge, and the divergence will surface at the worst possible moment. The remedy is the same one that makes value-creation plans work: the model lives with FP&A, benefits are tracked against named accounts, and integration reporting runs on the close calendar.
Holding the CFO’s agenda together through post-acquisition integration at a $1B PE-backed chemical manufacturer and distributor produced a monthly close roughly 40% shorter, $25M+ of cash unlocked for reinvestment and debt reduction, and $8M+ in cost savings. None of that required a systems decision to be made first.
The cost of fixing governance late
Governance can be drafted in a week before close. After close it takes a quarter, because by then people have made decisions under the ambiguity and unwinding them is political rather than procedural. That asymmetry is the whole argument for doing it first, and it is the reason a Day 1 checklist that opens with decision rights tends to beat one that opens with systems.
Related: M&A & Post-Merger Integration engagements.
Further reading: Why value-creation plans die between the deal team and FP&A and The first thirty days of an interim CFO engagement. Engagement records behind this article: integration planning, pharmaceuticals producer, Americas PMO, commercial real estate services and post-acquisition integration, chemical manufacturer and distributor.
By Chad Barber, CFA, CPA — Managing Director, Finance, Strategy & Operations, CDB Advisory Services. Published by CDB Advisory Services, July 30, 2026.
Original analysis by the author, drawn from his own engagements. Clients are described by size and industry only, in keeping with confidentiality obligations. No third-party content is reproduced. © 2026 CDB Advisory Services. All rights reserved.