Home/Software in Deal Valuation/Preparing for Sale
Software in Deal Valuation

How sellers should prepare software for sale

A target that has reconciled its licensing position is a cleaner asset. One that has not is a discount waiting to be found. Here is what good seller preparation looks like, read from the buyer side of the table.

How sellers should prepare software for sale is a question buyers care about too, because a target that has prepared its licensing position well is a cleaner, more valuable asset, and one that has not is a discount waiting to be found. This page is written from the buyer side, but it sets out plainly what good seller preparation looks like, so a buyer can tell the difference between a target that has done the work and one that is hoping the software dimension goes unexamined. A prepared estate protects value on both sides of the table.

How sellers should prepare software for sale, the buyer view

Inherited software licensing exposure is usually latent and unquantified, and it surfaces as a publisher audit after a deal completes. A seller who waits for the buyer to find that exposure cedes control of both the timing and the price impact. A seller who instead reconciles deployment against entitlement before going to market knows where the gaps are, can fix the cheap ones, and can frame the rest with evidence rather than leave them to be discovered. From the buyer perspective, encountering a target that has done this work is a strong signal of a well run estate, while encountering one that has not is an invitation to probe harder and price the uncertainty.

The core of good preparation is a clean entitlement position. That means knowing what the target is licensed for, what it actually has deployed, and where the two diverge. It means resolving the easy non compliance before the data room opens, and documenting the rest so a buyer cannot inflate it. It also means understanding the change of control and anti assignment clauses in the major agreements, because those clauses decide what happens to the licences on a sale, and a buyer will certainly examine them.

The seller software readiness sequenceTimeline of five phases a seller works through to prepare software for sale, from reconciling entitlement to documenting the disclosure position.The seller software readiness sequence1Reconcileentitlement2Remediatecheap gaps3Reviewclauses4Documentthe position5Disclosethe data room
A prepared seller reconciles, remediates the cheap gaps, reviews the clauses, documents the position, and frames the disclosure before the buyer arrives.

What good preparation looks like to a buyer

A buyer evaluating a target reads the state of its software preparation as a proxy for how well the whole estate is managed. A target that can produce a current entitlement position, a clear deployment baseline, and a documented view of any gaps is presenting a defensible asset. A target that offers only invoices and a vague assurance of compliance is presenting risk. The difference shows up directly in diligence: the prepared target compresses the buyer questions and limits the price impact, while the unprepared target invites the buyer to assume the worst and discount accordingly.

The preparation a seller does maps closely onto what the buyer would otherwise do in reverse. The seller version of this work is examined in sell side software due diligence, and the way the prepared position is presented is covered in software risk disclosure in the data room. For the buyer, the value of understanding seller preparation is simple: it tells you where to look and how hard, and it tells you whether the asset has been managed or merely operated.

Seller readiness actions and the buyer signal
Seller actionWhat it producesBuyer reads it as
Reconcile entitlementCurrent licence positionA managed estate
Remediate cheap gapsReduced exposureGood faith and control
Review change of control clausesTransferability mapDeal structure clarity
Document residual riskEvidenced positionLimited room to discount
Frame the disclosureClear data room narrativeLower uncertainty premium

Why preparation protects value for both sides

The reason seller preparation matters to a buyer is that it shrinks the zone of uncertainty where value leaks away. When the software position is documented and evidenced, the negotiation is about a known number, which can be priced, indemnified, or escrowed cleanly. When it is opaque, the buyer must either accept unquantified risk or apply a conservative discount, and both outcomes are worse for the seller and harder for the buyer to underwrite with confidence. A prepared estate turns a contested unknown into a managed known, as covered in negotiating software risk allocation in the SPA.

The cost of poor preparation is visible in public 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. Exposures of that magnitude do not appear overnight; they accumulate in estates that were operated without a clean entitlement view. A seller who prepares properly reduces the chance of leaving such a liability for a buyer to find, and a buyer who understands good preparation can tell quickly whether the target has done so. This page is commercial advisory on preparation, not legal advice; the parties should engage their own counsel on the agreements.

The publishers a prepared seller addresses first

A seller with limited time before going to market should concentrate its preparation on the publishers most likely to generate a post deal audit, because those are the agreements a buyer will probe hardest. The major post deal audit risks come from Oracle, SAP, Microsoft, IBM, and increasingly Broadcom following its acquisition of VMware, Salesforce, and ServiceNow, as of June 2026. A seller that can present a clean, evidenced position on those estates removes the buyer biggest concern and protects the most value, while a seller that leaves them opaque hands the buyer a reason to discount aggressively regardless of how tidy the rest of the estate is.

For a buyer, the same list is a checklist. If the seller preparation is thorough on the minor tools but thin on the major publishers, that pattern itself is informative: it suggests the seller has tidied the easy items and avoided the hard ones. A buyer should weight its review toward the high risk publishers, validate the seller deployment data against independent evidence, and quantify any gap on those estates before it informs the price. Good preparation on the right publishers protects the seller; the absence of it tells the buyer exactly where to dig.

Key takeaways

  • How sellers should prepare software for sale matters to buyers because a prepared estate is a cleaner, more valuable asset.
  • Good preparation centres on a clean entitlement position, with cheap gaps fixed and residual risk documented.
  • A buyer reads the state of software preparation as a proxy for how well the whole estate is managed.
  • A prepared position turns a contested unknown into a managed known that can be priced, indemnified, or escrowed.
  • Preparation should concentrate first on the publishers most likely to drive a post deal audit.

Recommendations for buyers

  1. Read the preparation as a signal. A documented entitlement position points to a managed estate; invoices alone point to risk.
  2. Probe the unprepared target harder. Where the seller cannot evidence its position, examine deployment against entitlement yourself.
  3. Weight your review to the high risk publishers. Concentrate on the estates most likely to drive a post deal audit.
  4. Check the change of control clauses. Confirm how the major agreements treat a sale before relying on transferability.
  5. Price the uncertainty that remains. Where the position is opaque, allocate the residual risk through the agreement rather than absorbing it.

How sellers should prepare software for sale sits within software in deal valuation, alongside sell side diligence and data room disclosure. The buyer side analysis that tests a seller preparation comes from software spend diligence. Engage your own counsel for legal interpretation of any agreement.

Frequently asked questions

How should a seller prepare software for sale?
By reconciling deployment against entitlement, remediating the cheap gaps, reviewing change of control and anti assignment clauses, documenting any residual risk, and framing the position clearly in the data room before buyers arrive.
Why does seller preparation matter to a buyer?
Because a prepared estate is a cleaner, more valuable asset with less hidden exposure. The state of preparation signals how well the whole estate is managed and tells the buyer where to look and how hard.
What does poor preparation look like?
Only invoices and a vague assurance of compliance, with no current entitlement position or deployment baseline. It invites the buyer to assume the worst and discount the price for the uncertainty.
Which publishers should a seller prepare first?
Those most likely to drive a post deal audit, including Oracle, SAP, Microsoft, IBM, and increasingly Broadcom following its VMware acquisition, Salesforce, and ServiceNow, as of June 2026.
How do change of control clauses fit in?
They decide what happens to the licences on a sale, and a buyer will examine them closely. A prepared seller maps how the major agreements treat the transaction structure in advance.
Does preparation protect the seller price?
Yes. A documented, evidenced position limits the buyer ability to discount for uncertainty and turns a contested unknown into a managed known that can be priced or allocated cleanly in the agreement.

Request a confidential software M&A risk assessment

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