A buyer's guide to software M&A due diligence: what belongs in the tech data room, how to structure OSS licence reviews, ARR and churn cohorts, and the security questionnaire process.
A software M&A data room holds six document sets that have no equivalent in a traditional business sale: source code escrow agreements, open-source licence audits, ARR and net revenue retention schedules, security certifications and pen-test reports, IP assignment records, and sub-processor lists under active data processing agreements. Get those six sets right before the process opens and buyers reach conviction in weeks, not months.
Papermark: best for software M&A teams. NDA-gated access, granular permissions for code repos and IP folders, watermarked financials, audit log export and SOC 2 Type II and ISO 27001 certifications. From $99/month with unlimited data rooms. See the Papermark profile for full feature detail.
For the general M&A data room playbook, see best virtual data room for mergers and acquisitions. For the broader due diligence framework, see best virtual data room for due diligence.
Meridian Analytics is a Denver-based B2B SaaS company that sells workforce analytics to mid-market employers. Annual recurring revenue is $14.2 million, net revenue retention is 108 percent, and gross margin is 74 percent. After seven years of bootstrapped growth, the founders have engaged a boutique M&A adviser to run a sell-side process targeting strategic acquirers and growth equity firms.
The adviser sets up a data room on day one and structures it into nine top-level folders. Folders 1 through 5 cover the standard M&A workstreams: corporate documents, financials, tax, legal, and HR. Folders 6 through 9 are software-specific: 6.0 Technology and IP, 7.0 Security and Compliance, 8.0 Customer and Revenue Data, and 9.0 Data and Privacy.
The first buyers to log in are two strategic acquirers. Within 48 hours, both have submitted questions on the same items: the third-party components in the product, the ownership chain for the core algorithm (developed partly by a contractor in 2021), and the SOC 2 report currency. These are not random questions. They are the three items that most commonly generate price adjustments in software acquisitions, and they hit on day two because sophisticated buyers have learned to look for them first.
By week three, Meridian's team has uploaded the escrow agreement showing the source code is held in a Major ESCROW provider, the OSS dependency scan from a certified tool, the contractor IP assignment signed in 2021, and the refreshed SOC 2 Type II report covering the period ending August 2026. Those four documents resolve the opening questions, the process accelerates, and both buyers submit indicative offers that reflect the premium valuation the adviser was targeting.
Code escrow is a three-party arrangement between the software vendor (the seller), a buyer or licensee, and a neutral escrow agent that holds a copy of the source code. The escrow agreement specifies release conditions: typically, insolvency of the vendor, failure to maintain the software, or a material breach of the license. In an M&A context, a buyer acquiring a business built on a licensed platform (not acquiring the IP outright) will request to see the escrow agreement to confirm the codebase is protected if the licensor is later acquired or winds down.
For sellers, the relevant document is proof that the escrow is current. The escrow agent issues annual verification certificates confirming that the deposited code is current, compilable, and matches the production version. If that certificate is out of date, buyers will discount the IP value or require a fresh deposit and verification before closing.
Standard ESCROW agreements in US software transactions are governed by the Technology Escrow Professionals Association model terms, though most escrow agents (Iron Mountain, NCC Group, Escrow London) use their own forms. The key terms to disclose in the data room are the trigger events, the verification schedule, the technology specification (what constitutes the deposit), and any existing beneficiaries who already have release rights.
Open-source software is the foundation of almost every modern application. The issue in due diligence is not open-source itself, but the licence conditions attached to open-source components embedded in the product. Three families of licence create disclosure obligations:
GPL and LGPL (copyleft). The GNU General Public License requires that any software distributed with a GPL component must also be distributed under the GPL, with source code available. For a commercial software product, an undisclosed GPL dependency can create a "licence contamination" risk: a buyer's legal team may argue the entire codebase is subject to open-source disclosure obligations. LGPL is weaker (it applies to the library itself, not necessarily the calling code) but still requires analysis.
AGPL (Affero GPL). The AGPL extends the GPL copyleft trigger to software provided over a network. A product that uses an AGPL-licensed library in its backend and delivers that functionality via API or SaaS must disclose the source code of the modified AGPL component. This is frequently overlooked because the trigger is a network interaction, not traditional distribution.
MIT, Apache 2.0, and BSD. Permissive licences. They require attribution but impose no copyleft restrictions. These are generally unproblematic, but the data room should still include a full dependency manifest to demonstrate that no copyleft components are present.
A thorough OSS licence scan uses an automated FOSS (Free and Open-Source Software) audit tool, such as FOSSA, Black Duck, or Snyk, to generate a complete bill of materials covering every direct and transitive dependency. The output is a report listing each component, its version, its licence, and any flagged risk. That report, together with counsel's analysis of flagged items and any remediation steps taken (component replacement, licence purchase, or carve-out), is the core of the Technology and IP folder.
Revenue quality is the central valuation question in a SaaS acquisition, and the data room must provide the metrics that let a buyer independently reconstruct the ARR and verify the net revenue retention figure in the management presentation.
ARR bridge. An ARR bridge is a table that reconciles beginning-of-period ARR to end-of-period ARR through five movements: new business, expansion (upsell and cross-sell), contraction (downgrades), churn (non-renewals and cancellations), and foreign-exchange adjustments for multi-currency businesses. A buyer will build their own version from the underlying contract data, so the data room should include the contract register with start and end dates, annual contract value, renewal terms, and the history of expansions and contractions at the customer level.
Net Revenue Retention (NRR). NRR measures revenue from the existing customer base at the start of a period relative to revenue from that same cohort at the end, capturing expansion, contraction, and churn but excluding new customers. An NRR above 100 percent means the existing base grows on its own without any new sales. For enterprise SaaS, NRR above 110 percent is considered strong. The data room should include the NRR calculation methodology, the input data, and a cohort-level breakdown showing whether retention varies by customer segment, contract size, or acquisition channel.
Churn cohort analysis. Logo churn (the number of customers who cancel) and revenue churn (the ARR lost to cancellations) can tell different stories. A product that loses many small accounts but retains large ones may have strong revenue retention but weak logo retention. Buyers will want to see churn broken out by cohort (year of acquisition), by contract size, and by customer segment, as well as a qualitative analysis of the top-10 churn events over the trailing 24 months. What caused each loss, and was it recoverable or structural?
Seat count versus contracted revenue. Many SaaS products price on a per-seat basis, and the distinction between contracted seats and active seats matters for valuation. If contracted seat count exceeds active seat count by more than 15 to 20 percent, a buyer will model a contraction risk at renewal as customers right-size their licenses. The data room should include both contracted seats by customer and product usage data showing active seats over the trailing 12 months.
A software acquisition is also an information security acquisition. Buyers will want to see the full security posture of the target, including third-party certifications, penetration test results, and the vulnerability disclosure and incident history.
SOC 2 Type II. The System and Organization Controls 2 Type II report is the standard security audit for US software companies. It covers five trust service criteria: security, availability, processing integrity, confidentiality, and privacy. A Type II report covers a 12-month audit period, so its currency matters: a report covering a period that ended more than 12 to 15 months ago is effectively stale. The data room should include the current report and the management response to any exceptions noted by the auditor.
ISO 27001. ISO 27001 certification is the international standard for information security management. It is increasingly required by enterprise customers in regulated industries and by European buyers. The data room should include the current certification letter, the scope statement, and the most recent surveillance audit findings.
Penetration test reports. Annual external penetration tests (and, for products with significant attack surface, quarterly internal scans) are expected by enterprise buyers. The data room should include the full penetration test reports for the past two years, the finding severity classifications, and documented evidence that critical and high findings were remediated within the agreed SLA. Open findings should be listed with their current status and planned remediation date.
Vulnerability disclosure policy and incident history. A published vulnerability disclosure policy (VDP) demonstrates security maturity. The data room should include the policy itself and a log of reported vulnerabilities over the trailing 24 months: what was reported, how it was classified, how quickly it was fixed, and whether any were exploited. Any material security incidents (breaches, unauthorized access, data loss) must be disclosed, together with the root-cause analysis and the notification records for affected customers or regulators.
IP chain-of-title is one of the highest-frequency issues in software M&A. The question is simple: does the company actually own the code? The answer depends on three categories of contributor.
Current and former employees. Under US law, work created by an employee within the scope of employment is a work made for hire, owned by the employer. However, this requires that an IP assignment and proprietary information agreement (PIIA) was signed at the start of employment. Many early-stage companies miss this step for the first few hires. The data room should include signed PIIAs for every employee who contributed to the core product, and if any are missing, an explanation of what remediation was taken (which may include retroactive assignments).
Contractors and freelancers. Work created by an independent contractor is NOT a work made for hire under US law unless the parties sign a written agreement that specifies it as such. Any contractor who wrote code for the product, designed a component, or contributed to the architecture should have a signed agreement that explicitly assigns all intellectual property to the company. Missing contractor assignments are a common red flag in SaaS acquisitions, particularly for offshore contractors, and they are frequently used by buyers to negotiate price reductions or escrow holdbacks.
Third-party tools and APIs. Software products often integrate third-party APIs and use licensed tools in the development process. The data room should include a register of these integrations with the governing terms, confirming that the product's use complies with each third party's license terms (some API licenses, for example, prohibit use in a product that is subsequently sold without a license change).
If the target processes personal data on behalf of its customers, it is a data processor under GDPR and a service provider under state laws such as CCPA. That status creates documentation obligations that belong in the data room.
Data Processing Agreements (DPAs). Customer contracts should include signed DPAs covering the standard clauses required by GDPR Article 28: subject matter, duration, nature and purpose of processing, type of personal data and categories of data subject, the customer's obligations and rights, and the sub-processor approval mechanism. The data room should include template DPAs and confirmation that signed DPAs are in place with all EU-established customers.
Sub-processor list. The DPA commits the company to maintaining a current list of sub-processors (the third parties to whom it transfers customer personal data for processing) and notifying customers of changes. A well-maintained sub-processor list that is publicly available on the company's website is a positive signal. An outdated or missing list is a gap that buyers will address in reps and warranties.
International data transfers. If the company transfers EU personal data to the US or other non-adequate countries, the legal basis for those transfers must be documented. Standard contractual clauses (SCCs, updated to the 2021 versions) are the standard mechanism. The data room should include signed SCC addenda with sub-processors and evidence of transfer impact assessments where required.
Enterprise SaaS contracts typically include service level agreements that commit to uptime thresholds (commonly 99.9 percent monthly, with credits for failures) and support response times. These commitments become contractual liabilities after closing, so buyers will review them carefully.
The data room should include the standard SLA terms, a trailing-24-month uptime log from the company's status page or monitoring platform, and a record of SLA credits paid to customers. A pattern of repeated credits to the same customers may indicate persistent reliability issues in a component that the acquirer will need to address. It may also signal a customer relationship risk: customers who have received material credits may be less loyal than the ARR bridge suggests.
1. Treating the OSS licence scan as a checklist item. A scan report that shows "no critical findings" can still contain LGPL dependencies in a context that creates copyleft risk. The report must be reviewed by counsel who understands software licensing, not just checked for the absence of red flags.
2. Accepting NRR without the underlying cohort data. A single NRR figure can mask severe churn in older cohorts that is offset by expansion in a large recent cohort. Always request the cohort-level breakdown before forming a view on retention quality.
3. Missing contractor IP assignments. This is the single most common IP gap and the one most likely to result in a post-closing indemnification claim or escrow dispute. Run the full contributor list against the signed agreement archive before LOI, not after.
4. Not verifying SOC 2 currency. A SOC 2 report covering a period that ended 18 months ago tells buyers very little about the current security posture. Confirm the report period and the gap between report end date and the current date as part of opening document review.
5. Underweighting sub-processor disclosure gaps. A missing or stale sub-processor list is not a cosmetic issue in an acquisition where the target processes EU personal data. It may indicate that the company has been adding sub-processors without customer notification, creating a GDPR compliance gap that the acquirer will inherit.
What is a tech data room for software M&A?
A tech data room for software M&A is a virtual data room that organizes source code escrow agreements, OSS licence audits, ARR and churn schedules, security certifications, IP assignment records, and data processing agreements into a structured index that buyers can review efficiently. It supplements the standard M&A folders (corporate, financial, legal) with software-specific workstreams that have no equivalent in a traditional business sale.
How is software M&A due diligence different from standard M&A due diligence?
Standard M&A due diligence focuses on corporate records, financial statements, contracts, and HR. Software M&A adds technology-specific workstreams: validating IP ownership (chain-of-title for code), auditing open-source dependencies for licence compliance, verifying SaaS metrics (ARR, NRR, churn cohorts) independently of management figures, reviewing security certifications and penetration test results, and confirming that data processing agreements are in place with all customers processing personal data.
What is code escrow and why does it matter in an acquisition?
Code escrow is a three-party arrangement where source code is deposited with a neutral escrow agent and released to the licensee if the vendor becomes insolvent or fails to maintain the software. In an acquisition, buyers look for a current escrow agreement and a recent verification certificate to confirm the deposited code is current and compilable. An out-of-date deposit may indicate that the production codebase has diverged significantly from what the escrow agent holds, creating IP protection risk.
What OSS licence types create the most risk in a software acquisition?
GPL (GNU General Public License) and AGPL (Affero GPL) create the highest copyleft risk. GPL-licensed components require that software distributed with them also be licensed under the GPL, with source code available. AGPL extends the trigger to software delivered over a network, which affects most SaaS products. LGPL creates a weaker copyleft obligation but still requires analysis. MIT, Apache 2.0, and BSD licences are permissive and generally low risk.
What SaaS metrics should be in a software M&A data room?
The core SaaS metrics for a software M&A data room are: ARR bridge (reconciling beginning to ending ARR through new business, expansion, contraction, and churn), net revenue retention by cohort and customer segment, logo churn rate, seat count versus contracted seats, gross margin by product line, and customer acquisition cost versus lifetime value. The underlying contract register with customer-level detail should support all of these figures so buyers can independently reconstruct the numbers.
How current does a SOC 2 Type II report need to be?
A SOC 2 Type II report should ideally cover a period ending no more than 12 months before the date a buyer reviews it. A report covering a period that ended 15 or more months ago is effectively stale for diligence purposes because it tells buyers little about the current security posture. If the company's annual SOC 2 renewal is in progress, the data room should include the prior report and an estimated completion date for the new one.
What IP assignment gaps are most common in software acquisitions?
The two most common IP assignment gaps are missing PIIA (Proprietary Information and Invention Assignment) agreements for early employees, and missing IP assignment agreements for independent contractors. Early-stage companies often did not obtain signed PIIAs from their first few hires. Contractors who wrote code without a signed work-for-hire agreement retain default ownership under US copyright law. Both gaps can be remediated by retroactive assignments, but they require legal review and may affect deal timing or pricing if discovered late.
How should a software M&A data room handle sub-processors?
The data room should include the company's current sub-processor list, the standard DPA template, and evidence that signed DPAs are in place with all EU-established customers. If the sub-processor list has not been updated in the past six months, buyers will treat it as a gap. For companies that transfer EU personal data to non-adequate countries such as the US, signed Standard Contractual Clauses (2021 version) with each sub-processor should also be included.
Historia real de una adquisición de manufactura de $50M: cómo la empresa objetivo utilizó las funciones del VDR para acelerar la due diligence, gestionar varios postores y cerrar 6 semanas antes de lo esperado.
Guía completa de la due diligence operativa, incluyendo marco, checklist y buenas prácticas para evaluar las operaciones, las personas, los sistemas y el cumplimiento de las empresas objetivo en operaciones de M&A.
Guía completa de la due diligence farmacéutica que incluye requisitos regulatorios, cumplimiento de la FDA, evaluación de producto y consideraciones específicas del sector para transacciones M&A en el ámbito farmacéutico.
Aprenda todo sobre los acuerdos de servicios de transición en operaciones M&A, desde entender los tipos y beneficios de los TSA hasta implementar estrategias de gestión eficaces y evitar errores comunes.