How to scope software due diligence on a target is the decision that determines whether the work finds the exposure or runs out of time before it does. Scope is not about doing everything. It is about matching the depth and the coverage to the deal profile, the timeline and the shape of the estate, so the largest risks are sized first and nothing material is left to chance. Good scoping is what makes the software due diligence method work inside a real deal calendar.
The wrong instinct is to spread effort evenly across every publisher and every contract. The right instinct is to concentrate on where the money is, then widen coverage only as far as the timeline allows. This guide sets out how to make that call.
How to scope software due diligence on a target
Start by reading the deal profile. A small SaaS heavy target needs a focused review of active versus paid seats and auto renewals. A large on premises estate needs deep measurement of Oracle, SAP, Microsoft and IBM deployment against entitlement. A carve out or cross border target needs a full multi entity position because shared agreements and territory rules multiply the exposure. The scope follows the estate, not a fixed template.
Why scope is the highest leverage decision
Scope decides the return on the diligence before a single contract is read. Get it right and the team spends its hours on the publishers and metrics that can actually move the price, producing a number the deal can use. Get it wrong and the same hours are spent confirming low risk areas while a seven figure exposure sits unmeasured behind a publisher that was descoped to save time. No amount of careful fieldwork rescues a bad scope, because the work never looks where the exposure is. That is why scoping deserves explicit attention at the start rather than being treated as an administrative preamble. It is the decision that most determines whether the diligence earns its fee.
Scope around the timeline you actually have
Diligence runs against a deal clock, so scope has to be honest about time. In a time boxed process the priority is to size the publishers most likely to produce a large settlement, then extend coverage if the calendar permits. This is the logic of prioritising publishers in a time boxed diligence: a defensible number on the top three publishers beats a thin pass across all of them.
Set a materiality threshold
Scope also means deciding what is worth measuring. Set a materiality threshold tied to the deal size, below which a finding is noted but not deeply quantified. This keeps effort on the exposures that can move the price or the terms. A publisher representing a few thousand dollars of possible gap does not warrant the same measurement as one carrying a seven figure risk.
Key takeaways
- Scope matches depth and coverage to the deal profile, the timeline and the shape of the estate.
- Concentrate effort where the money is, then widen coverage only as far as the timeline allows.
- A small SaaS target, a large on premises estate and a carve out each need a different scope.
- In a time boxed process, a defensible number on the top publishers beats a thin pass across all of them.
- A materiality threshold keeps effort on the exposures that can move price or terms.
Decide what data and access you need
Scope determines the data request. A focused SaaS review needs administration exports and contract terms. A deep on premises position needs server, processor and directory data and, ideally, access to measurement tools such as sub capacity reporting. Define the data you need before fieldwork, because a scope that depends on data the target cannot produce will collapse. The detail is in how to request software data from a target.
Agree who owns the scope
Finally, scope is a shared decision between the advisor and the deal team, and it should be written down. The deal team owns the materiality and the timeline. The advisor owns the judgement about where exposure is most likely to sit. The question of who should own software due diligence on the deal is part of scoping, because an unclear owner produces an unclear scope.
Scoping for a carve out or competitive auction
Two deal types stretch scoping in opposite directions. A carve out widens it, because the target shares agreements with a parent and the scope has to cover how the estate splits, which shared licenses transfer, and where separation triggers consent or repricing. A competitive auction compresses it, because the timeline is short and access is limited, so the scope has to deliver a defensible top publisher position fast and flag where confirmatory work is still needed. The approach to the latter is set out in software due diligence in a competitive auction process. In both cases the principle holds: scope to the risk and the calendar, not to an ideal.
When to widen or stop the scope
Scope is not fixed once set. Early findings should reshape it. If the first pass on a priority publisher surfaces a large gap, widen the scope to measure it fully and to check whether the same metric breaches sit elsewhere in the estate. If a publisher comes back clean and low risk, stop there rather than polishing a number that cannot move the deal. The skill in scoping is knowing when a finding warrants more depth and when it is already good enough to act on, so effort follows exposure rather than habit.
Recommendations for buyers
- Read the deal profile first and let the estate shape the scope, not a fixed template.
- In a time boxed process, size the top publishers to a defensible number before widening coverage.
- Set a materiality threshold tied to deal size so effort stays on exposures that can move price or terms.
- Define the data and access the scope depends on before fieldwork, and confirm the target can produce it.
Once scope is set, the work runs against a timeline, covered in software due diligence timeline in a deal, and is delivered through our software due diligence service.