The first 90 days after a deal closes decide whether the combined software estate becomes a controlled position or a latent liability. In the first 90 days, consumption changes faster than contracts can keep up: users move between systems, subscriptions auto renew on their old terms, and the publishers that audit most aggressively notice a freshly merged customer. A disciplined plan for the first 90 days turns that pressure into progress, sequencing the reconciliation so the highest risk exposure is closed while the window of greatest danger is still open.
This guide lays out what to do, week by week, in the period that matters most. It sits inside the wider post close license reconciliation effort and follows the position built in building the combined entity license position. For the foundational definition, see what post close license reconciliation is.
What to achieve in the first 90 days
The first 90 days have three goals in order: stop new exposure forming, measure the combined position, and remediate the most urgent gaps. Stopping new exposure means freezing uncontrolled access changes and putting a hold on renewals that would lock in the wrong terms. Measuring means assembling one entitlement record and one deployment measurement across both estates. Remediating means closing the under licensing that an aggressive auditor would find first. The work is sequenced so that each phase enables the next, and so the deadline pressure of an approaching renewal never forces an uninformed decision.
The first 90 days, week by week
Translating the goals into a schedule keeps the work honest. The table below sets out the typical sequence, the milestone for each window, and the risk it retires. The dates are a guide, not a rule, and they compress or extend with the size of the estate, but the order rarely changes: control first, measure second, remediate third.
Key takeaways
- The first 90 days decide whether the combined estate becomes a controlled position or a latent liability.
- The order is fixed: stop new exposure forming, measure the combined position, then remediate urgent gaps.
- Freeze uncontrolled access changes and risky renewals first, before consumption locks in the wrong terms.
- Close the under licensing an aggressive auditor would find first, while the window of danger is still open.
- Hand a consolidation and savings plan to business as usual at day 90 so the gains are not lost.
The traps that waste the first 90 days
Two traps recur. The first is paralysis: the team waits for perfect data before acting, and an auto renewal or an audit notice arrives before anything is decided. The answer is to act on the highest confidence findings early and refine later. The second is misplaced urgency: the team rushes to consolidate tools for quick savings before it has measured the position, and creates new breaches by moving users into systems they are not licensed for, exactly the failure described in how entity consolidation triggers license breaches. The disciplined path measures before it moves, and the first 90 days reward that discipline.
Recommendations for buyers
- Put an access and renewal freeze in place in the first two weeks, before consumption changes lock in.
- Assemble one combined inventory and entitlement record before drawing any conclusions about exposure.
- Act on the highest confidence findings early rather than waiting for a perfect data set.
- Remediate the under licensing an aggressive auditor would find first, not the easiest gaps to close.
- Measure the position before consolidating tools, so quick savings do not create new breaches.
Carrying the diligence findings into the first 90 days
The first 90 days are far easier when they start from the diligence findings rather than from a blank page. Everything the buyer side review priced before signing, the indirect access exposure, the virtualisation risk, the change of control clauses that needed consent, should arrive at close as a live list with owners attached. The team that begins the first 90 days with that list already in hand spends its early weeks acting, not rediscovering. The team that begins without it spends the first month rebuilding knowledge the deal already paid to acquire, and loses the window where exposure is highest and remediation is cheapest.
This is why the handover from diligence to integration deserves as much attention as the work itself. A priced exposure that is filed in a report and never assigned to an owner is an exposure that will be met unprepared when its renewal or audit clock arrives. The discipline that protects the first 90 days is the same one that protects diligence value generally: every finding carries an owner and a date, and the same evidence base flows from before signing into after close without a break. The first 90 days are the proving ground for whether that continuity exists.
The work also sets the tone for the integration as a whole. A combined entity that controls its software position in the first quarter establishes the habits, the data, and the ownership that make every later renewal and consolidation easier. One that lets the first 90 days slip into firefighting tends to keep firefighting, because the position is never measured and each new integration step adds exposure on top of an unknown base. The first 90 days are not just about closing the immediate risk. They set whether the combined entity manages its software deliberately or reactively for years afterward.
Why an independent advisor runs the first 90 days
The first 90 days fail when the team running them is also being pulled into a hundred other integration tasks and has no specialist owner for the software position. An independent, buyer side advisor with no affiliation to any publisher or reseller takes that ownership, sequences the work so control comes before consolidation, and closes the most dangerous exposure while the buyer attention is elsewhere. That focused ownership in the first 90 days is what keeps the value diligence protected from leaking back out after close.