Warranty and indemnity insurance and software risk

Warranty and indemnity insurance and software risk meet at a specific and often misunderstood point: the policy is built to cover the unknown breach, while inherited software licensing exposure is frequently a known risk that the insurer will exclude. Understanding where the cover starts and stops is what lets a buyer use insurance well, rather than discovering at claim time that the very exposure that worried them was carved out. This page sets out how warranty and indemnity insurance interacts with software licensing risk, and how buyers structure the deal so the policy and other protections cover the field between them.

Warranty and indemnity insurance and software risk in outline

Warranty and indemnity insurance, often written as W and I insurance, transfers the risk of a breach of the seller warranties to an insurer in exchange for a premium. In a competitive sale it allows a buyer to recover for a warranty breach without pursuing the seller directly, and it lets the seller achieve a cleaner exit. For software, the relevant warranties usually concern licensing compliance, the right to use the deployed software, and the absence of known disputes with publishers. If one of those warranties proves untrue and the buyer suffers a loss, the policy is meant to respond.

The difficulty is that most insurers will not cover a risk the buyer already knows about. If diligence has surfaced a specific over deployment or a likely indirect access exposure, the insurer will typically exclude it, because insurance is priced for uncertainty, not for a loss the parties can already see coming. This is the central tension. The exposures that buyer side diligence is best at finding are often precisely the ones the policy will not cover, which is why insurance is a complement to escrow and indemnities rather than a substitute for them.

What the policy covers and what it excludes

The practical task for the buyer is to map each software exposure to the right instrument. A clean licensing position that later proves to have a hidden defect, unknown at signing, is the classic insurable breach. A documented over deployment found during diligence is not insurable in the ordinary way, and should be priced into the consideration or covered by a specific indemnity and an escrow. Getting this mapping right before the policy is bound avoids the worst outcome, which is paying a premium for cover that excludes the one risk the buyer was most concerned about.

Underwriters also expect to see thorough diligence. A buyer who has run proper software spend diligence presents a far better risk and can negotiate narrower exclusions, because the underwriter can see the work has been done. Thin diligence invites broad exclusions, since the insurer assumes the unexamined area hides problems. The quality of the diligence therefore feeds directly into the breadth and price of the cover, which is one more reason the software dimension should be examined specifically rather than folded into a general financial review.

Using insurance alongside escrow and indemnities

The strongest structures use the instruments together. A specific indemnity backed by an escrow or holdback covers the known exposure that the policy excludes. The W and I policy then sits over the unknown breach. The underlying warranties, which define what the policy responds to, are examined in reps and warranties for software licensing, and the way the indemnity itself is structured is covered in software licensing indemnities explained. The buyer goal is a continuous field of cover with no gap between what the seller will stand behind, what the escrow secures, and what the policy will pay.

The stakes justify the structuring effort. 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. A buyer who assumed a policy would catch such a demand, only to find the exposure excluded as known, would be left absorbing the loss. Whether and how a policy responds to a software warranty breach is a legal question of contract and policy interpretation, so this page is commercial advisory on how to structure the protection, not legal advice. Engage your own counsel and your broker on the policy wording.

How the policy process runs alongside the deal

A W and I policy is not bought at the last minute. The underwriter runs its own review of the diligence, raises questions on the high risk areas, and sets the exclusions before the policy is bound, usually in parallel with the final stages of the deal. For software, this means the underwriter will want to see the licensing diligence and will probe any area that looks thin. A buyer who has the software analysis ready can answer those questions quickly and argue for narrower exclusions, while a buyer who has not examined the software estate hands the underwriter a reason to exclude licensing risk broadly. The diligence and the insurance process are therefore best run together, not in sequence.

The buyer should also understand what the policy will not do at claim time. A policy responds to a breach of warranty, so the buyer must be able to show that a warranty was untrue and that a loss followed. That places weight on the drafting of the software warranties and on the buyer ability to evidence the breach with deployment and entitlement data. Insurance does not remove the need for good diligence and well drafted warranties; it sits on top of them. Used that way, it is a valuable tool for the unknown risk, but it is never a reason to examine the software estate any less carefully.

Warranty and indemnity insurance and software risk sit within software in deal valuation, alongside indemnities, escrow, and risk allocation in the agreement. The diligence that underpins a strong policy comes from software spend diligence. Engage your own counsel and broker for interpretation of any policy or warranty.