Post Close Software Inventory: Where to Start

A post close software inventory is the first piece of work that turns a closed deal into a defensible combined estate. The day after close, the acquirer owns every license, subscription, and unpaid true up the target carried, but it almost never owns a complete picture of them. A disciplined post close software inventory builds that picture deliberately, because inherited licensing exposure is usually latent and unquantified in standard due diligence and tends to surface as a publisher audit once the new owner is known. The buyer that starts the inventory early controls the timeline. The buyer that waits lets a publisher set it.

This guide explains where to start, what to capture, and how to sequence the work so nothing is missed. It is the opening move in post close license reconciliation and the input every later workstream relies on. Without a complete inventory, the team cannot build a defensible position, cannot find duplicated spend, and cannot tell whether consolidation will trigger a breach.

Post close software inventory: what to capture first

Start where the exposure concentrates rather than where the data is easiest to pull. The publishers that drive the largest post deal audit risk are Oracle, SAP, Microsoft, IBM, and increasingly Broadcom for VMware, alongside Salesforce and ServiceNow. Inventory those estates first, because a gap there costs more than a gap in a minor tool. For each, capture the contract, the entitlement metric, the deployed quantity, and the renewal date. The deployment count without the entitlement is half a picture, and the entitlement without the deployment is the other half. Only the two together tell you whether the combined entity is compliant, under licensed, or carrying shelfware it can recover.

Capture both the discovered estate and the contracted estate, then compare them. Discovery tools show what is installed and used. Contracts show what was bought and on what terms. The gap between them is the inventory's real output, because that gap is where exposure and savings both live. A name that appears in deployment but not in any contract is an unlicensed deployment. A contract with no matching deployment is either shelfware to recover or a renewal to question.

Where the inventory data comes from

No single source holds the full picture, so the inventory pulls from several and reconciles them. Discovery and asset management tools give the deployed view. Procurement and contract repositories give the entitlement view. Finance systems show what is actually being paid, which often reveals subscriptions no one in IT knew existed. Identity and access systems show who is actually logging in, which separates active users from dormant accounts that inflate a license count. Each source is partial and each is wrong in its own way, so the discipline is to triangulate rather than trust any one of them.

The most common failure is treating the target's own license position statement as fact. A target preparing for sale has every incentive to present a clean position, and a target under time pressure rarely has the data to support one. The acquirer rebuilds the position from primary sources rather than inheriting the seller's summary. This is the same discipline that underpins building the combined entity license position, which is the structured output the inventory feeds.

Sequencing the inventory so nothing is missed

Sequence the work by exposure and by deadline, not alphabetically. Any publisher with a renewal or audit clause that bites in the first year goes to the front, because the inventory has no value if it arrives after the leverage is gone. Map each contract's renewal and notice dates as the inventory is built, so the team knows which decisions have a clock running. This sequencing is what connects the inventory to the wider post close reconciliation project plan, which assigns owners and dates to each workstream that flows from it.

Set a clear cut off for what counts as in scope. A combined estate of any size contains hundreds of minor tools, and chasing every one delays the inventory of the publishers that matter. The disciplined approach inventories the material estate to full depth and the long tail to a lighter standard, then revisits the tail once the priorities are secured. Completeness on the publishers that drive audit risk beats partial coverage spread thin across everything.

Turning the inventory into a defensible position

The inventory is a means, not an end. Its purpose is to support a position the combined entity can defend if a publisher comes asking, and to reveal the savings consolidation makes available. Once the deployed and contracted views are reconciled, the team can quantify under licensing before a publisher finds it, identify overlapping agreements to rationalise, and plan the consolidation in a sequence that avoids creating a breach. The first ninety days set the tone, which is why the inventory should be substantially complete before then, as covered in the first 90 days reconciling software after close.

A complete inventory also changes the negotiating posture. A buyer who knows exactly what it owns, what it uses, and what it can stop paying for sits across the table from a publisher with facts rather than fear. That is the difference between settling an audit on the publisher's number and settling on the buyer's. The inventory is what makes the difference real rather than rhetorical.

Why an independent advisor runs the inventory

A post close software inventory done by a party with no stake in any publisher relationship is the only version a buyer can fully trust. An independent, buyer side advisor reconciles the deployed and contracted estates without an incentive to keep any contract running, surfaces exposure the seller had reason to leave unstated, and hands the acquirer a position built to be defended rather than sold. That independence is what makes the inventory a foundation rather than a formality.