Technical due diligence checklist for startups (before you raise)

·Updated · 8 min read · fundraising · leadership

Technical due diligence rarely kills a deal on its own. What it does is slow the round, cut the valuation or add conditions. Most of what reviewers flag can be fixed in a few weeks if you know what they look for.

Not legal advice. This checklist covers the technical side of due diligence. Questions about IP ownership, licences and contracts are legal questions; confirm them with your lawyer before the data room opens.

Somewhere between the term sheet and the money in the bank, an investor sends a technical reviewer to look at your product. Sometimes it's a partner who used to be a CTO, sometimes a specialist firm, sometimes an engineer from a portfolio company. They have a few days, a questionnaire and a call with your team.

Their job is not to judge whether your code is beautiful. It is to answer three questions for the investment committee: can this product scale with the plan in the deck, is there a hidden liability (security, IP, data protection, one person who knows everything), and how much will it cost to fix what's broken. This checklist is organised around those questions, and it's the one we use when we prepare companies for a round.

Technical due diligence questions, area by area

Expect questions in seven areas. Answer each with a short document or a screen share, not a promise.

1. Architecture and scalability

2. Code quality and engineering process

3. Security and compliance

4. Infrastructure and cost

5. Team and key-person risk

6. IP ownership and open-source licences

7. Data protection and GDPR

The five documents to prepare

Five documents answer most of a reviewer's questions before they ask them. Put them in a data-room folder, keep each to a few pages, and date them.

DocumentWhat it should containEffort
Architecture diagramOne page: components, data stores, external services, regions, how traffic flows. Plus a paragraph on what changes at 10x.1 to 2 days
Data-flow mapWhich personal data enters where, which systems and vendors it touches, where it's stored and for how long. Doubles as the base of your Article 30 record.2 to 3 days
Incident historyThe last 12 months of outages and security events: date, impact, duration, root cause, what changed. Our incident response runbook template has the postmortem format.1 day if you kept notes
Cost breakdownMonthly cloud and SaaS spend by service and environment for the last 6 to 12 months, cost per customer or per transaction, and the main drivers.1 day
Access listEvery system with admin access (cloud, code hosting, DNS, registrar, app stores, payments, email), who holds it, MFA status, and which accounts are company-owned.1 day

Add a short technical roadmap and a list of known technical debt with rough effort estimates. Showing that you already know the weak spots is the single most reassuring thing you can do in due diligence.

Three checks you can run this afternoon

You don't need a tool vendor to find most of what a reviewer will find. These commands surface the access, key-person and licence issues that come up most often.

Who has access. The IAM credential report lists every IAM user with password, MFA and access-key status. GitHub's API lists organisation members and outside collaborators.

# AWS: IAM users, MFA and access keys (run per account)
aws iam generate-credential-report
aws iam get-credential-report --query Content --output text   | base64 --decode   | cut -d, -f1,4,5,8,9,10,11 > iam-users.csv

# GitHub: org members and outside collaborators
gh api orgs/YOUR_ORG/members --paginate --jq '.[].login' > gh-members.txt
gh api orgs/YOUR_ORG/outside_collaborators --paginate --jq '.[].login' > gh-outside.txt

If you've moved people to IAM Identity Center, the credential report should show almost no human users. That is the answer reviewers want.

Key-person risk. Who has written the code in each part of the repository over the last year?

# Top contributors over the last 12 months
git shortlog -sn --no-merges --since="12 months ago" HEAD | head -5

# Main author per top-level directory
for d in */; do
  echo "$d $(git log --no-merges --since='12 months ago' --format='%an' -- "$d"     | sort | uniq -c | sort -rn | head -1)"
done

If one name dominates every directory, that's your key-person risk, in a form you can show a reviewer together with your plan to spread the knowledge.

Open-source licences. Syft builds a software bill of materials from a directory or container image. Filter it for licences that carry source-disclosure or commercial-use conditions, then review each hit by hand.

syft dir:. -o syft-json=sbom.json

jq -r '.artifacts[]
  | [.name, .version,
     ([.licenses[] | if .spdxExpression != "" then .spdxExpression else .value end]
      | join("; "))]
  | @tsv' sbom.json   | grep -Ei 'AGPL|GPL|SSPL|BUSL|Commons-Clause'

