Home/Services/Diligence Checklist
For buyers and deal teams

A software due diligence checklist service

A software due diligence checklist service that works each item against the target's real data and delivers a defensible exposure figure, not a set of ticked boxes.

Our software due diligence checklist service turns a generic checklist into a quantified result. A checklist on its own lists what to ask for. The service works through each item against the target's real data, reconciles deployment against entitlement, and delivers a defensible exposure figure rather than a set of ticked boxes. The difference is the difference between knowing what to look for and knowing what the answer costs.

The software due diligence checklist as a sequenced workflowTimeline showing the stages of a software due diligence checklist from contract gathering through quantified exposure.Gathercontracts andinvoicesReconcileusage versusentitlementTestmetrics andclausesQuantifyexposure bypublisherActprice andplan
The software due diligence checklist run as a sequenced workflow, from contract gathering through quantified exposure.

What the software due diligence checklist service covers

The software due diligence checklist service starts where most checklists stop. We locate every material agreement so no publisher surprises the buyer after close. We capture deployment data, because installs and consumption against entitlement are the only figure a publisher audits on. We test the metrics that breach quietly, such as processor counts, named users, and indirect access. We read the change of control and anti assignment terms that decide whether a deal structure protects the target's pricing. And we map the renewal calendar so year one cost rises are priced in rather than discovered.

Inherited software licensing exposure is usually latent and unquantified in standard due diligence, and it lands as a publisher audit after close. As of June 2026, public reporting shows SAP pursued AB InBev for a figure in the region of 600 million dollars, and the Diageo Great Britain Ltd v SAP UK Ltd judgment, [2017] EWHC 189 (TCC), confirmed indirect access can require licensing. A checklist that ends at gathering documents leaves that exposure unmeasured.

The software due diligence checklist and what each item protects
Checklist itemWhat we verifyWhat it protects
Contract inventoryAll material agreements locatedNo surprise publisher after close
Deployment dataInstalls and consumption capturedThe figure a publisher audits on
Metric testProcessors, users, indirect accessQuiet breaches surfaced early
Change of controlConsent and reprice triggers readDeal structure chosen with eyes open
Renewal calendarReprice dates mappedYear one cost rises priced in

What a thorough checklist actually asks

A software due diligence checklist worth running goes well beyond a request for contracts. It asks the target to evidence every material agreement, including the order forms and amendments that change the terms, because a missing amendment can flip a position from compliant to exposed. It asks for deployment evidence, not a self assessment, because the only figure that matters is what the systems actually run against what the licences permit. It asks for the renewal schedule, the audit history, and any prior true ups, since a publisher that has audited once will audit again. And it asks the change of control question against the proposed deal structure, because a stock purchase, an asset purchase, and a merger each trigger different clauses.

Running those items as a workflow is what produces a result instead of a record. We sequence the checklist so each answer feeds the next, gather the deployment data, test it against the entitlement, and convert the gap into a quantified exposure by publisher. The deal team receives a figure with a defensible basis, the renewal events that will move it, and a prioritised list of what to address in the first hundred days after close. A checklist that ends at a stack of documents leaves all of that work undone and the buyer exposed to whatever the documents did not reveal.

Why a service beats a checklist alone

A checklist is a useful starting point, but a list of questions does not protect a buyer. The exposure that matters is the gap between the answers, and quantifying that gap takes the deployment data, the metric tests, and the publisher knowledge that a checklist cannot supply on its own. The service runs the checklist as a workflow and converts it into a number the deal team can act on. Because we are independent and paid only by the acquirer, that number is built to survive the investment committee. We provide commercial and licensing advisory, not legal advice, and recommend your own counsel for the interpretation of any contract term.

Key takeaways

  • A software due diligence checklist service delivers a quantified figure, not ticked boxes.
  • Locating every agreement prevents a surprise publisher after close.
  • Deployment against entitlement is the only figure a publisher audits.
  • Mapping renewals prices year one cost rises into the deal.

Recommendations for buyers

  1. Use the checklist as a workflow, not a wish list. Each item should produce data, not just a request.
  2. Insist on deployment data. Without it the checklist cannot quantify anything.
  3. Read change of control early. Deal structure decisions depend on which clauses bite.
  4. Keep the work independent. A buyer paid result is the one that holds up.

The checklist feeds our full software due diligence service and the software due diligence guide pillar. In practice: a deal repriced by 6 million dollars and hidden licensing gaps mapped.

Frequently asked questions

What is a software due diligence checklist service?
It is a service that runs a software due diligence checklist against a target's real data, reconciling deployment against entitlement and delivering a quantified exposure figure rather than a list of ticked items.
Can we just use a free checklist?
A free checklist tells you what to ask for. It does not capture deployment data, test the metrics, or quantify the exposure, which is the part that protects a buyer.
What items does the checklist cover?
Contract inventory, deployment data, metric tests for processors, users, and indirect access, change of control terms, and the renewal calendar, each verified against the target's data.
How fast can the checklist be completed?
We work to the deal timetable, with an early read on where exposure concentrates and a full quantified result in time to price it into the offer.
Are you independent of vendors?
Yes. We are paid only by the acquirer and hold no affiliation with any publisher or reseller.

Want the checklist run as a quantified result?

We turn a software due diligence checklist into a defensible exposure figure. Tell us about the deal and we respond within one business day.

Book a confidential call