The title chain must be clarified first.
Collect repositories, developer contracts, licence lists, open-source notices and assignment evidence in a dedicated data-room section.
In a software or SaaS acquisition, source code, title to IP, open source, cloud contracts, customer data and subscriptions must be reviewed.
BRANDAUER Rechtsanwälte
Salzburg law firm for corporate, company and transaction law
Every transaction is handled by a coordinated team of lawyers, legal staff and specialists. In company acquisition matters we look at structure, contract, tax and liability together.
When buying a software or SaaS business, value rarely lies only in revenue. Source code, title to IP, cloud infrastructure, open-source use, customer data, subscriptions and operational continuity matter.
The review differs from generic IT due diligence. Buyers need to know who owns the code, which licences are used, which developers are critical and whether customer contracts, service levels and data processing are robust.
This article complements our overview on IP and IT contracts and separates SaaS from e-commerce acquisitions.
Answer two questions on rights, infrastructure and data.
Already know you want to get in touch? Go straight to the enquiry form.
Without clear rights, the buyer cannot safely continue the product.
Collect repositories, developer contracts, licence lists, open-source notices and assignment evidence in a dedicated data-room section.
Translate title chain, cloud contracts, customer data and subscription metrics into warranties, closing deliverables and handover duties.
Review customer contracts, subprocessors, service levels, termination rights and access concepts before signing.
For a software business, source code is a core asset. The buyer needs evidence that the company owns or may use the required rights. Developer contracts, assignments, licence lists, repositories, documentation and rules for third-party libraries matter.
SaaS depends on ongoing contractual relationships. Buyers should review transferability, termination rights, promised service levels and whether revenue is truly recurring. A strong MRR number is weak if key customers can leave quickly.
Customer data, usage data and support data must be processed lawfully. Roles, processing agreements, deletion concepts, international transfers and technical security should be reviewed. More on this in our article on data protection due diligence.
The overview shows the points that should be reviewed separately in a SaaS acquisition.
| Field | Why it matters | Contract consequence |
|---|---|---|
| Source code Source code | Ownership and use rights secure product value. | Warranty, repository list and handover obligation. |
| Open source Open source | Licence obligations can affect product use. | Disclosure, indemnity or clean-up before completion. |
| Data Data | GDPR and security affect operations and liability. | Data warranties and technical measures. |
The overview does not replace technical code review, but it shows the legal minimum questions for buyers.
Practice note: A SaaS acquisition needs a bridge between technology and contract. The data room should show not only PDFs, but also repository structure, licence lists and access concepts.
Review ownership, use rights, developer contracts, assignments, external providers and open-source components. Without a clear title chain, product value is uncertain.
That depends on contracts, roles and privacy law. Buyers should review processing agreements, information duties, deletion periods and international data transfers.
A SaaS acquisition focuses on subscriptions, software operations, cloud contracts, service levels and source code. A webshop acquisition often focuses more on range, payment providers, logistics and platform dependence.
When buying a company, structure, review and contract decide. Call us directly or send an email, callback within one business day.
Address
BRANDAUER Rechtsanwälte GmbH Giselakai 51 5020 Salzburg
Phone
+43 662 6280000