A GPL or LGPL hit is not automatically a problem. It depends on how the component is used and distributed, which is a question for a lawyer once you have the list. Not knowing the list is the problem.

Red flags and how to fix them in 30 to 60 days

Most red flags are fixable in weeks, and a reviewer who sees a dated fix plan treats them very differently from one who discovers them. This is the order we'd work in.

Red flagWhy it worries an investorFixTime
Freelancer or agency code without a written IP assignmentThe company may not own its productSigned assignment agreements from every past contributor, reviewed by a lawyer1 to 4 weeks, depends on reaching people
Production in a founder's or contractor's personal accountOwnership and continuity riskMove to company-owned accounts under an AWS Organization; transfer domains and app store listings1 to 2 weeks
No MFA, shared logins, long-lived keysBreach likelihoodSSO with MFA, delete IAM users and keys, OIDC for CI1 to 2 weeks
Backups never restoredOne bad day ends the companyAutomated backups, a documented restore test, the time recordedDays
Infrastructure clicked together by handCan't rebuild, can't review changesImport the core (network, database, compute) into Terraform or OpenTofu2 to 6 weeks
One engineer knows everythingKey-person riskArchitecture docs, runbooks, pairing, a second person deploying4 to 8 weeks, ongoing
Cloud cost growing faster than revenueGross margin story breaksTagging, rightsizing, commitments; see our AWS cost checklist2 to 4 weeks
No GDPR records, missing DPAsRegulatory and customer-contract riskData-flow map, Article 30 record, signed DPAs, privacy notice updated2 to 3 weeks
Copyleft component in a distributed or network-served product without complianceForced disclosure or rewriteReplace the component or meet the licence terms, with legal sign-offVaries
Don't hide what you can't fix in time. A known issue with an owner and a date costs you little. The same issue found by the reviewer costs you trust, and trust is what the rest of the process runs on.

How long before the round to start

Start two to three months before you expect a term sheet. That leaves time for the 30 to 60 day fixes without doing them in the same weeks as the round itself, when the team is answering questions and still shipping.

  1. Weeks 1 to 2: run the checks above, write the five documents, list every red flag honestly.
  2. Weeks 3 to 6: fix ownership, access and backups first, because they are fast and they are what reviewers check first. Chase IP assignments in parallel.
  3. Weeks 6 to 10: infrastructure as code, cost work, documentation to reduce key-person risk.
  4. Before the data room opens: update the documents with what you fixed and a dated plan for what's left.

An independent review before investors run theirs is the cheapest way to find out what they'll find. Our five-dimension cloud audit covers the infrastructure, security and cost side.

If you're heading into a round without a senior technical person on the team, this is what a fractional CTO is for: preparing the data room, sitting in the reviewer call and owning the fix plan. If you mainly need the infrastructure side checked and documented, start with a cloud audit.

Frequently asked questions

What is included in a technical due diligence checklist?

A technical due diligence checklist covers architecture and scalability, code quality and engineering process, security and compliance, infrastructure and cloud cost, team and key-person risk, IP ownership and open-source licences, and data protection. Prepare an architecture diagram, data-flow map, incident history, cost breakdown and access list before investors ask.

How long does technical due diligence take for a startup?

The reviewer's work usually takes days to a couple of weeks, depending on the round and how ready you are. Preparation is what takes time: allow two to three months before the round to write the documents and fix red flags such as missing IP assignments, personal-account ownership or untested backups.

Do investors check open-source licences during due diligence?

Many do, especially at Series A and later. They want to know which licences are in your dependencies and whether you meet their obligations. Copyleft licences such as GPL and AGPL can require you to publish source code, and AGPL applies to software users reach over a network. Generate an SBOM and review the copyleft hits with a lawyer.

Does a Greek startup own code written by freelancers?

Not automatically. Under Greek Law 2121/1993, economic rights in software written by employees pass to the employer, but code written by freelancers, agencies or founders before incorporation needs a written assignment. Article 14 makes unwritten transfers void, so collect signed assignments from every past contributor before due diligence.

Tell us what you need