Helios Mutual and Cedar Assurance: Governing Post-Merger Synergies
Helios Mutual and Cedar Assurance completed a merger eight months ago. The combined insurer runs two policy administration systems, employs 1,400 people, and committed to a $40 million annual synergy target by the end of year three to justify the deal premium. The integration management office tracks synergies in spreadsheets maintained by six workstream leads, and the first quarterly board report claims $12 million annualized already. The CFO suspects double counting: two workstreams both claim the same procurement savings, and one claims revenue synergy from a product that has not launched. Regulators require stable policy servicing throughout integration, and the system-of-record decision between the two policy platforms is politically contested because each has an executive sponsor. A separate stranded-cost estimate has not been updated since the deal closed. The board wants confidence in the synergy number before it approves the next integration budget.
1. Design the governance for synergy benefits realization. What must be true for the $40 million target to be credible, and who owns each category?
Read the worked answer
Credibility requires four things the current process lacks: a baseline, a taxonomy, named owners, and a link to the financial ledger.
Taxonomy and owners:
- Cost synergies - CFO, with workstream leads accountable for specific lines: headcount, procurement, facilities, IT contracts. Each line must be traceable to a general ledger account or contract.
- Capital synergies - CFO and CIO jointly, especially avoided platform and infrastructure spend.
- Revenue synergies - Chief Commercial Officer, with launch dates and conversion assumptions. These are the least reliable and must be discounted until evidence exists.
- Dis-synergies and stranded costs - CFO, updated quarterly; ignoring them overstates net benefit.
What must be true: baselines reflect pre-merger run rates, not post-deal estimates; every synergy has one owner and one calculation method; timing is realistic; and the $40 million is net of integration cost and dis-synergies. The claim of $12 million annualized in eight months is implausible against typical integration curves unless most of it is procurement already contracted.
Governance: an integration steering committee chaired by the CEO, with the CFO as benefits authority, meeting monthly. The IMO maintains one register and has authority to reject duplicate claims. The board sees net, risk-adjusted, in-year and run-rate figures separately.
2. How should the integration team avoid double counting and stranded costs when reporting synergies to the board and regulators?
Read the worked answer
Prevent double counting structurally rather than by reconciliation after the fact.
- One register, one line, one owner. Every synergy has a unique identifier tied to a cost centre, contract, or headcount position. If two workstreams claim the same procurement saving, the register allows only the contract owner to claim it; the other records a dependency, not a benefit.
- Tie claims to evidence. A synergy is 'committed' when a contract is amended, a position eliminated, or a system decommissioned; 'approved' when only a decision exists; 'pipeline' otherwise. Board reporting should show the three tiers, not one blended number.
- Net presentation. Report gross savings, integration cost, and stranded cost together. The un-updated stranded-cost estimate is a material gap: duplicate facilities, licence overlap, and retention payments can consume a large share of apparent savings.
- Revenue synergies separately and discounted. The unlaunched product should carry zero in the committed tier.
- External validation. Have internal audit or an independent reviewer test a sample before the board relies on the number, and keep an audit trail suitable for regulatory scrutiny.
Reporting format: one page, net, tiered, with prior-quarter restatements explained. If the CFO is already suspicious, the first report should restate the $12 million downward. Credibility with the board depends on that honesty.
3. The policy administration system-of-record decision is politically contested. What decision criteria and decision rights should apply?
Read the worked answer
Separate the decision from the sponsor politics by fixing criteria and decision rights before evaluating options.
Criteria:
- Regulatory and policy-servicing continuity, including the regulator's tolerance for migration risk.
- Cost to serve per policy and total cost of ownership over five years, including decommissioning the other platform.
- Migration risk and duration, with data quality assessed on real policy samples.
- Customer and broker impact, including any product changes required.
- Ability to deliver the revenue synergies in the business case.
- Skills and vendor support in the combined organization.
Decision rights: the integration steering committee chaired by the CEO decides, with the CIO and CTO providing technical assessment and the Chief Risk Officer providing an independent risk opinion. The two executive sponsors present their cases but do not vote. The board approves if the decision exceeds the integration budget threshold.
Process: publish weighted criteria and minimum thresholds before scoring; require both sponsors to submit the same evidence pack; have an independent reviewer test the cost and migration assumptions. Record the decision and the rejected option's rationale.
Why this matters: a politically contested platform decision made by sponsorship strength usually produces a hybrid that runs both systems far longer than planned, adding stranded cost and regulatory exposure. The governance answer is not to pick a winner early, but to make the basis of the choice transparent and testable, then hold the organization to it.