Audit & takeover

Technical due diligence: what investors check, how to prepare

Before a funding round or an acquisition, investors check code ownership, security, key-person risk and costs. Here is what they look at and how to prepare.

Technical due diligence checks, before a funding round or an acquisition, that the product exists as presented, that the company actually owns it, and that it can grow without hidden costs. The investor or acquirer looks at six topics: ownership of the code and accounts, open source licences, security and GDPR, code quality, dependence on a few people, and finally scalability and costs. To prepare, gather the evidence before anyone asks for it, and fix first whatever could block the deal.

What is technical due diligence?

It is the technical strand of the checks an investor or acquirer runs before committing, alongside the legal, financial and employment strands. How deep it goes depends on the stage and the amount. It can be limited to a questionnaire, a call with the CTO and a demo. It can also extend to a review of the code and tooling by a firm or an outside CTO hired by the investor.

Either way, it runs on evidence: contracts, access, histories, dated documents. A claim you cannot back up becomes one more question at best, and an extra condition in the contract at worst.

Funding round or acquisition: what changes?

Funding round or acquisition: what the other side is after

CriterionFunding roundAcquisition
Core questionWill the product hold up to the growth plan?What are we buying, and what will it cost next?
Typical depthQuestionnaire, interview, demoDetailed review, often with code access
Main focusTeam, architecture, costs at scaleOwnership, licences, security, debt
Effect of a problemMore questions, conditions, a longer timelinePrice revised, warranties, conditions precedent
General tendencies: depth depends on the amount and the investor.

In a funding round, the investor is backing a trajectory: they want to know whether the team and the architecture will hold up to the growth plan you presented. In an acquisition, the buyer takes on the product along with its debt: they want to know exactly what they are buying, what they will have to fix and at what cost. Intellectual property and licences weigh more heavily here, because they go to the heart of what is being bought.

The six topics checked, and the evidence to prepare

1. Ownership of the code and accounts

Under French law, the economic rights in software written by an employee in the course of their duties belong to the employer, unless agreed otherwise (article L113-9 of the French Intellectual Property Code). That rule does not cover code written by a freelancer or an agency: a services contract does not, on its own, take the author’s rights away (article L111-1). Without a written assignment, the contractor may still hold the rights to part of your product. Other countries have their own rules, so if in doubt, have a lawyer review your contracts.

Accounts matter as much as code: the GitHub repository, hosting, database, domain name, Apple and Google developer accounts, Stripe. Each one should be in the company’s name, with at least two administrators and two-factor authentication.

Prepare: a list of the people and companies that wrote code, with their contract and assignment clause; a list of accounts with their owner and administrators.

2. Open source licences

Your product ships open source libraries, and each has its own licence. Permissive licences such as MIT or Apache 2.0 leave a lot of freedom, provided you keep the author notices. Others require you to share source code in some cases. The AGPL v3 licence targets SaaS directly: if you modify an AGPL component and your users interact with it over a network, you must offer them the source code of your modified version (section 13 of the AGPL v3 licence).

Prepare: an inventory of dependencies with their licences and, for every licence that requires sharing, how you comply with it.

3. Security and GDPR

The investor will ask how data is protected and how past incidents were handled. On GDPR, they will expect your record of processing activities (Article 30), contracts with your processors (Article 28), where data is hosted, and your breach procedure, since a breach must be reported to the supervisory authority within 72 hours where feasible (Article 33) (GDPR on EUR-Lex). If your product hosts health data on behalf of French healthcare professionals or institutions, the host must hold HDS certification (article L1111-8 of the French Public Health Code). The expected baseline is covered in the article on SaaS security and GDPR.

Prepare: the results of your latest security review, the list of incidents and how each was handled, the record of processing, the list of processors and the date of your last restore test.

4. Code quality and debt

The underlying question: could another team take over the product? The investor checks whether critical user journeys are tested, whether releases are automated, whether dependencies are still maintained and whether the debt is known. The method for assessing it is in the article on the technical debt audit.

Prepare: a debt register listing each item with its risk, estimated effort and planned date.

5. Team and key-person risk

The “bus factor” counts how many people could leave before nobody knows how to run the product any more. If it is one, the product depends on a single person, and the investor will treat that as a risk. Expect questions on who knows production, who holds admin access, how a new developer gets up to speed and how access is removed when someone leaves.

Prepare: a page showing who knows what, the setup and release documentation, and the offboarding procedure.

6. Scalability and costs

Will the product handle ten times the users, and at what cost? The investor wants to see the architecture diagram, known limits, monthly costs broken down by line (hosting, database, third-party services, AI APIs) and how they project forward. They will also ask what happens if a critical third-party service goes down or changes its pricing.

If your product uses AI, expect questions about which models you use, what data goes to each provider and where the product stands under the EU Artificial Intelligence Act.

Prepare: a one-page architecture diagram and a cost table for today and for ten times the usage.

