The first hundred days set whether a software estate is consolidated on your terms or audited on the publisher's. Here is a buyer side plan that sequences the work so reconciliation stays ahead of the risk.
A software integration day one to day 100 plan is a sequenced buyer side plan that puts stabilisation and reconciliation before consolidation and renewal, so the merged software estate is consolidated on your terms rather than audited on the publisher's. The first hundred days after close decide which of those two outcomes the buyer gets. Move too fast on merging systems and the estate drifts out of compliance before anyone has measured it. Move with a defensible sequence and the same hundred days deliver synergy while the position stays audit ready throughout.
Integration changes a software estate faster than any other moment in its life, and a change of control is a recognised trigger for a publisher audit. Those two facts collide in the first hundred days: the estate is least settled at exactly the time it is most likely to be examined. A plan that rushes to provision users and merge platforms before reconciling entitlements is building exposure it cannot yet see. A plan that sequences the work keeps reconciliation ahead of the riskier moves, so each change is made against a known position.
The discipline is sequencing, not speed. There is real pressure to show synergy quickly, but the synergy that matters in software comes from consolidation, and consolidation depends on first knowing what is owned. A buyer who reconciles in the first month then consolidates from that baseline captures more value, and keeps it, than one who cuts contracts on day ten and discovers the gaps at the first audit.
Day one is about control, not change. The buyer assigns a single owner for the combined licensing position, captures the inherited contracts and entitlements from both companies, and gates the changes that affect licensing so the estate does not drift before it can be measured. This is the moment to put a light freeze on provisioning, virtualisation moves, and feature enablement that would alter the licensable footprint, as covered in avoiding compliance gaps during integration.
With the estate stable, the first month is reconciliation: an independent baseline of what each company actually owns against what it actually deploys. That baseline, the product of license reconciliation, is the reference every later decision is checked against. Without it, duplication is guessed and exit opportunities are missed. For the broader starting point, see post merger software integration and where to start.
| Phase | Window | Output for the buyer |
|---|---|---|
| Stabilise | Day 1 to 14 | Change freeze on licensing affecting moves, owner assigned |
| Reconcile | Day 15 to 44 | Independent baseline of entitlement against deployment |
| Map duplication | Day 45 to 74 | Ranked list of duplicate contracts and exit dates |
| Renegotiate | Day 75 to 99 | Combined volume positions opened with major publishers |
| Consolidate | Day 100 | First duplicates exited, defensible position held |
Once the reconciled baseline exists, the middle of the window is about finding overlap and acting on it. Mapping duplication produces a ranked list of contracts that pay twice for the same capability, each with its renewal date, so exits can be timed rather than rushed. This is the work that turns reconciliation into savings, and it is the heart of integration and consolidation advisory in the first hundred days.
Renegotiation follows, not precedes, the mapping. By day 75 the buyer knows the combined position and the combined volume, and can open conversations with major publishers from a verified, defensible footing. Renegotiating before reconciliation means negotiating from incomplete information, which publishers exploit. For the roadmap that frames this sequence beyond the first hundred days, see integration roadmap for the software estate.
The hundred day plan ends with the first duplicates exited and a defensible position held, but the estate keeps changing afterward. A change of control fires the audit clock early, and the major publishers, Oracle, SAP, Microsoft, IBM, and increasingly Broadcom following its VMware acquisition, Salesforce, and ServiceNow, may verify the estate at any point, as of June 2026. The plan therefore hands the reconciled position to a standing governance model rather than declaring the work finished.
The cost of getting the sequence wrong is well documented. In publicly reported disputes SAP pursued AB InBev for a reported 600 million dollars and Diageo for a reported 60 million over disputed and inherited licensing, as of June 2026. Those outcomes are what a defensible first hundred days is built to prevent. Carrying the position into a combined software governance model is what keeps the gains durable. Engage your own counsel for legal interpretation of any audit or change of control clause.
The day one to day 100 plan also gives the deal team something it can report against. Each phase has a defined output, from the change freeze on day one to the first duplicates exited by day one hundred, so progress is visible to the sponsor and the investment committee rather than buried in technical workstreams. That visibility matters because software synergy is often promised in the investment case and then lost in execution. A sequenced plan with named outputs is how the buyer proves the synergy underwritten at signing is actually being captured, and where it is slipping, in time to correct it.
The day one to day 100 plan is the opening phase of post merger software integration. It sets the sequence that the integration roadmap and governance model then carry forward. Engage your own counsel for legal interpretation of any contract, clause, or claim.
Tell us where the deal stands. We respond within one business day with a scoped, buyer side engagement that protects the value you underwrote.
Book a confidential call