Skip to content
Audits

Technical due diligence: auditing software before an acquisition or investment

Acquiring a company, investing in a startup or taking over a SaaS: what technical due diligence must check (code ownership, dependencies, security, technical debt, key people, hidden costs) and the red flags.

By Damien Ladurelle · Updated · 6 min read

Contents
  1. The questions to ask
  2. What the analysis produces
  3. Common traps
  4. How I approach it
In short

Technical due diligence checks, before an acquisition or investment, what a company’s software is really worth: who owns the code, which licenses and dependencies it relies on, its level of security and technical debt, its dependence on one or two people and its real running costs. It produces a list of costed risks to use in the negotiation.

When you acquire a company whose business runs on software, the software is often the main asset and the least well assessed. The financials show how much it earns, not how much it will cost to maintain, nor whether the company really owns it. Technical due diligence fills that gap.

The questions to ask

Area Question Red flag
Ownership Does the company own the code? Built by a contractor with no written transfer of rights
Licenses Are the components compatible with commercial use? A license that requires publishing the code, not complied with
Dependencies Are the building blocks maintained? A framework or language version at end of life
Security Are the major risks handled? Permissions checked only in the browser, secrets in the code
Data Where is it, is it backed up, GDPR-compliant? Backups never tested, data outside the EU without safeguards
Technical debt What will the next change cost? No tests, duplicated code, manual deployments
People How many people can keep the system running? Only one, with no documentation
Operations What do hosting and third-party services cost? Costs that rise with usage, not in the business plan
Vendors Which external services does it depend on? A critical service with no alternative and no contract

What the analysis produces

  1. A map of the system: components, data, external services, who does what.
  2. A list of risks ranked by severity, each with an estimated cost to fix.
  3. Real running costs over 12 and 36 months.
  4. A conclusion non-technical readers can follow, usable in the negotiation: blocking issues, issues to fix before signing, issues to price in.

Common traps

  • The quickly generated app built with an AI tool or no-code: impressive in a demo, fragile in production. The points to check are covered in taking an internal prototype to production.
  • The sole developer who leaves with the sale: without documentation, the software’s value walks out the door with them.
  • The contractor who owns the code: the company uses the software but does not hold the rights.
  • Hidden subscriptions: cloud services, paid APIs, per-user licenses.

How I approach it

I am a developer and I ran an agency for ten years: I read the code and I know how to turn a technical risk into a business consequence. The method is that of the code audit, extended to operations, vendors and people.

Due diligence builds on my full audit ($2,200 (€1,990)excl. VAT for a typical application); its price is quoted based on the size of the system and the deal timeline, after a 30-minute call. I work under a non-disclosure agreement. For a qualified penetration test or legal advice, I point you to the right people, and my report prepares their work.

Frequently asked questions

Who orders technical due diligence?

Usually the buyer or investor, with the agreement of the seller, who opens access to the code and infrastructure, often under a non-disclosure agreement. The seller can also have it done in advance to prepare the sale and avoid bad surprises during negotiation.

Does it replace legal due diligence?

No. It flags technical points with legal consequences, such as an incompatible license or code written by a contractor without a transfer of rights, but analyzing them is a lawyer’s job.

How much time should I plan for?

A few days for a modest application, more for a platform with several services. The timeline depends mostly on how quickly you get access to the code, the hosting and the people who know the system.

Can the seller refuse access to the code?

They can limit it, for example to supervised read access or an anonymized copy. A total refusal is itself a signal to factor into the negotiation.

Not sure about your project?

Let’s talk for 30 minutes: I’ll tell you honestly which option I would choose in your place.

Appearance
Book a 30-minute call Version française