The technical data room: documents to prepare
  • Architecture diagramOne page: components, data, third-party services.
  • Contracts and assignmentsEvery contributor, their contract and assignment clause.
  • Account listOwner, administrators and two-factor authentication.
  • Open source inventoryDependencies, versions and licences.
  • SecurityLatest review, past incidents and how they were handled.
  • GDPRRecord of processing, processors and hosting locations.
  • Debt registerEach known item, its risk and planned date.
  • CostsMonthly cost by line, today and at 10 times the usage.
  • OrganisationWho knows what, documentation and offboarding.

Red flags that worry investors

A single red flag does not necessarily sink a deal. Each one adds questions, conditions or delays, and most can be fixed before the review.

Six red flags, and how to deal with them before the review
Red flagWhat the investor concludesFix before
Only the founding CTO knows productionThe product depends on one personDocument it and train a second person
Agency-written code, no assignmentThe company may not own all of its productSign a written rights assignment
Accounts in a contractor’s nameA third party can block the productTransfer the accounts to the company
Secret keys in the repositorySecurity is not being managedRotate the keys, turn on detection
Backup never restoredData loss is possibleTest a restore and record the date
Unknown infrastructure costsMargins may shrink with growthBreak costs down and project them

How to prepare, step by step

Getting ready for technical due diligence
  1. InventoryAccounts, contracts, dependencies and existing documents.
  2. Independent auditAn outside view ranks the risks before the investor does.
  3. Blocking fixesOwnership, secrets, backups and data access first.
  4. Data roomA dated piece of evidence for each point.
  5. RehearsalThe CTO answers the hard questions out loud.
  6. Post-deal planWhat is left to do, with a budget and dates.

Start before you approach investors. Some fixes depend on third parties: a rights assignment has to be negotiated with the agency that wrote the code, an account transfer with the contractor who holds it. Once the data room is open, it is late to start them calmly.

An independent audit is not mandatory. It lets you find the problems before the investor does, and it adds a dated document to the data room: a report that ranks the risks, with a plan. Fix ownership, secrets, backups and data access first. For everything else, present a dated, budgeted plan rather than a rushed fix.

Questions to prepare for

These are typical questions in a technical review. Rehearse the answers out loud with the person who will give them on the day.

  • Who wrote the code, and under what contract?
  • What happens if your CTO leaves tomorrow?
  • Where is personal data hosted, and with which providers?
  • Have you had a security incident? How did you handle it?
  • What does infrastructure cost per customer, and at ten times the customers?
  • Which parts of the product would need rewriting, and why?
  • Which open source components do you use, under which licences?

Answer with dated facts. If something is not resolved, say so, along with the plan and the target date. Known, planned debt is open to discussion; debt the investor uncovers alone erodes trust.

My take as a CTO

I co-founded Welco in 2019 and I am its CTO: I built the technical team and the architecture of a platform that now has more than 150,000 registered users. I have also been a partner and CTO at Jo’s Burger since 2024. In my client work, I follow one simple rule: the code, accounts and documentation are in the client’s name, and I hand them over at the end. It prevents the problem that takes longest to sort out during a deal, a product the company does not fully own. My advice: have the app audited before you open the data room, by someone who did not write the code. The report should say what it sees, with examples from the code. An audit that merely confirms a decision already made will not help you when an investor starts asking questions.

Frequently asked questions

When should we start preparing for technical due diligence?

Before you approach investors or a buyer. Fixes that depend on third parties, such as a rights assignment or an account transfer, take time. A checklist followed by an independent audit tells you early what is missing.

Our app was built by an agency. Is that a problem?

Not in itself. Check that the contract includes a written assignment of rights in the code, that the code lives in a repository you own, and that the accounts (hosting, database, domain, app stores) are in your name.

Should we have the app audited before fundraising?

It is not mandatory, but an audit surfaces problems before the investor does and gives you a dated plan to present. At Techvisor, the express assessment costs €1,200 excluding VAT for about 3 working days, and the full audit with a costed roadmap costs €2,400 excluding VAT for about 5 working days.

Can an app built with Lovable or Bolt pass due diligence?

Yes, if it meets the same requirements: code exported to a repository in your name, database access rules checked, no exposed secret keys, tested backups and known costs.

What if the audit uncovers a serious problem?

Fix it before the review if you can. If not, document it: what the problem is, the risk, the plan, the budget and the date. A known, costed problem can be negotiated. A hidden problem that surfaces during the review weighs on both trust and terms.

Next step

To see where you stand, the production-readiness checklist (in French) covers several points of this review in 30 questions: accounts, secrets, backups and GDPR.

To walk into the review with an independent report and a plan, the app audit checks security, code, data, account ownership and costs. To talk it through, book a 15-minute call. The call costs nothing and comes with no commitment.

Sources

Technical diagnostic

A diagnostic of your code in 3 working days

Security, code, data and cost review. A green, amber or red rating for each point. A one-hour video debrief.

from €1,200 excl. VAT

Topics: technical due diligence · fundraising · technical audit · code ownership · startup

Book a call