← All articlesInfra and cloud

Technical due diligence checklist for startups

Technical due diligence mostly looks for what can lower the price or kill the deal. Here is how to run it on yourself before the buyer or investor does.

Julien Mauclair · ~9 min · intermediate
StackgitnpmAWSRDS

Technical due diligence checks code ownership, licenses, security, infrastructure and team. Four items block a deal: code the company does not own, a misplaced copyleft license, exposed secrets, and data nobody can restore. The rest mostly lowers the price.

01What the audit is really looking for

Madewithlove sums up the goal: find the hidden problems that may hurt the company's value or even kill the deal. Online checklists usually list everything: architecture, scalability, code quality, security, team. They also admit there is no one-size-fits-all checklist for startups. The trouble is that they put every item on the same level. An investor or a buyer does not think that way. They ask three questions: does the company own what it sells, can a hidden risk cost a lot after signing, and how much will it take to keep the product moving.

The first question is binary. If the answer is no, the deal stops or waits for a fix. The second turns into protective clauses in the contract, or a lower price. The third is a negotiation. That is why this checklist sorts every item into three levels:

BlockingThe deal waits for a fix, or stops.
NegotiableThe item becomes a clause, a condition or a price cut.
CosmeticThe auditor notes it, but it does not change the decision.

This ranking is a recommendation, not a rule: a strategic buyer acquiring a technology does not weigh things like a fund backing growth. But it tells you where to start when time is short. If you have no CTO to prepare this work, the article on what a fractional CTO actually does explains what you can hand to someone a few days a month.

02The checklist, area by area

Code ownershipBlocking. Every author is an employee or signed a written IP assignment.
Open source licensesBlocking if a copyleft license touches the product you sell.
Secrets in historyBlocking until any production key found has been rotated.
Data restoresBlocking if nobody has ever restored a backup.
Account accessNegotiable. Accounts belong to the company, with MFA.
Personal dataNegotiable. A GDPR record and processor contracts exist.
Key-person riskNegotiable. More than one person knows each part of the code.
Vulnerable dependenciesNegotiable. No known high-severity issue without a fix plan.
DeliveryNegotiable. You can measure deployment frequency and reliability.
Style, tests, docsCosmetic, unless their absence makes the code impossible to take over.

03Code ownership and licenses: the two items that stop a deal

Who owns the code

Under French law, which governs a French startup, code written by an employee as part of their job belongs to the employer: article L113-9 of the Intellectual Property Code vests the economic rights in software in the employer. The rule does not cover interns, temps, contractors placed by an agency or freelancers. For them, you need a written assignment that meets the conditions of article L131-3, as the same analysis points out. Without it, the freelancer who wrote the first MVP may still hold the rights to that code. Other countries have their own rules, so the exact paperwork depends on where the company and its contributors are.

To check, match the list of repository authors against contracts. The command below prints every author with their email and commit count. It relies on git shortlog, whose --no-merges option skips merge commits.

authors.shBASHCopy
# Every author since the first commit, with their email
git shortlog -sne --no-merges --all
# For each email: employment contract, or written assignment?

Each line should map to an employment contract or a signed assignment. An unknown personal address, an agency or a former co-founder with no paperwork are the cases to fix before the audit, not during it. The legal wording belongs to a lawyer: this command only finds the gaps.

Dependency licenses

A permissive license like MIT rarely causes trouble. Copyleft licenses need more care. The AGPL in particular requires a modified version to offer its source code to all users interacting with it remotely through a computer network, which squarely targets a SaaS. A modified AGPL component at the core of the product is something a buyer will want to understand in detail.

license-checker lists the licenses of a Node.js project. The --onlyAllow option fails the command as soon as a license is not on your list, which also makes it a CI guardrail.

licenses.shBASHCopy
# Overview of production licenses
npx license-checker --production --summary
# Fail if a license is not on the allowed list
npx license-checker --production --onlyAllow "MIT;ISC;Apache-2.0;BSD-2-Clause;BSD-3-Clause"
# Full export for the data room
npx license-checker --production --csv --out licenses.csv

Adjust the list to your context. A license missing from the list is not necessarily a problem: it just needs reading. Do the same for the other languages in the project with their own ecosystem's tool.

04Security and infrastructure: prove it, don't claim it

Secrets in git history

A secret removed from the code stays in git history, and the auditor will get the full repository. Gitleaks scans that history with gitleaks git -v. Its author says the project will only get security patches from now on and that he is focusing on Betterleaks, worth a look for a fresh setup.

secrets.shBASHCopy
gitleaks git -v --report-path gitleaks-report.json
npm audit --audit-level=high

Any production key you find must be rotated, not just removed from the repository. The method is in handling secrets properly. The second line runs npm audit, which only fails from high-severity issues upward. For the rest of a recent app's attack surface, the security checklist before going live gives ten tests with their expected result.

Account access

The buyer wants to know who can get into the infrastructure, and whether the accounts really belong to the company. On AWS, the IAM credential report lists every user with their MFA status and when their password and access keys were last used. AWS regenerates it at most once every four hours.

