How a merged insurer built one combined effective license position in 83 days and cleared an inherited true up before the next renewal landed.
This software M&A case study shows how an insurer reconciled two estates in under 90 days after a merger of equals, turning two conflicting license records into one defensible position before any publisher could test it.
The composite is a regional property and casualty insurer, roughly 4,500 employees across two legal entities, that completed a merger of equals. Each side ran its own data center, its own Microsoft enterprise agreement and a shared Oracle Database estate behind the claims platform. Day one passed with both estates still running in parallel. No one held a single view of what the combined entity actually deployed against what it was entitled to use. The next Microsoft true up and the Oracle renewal were both inside a 120 day window, so the clock was already running when we were engaged.
Running both estates as one revealed the kind of exposure that only appears when you combine the data. The merged entity had moved a block of users onto a shared claims environment that drew on Oracle Database through a middleware layer. Counted properly, peak deployment exceeded the combined entitlement by a margin that, valued at list plus back maintenance, sat near 1.6 million dollars. A second gap sat in Microsoft, where server roles had been duplicated across the two data centers and double counted against the wrong agreement.
| Publisher | Gap found | Indicative exposure | Status at close |
|---|---|---|---|
| Oracle Database | Peak deployment above combined entitlement | ~ USD 1.6m | Remediated pre renewal |
| Microsoft | Duplicated server roles across data centers | ~ USD 0.4m | Reallocated, no purchase |
| Shared middleware | Indirect use of database by claims users | Quantified, monitored | Contained |
We did not wait for a clean data set. We pulled deployment evidence from both estates, normalised the two inventories into one schema, and mapped every entitlement to the contract that granted it. Where the two sides held overlapping agreements, we modelled which combination produced the lowest defensible cost. The combined effective license position was the deliverable, written so the chief information officer and the procurement lead could act on it before either vendor cycle forced a decision.
The reconciliation completed in 83 days. The Oracle gap was remediated through reallocation and a targeted purchase that came in well below the 1.6 million dollar gross exposure, because the team could show exactly which users drove the peak and retire the rest. The Microsoft double count was corrected at no cost. When the renewal conversation came, the insurer arrived with its own numbers, which changed the tone of the negotiation entirely.
The lesson for buyers is that two clean estates do not add up to one clean estate. Exposure lives in the overlap, in the shared applications and the double counted infrastructure that only become visible once the entities operate as one. A merged insurer that waits for the vendor to ask the question inherits the vendor timeline. The one that reconciles first sets its own.
See the discipline behind this in our post close license reconciliation service, learn the terms in the effective license position glossary entry, and read a related post merger Microsoft consolidation case study.
Tell us where the transaction stands. We respond within one business day with a confidential, scoped software M&A risk assessment.
Book a confidential call