aws-access.shBASHCopy
aws iam generate-credential-report
aws iam get-credential-report --query Content --output text | base64 --decode > credentials.csv

In the file, look at three columns: mfa_active for every human, then password_last_used and access_key_1_last_used_date to spot former team members. Run the same review on the domain registrar, the code host, the payment provider and email. An account opened under a founder's personal name or an agency's name should be transferred before the audit.

Data restores

Having backups proves nothing. What counts is having restored one, with a date and a duration. On RDS, point-in-time restore creates a new DB instance without modifying the source, so you can run the test without risk to production.

restore-test.shBASHCopy
aws rds restore-db-instance-to-point-in-time \
--source-db-instance-identifier prod-db \
--target-db-instance-identifier audit-restore-test \
--use-latest-restorable-time

Write down the start time, the time the instance answers and the result of a check query, then delete the test instance so you stop paying for it. That record is worth more than a page of backup policy. The rest of the method is in backups that actually work.

Personal data

For a company that handles personal data in the EU, two documents always come up. The record of processing activities required by GDPR article 30 applies to every organisation, whatever its size, as the French regulator states. Contracts with processors follow article 28: hosting, email tools, analytics. And if a breach happened, the buyer will ask whether it was reported to the authority, which must happen within 72 hours where feasible. A hidden breach becomes a legal risk for the buyer, far worse than a reported one.

05Team and delivery: the risk you can't see in the code

Key-person risk

The same git command, narrowed to a period and a folder, shows who really knows each part of the product.

key-person.shBASHCopy
# Who touched the billing code over the last twelve months?
git shortlog -sn --no-merges --since="12 months ago" -- src/billing

If a single person shows up on the critical parts, and that person leaves after the deal, the buyer is acquiring a product nobody can evolve. It is not blocking on its own, but it often ends in a retention clause or a lower price. The answer is documentation, cross code reviews and a second developer on every critical area.

Ability to ship

A buyer wants to know whether the team ships often and without breaking things. DORA's metrics give a shared vocabulary: change lead time, deployment frequency, change fail rate, failed deployment recovery time and deployment rework rate. Nobody expects perfect numbers from a startup. Being able to produce them, though, shows the pipeline exists and is under control. To make it reliable, see make a deployment boring.

06Preparing the technical data room

Gather everything in one folder before the first meeting:

·an up-to-date architecture diagram, including third-party services;
·the list of code authors and the matching contracts or assignments;
·the license export and the reasoning behind any copyleft case;
·the gitleaks report and proof that any key found was rotated;
·a dated record of a restore;
·the list of accounts, their owner and their MFA status;
·the GDPR record and processor contracts;
·an honest list of known technical debt, with a rough size for fixing it.

That last item often surprises founders. Yet debt the team wrote down can be negotiated, while debt the auditor finds makes them doubt everything else.

Careful

This checklist does not replace a lawyer or an auditor. IP, licensing and GDPR questions need a legal reading, and the commands above only help you find the gaps before someone else points them out.

07FAQ

How long does technical due diligence take?

It depends on the size of the product and how prepared the team is. The part you control is preparation: a complete data room avoids back-and-forth, which often takes longer than the analysis itself.

Should I show all the code to the investor?

Not without a framework. One preparation guide suggests considering a non-disclosure agreement before any technical due diligence. Full repository access usually goes to the appointed auditor, not to the investor's whole team.

Can technical debt sink a fundraise?

Rarely on its own. It mostly weighs on price and terms. What kills a deal are the blocking items: code the company does not own, a license that clashes with the business model, a hidden breach or unrecoverable data.

A freelancer wrote the MVP without an IP assignment: what now?

Don't wait for the audit. Reach out to sign a written assignment covering the code already delivered, drafted by a lawyer. If that is not possible, find out how much of that code is still in the current product, and consider rewriting it.

08Sources

Sources & further reading
01Madewithlove, due diligence checklistpurpose of a technical audit.↗02Sphere, technical due diligence checklistareas covered and non-disclosure agreement.↗03Village de la Justice, software ownership in a companyFrench IP code articles L113-9 and L131-3, freelancers and interns.↗04GNU AGPL v3section 13 on remote network interaction.↗05license-checkercommand options.↗06git shortlog--no-merges and --since options.↗07Gitleaksscanning git for secrets, project status.↗08npm auditseverity levels and exit codes.↗09AWS, IAM credential reportcolumns and commands.↗10AWS, RDS point-in-time restorehow the restore works.↗11CNIL, record of processing activitiesGDPR article 30.↗12CNIL, GDPR chapter 4article 28 on processors.↗13CNIL, reporting a data breach72-hour deadline.↗14DORA, software delivery metricsdefinitions of the five metrics.↗
In short

Start with the blocking items: code ownership, licenses, secrets and data restores. Everything else can be negotiated, as long as you wrote it down before anyone asked.

Talk about your project ↗
Julien MauclairJulien Mauclair is the co-founder and CTO of Klickbee, where he builds the agency’s websites, tracking and AI automations, and develops Klickbee Tracking. He also runs Stralya, which designs and runs AWS infrastructure for scale-ups. Before that, he built the entire AWS infrastructure of an e-commerce business, since sold.

Read next