Fast. Simple. No meetings. No delays.
Home / Blog / Tel Aviv / Preparing Your Codebase for Investor and Acquirer Due Diligence

Preparing Your Codebase for Investor and Acquirer Due Diligence

What technical due diligence usually looks at — repository hygiene, dependencies, secrets, backups, tests and deployment — and how to prepare.

Cover graphic for the article: Preparing Your Codebase for Investor and Acquirer Due Diligence

A codebase due diligence checklist helps you prepare for the moment an investor or acquirer asks to look at your software. Reviewers usually want to see that the code is owned, readable, reasonably secure, backed up, tested and deployable by someone other than its author. Preparing early turns a stressful audit into a routine review.

What a codebase due diligence checklist should cover

Technical due diligence is a structured look at risk. Reviewers are not hunting for perfect code; they want to know whether the product can keep running and growing without surprises. Typical questions include:

  • Does the company actually own what it built, and who has access to it?
  • Can the system be built, deployed and restored by someone new?
  • Are there obvious security gaps, and how are secrets handled?
  • How dependent is the product on one person's knowledge?
  • What third-party components and licences does it depend on?
  • How much of the code is tested, and how risky is it to change?

Expect a mix of document requests, a call with your technical lead, and sometimes a read-only look at the repository. Being able to answer honestly and show evidence matters more than having no weaknesses. A short list of known issues with a plan beside each one reads far better than silence.

Repository and access hygiene

  • All code lives in repositories owned by the company's organisation account, not personal accounts of founders or contractors.
  • Every former employee, contractor and agency has been removed from repositories, cloud consoles, DNS, app stores and third-party tools.
  • Access is individual and uses two-step verification. No shared logins.
  • The main branch is protected, and changes go through review or at least a pull request.
  • The commit history does not contain pasted passwords or keys. If it does, rotate those credentials; deleting the file is not enough.
  • Domains, certificates and cloud accounts are registered to the company with a recoverable owner contact.
  • Contractor and employee agreements assign intellectual property to the company. Have a lawyer confirm this; it is a legal question, not a technical one.

Dependencies and licences

Modern applications are mostly third-party code. Reviewers will ask what you use and whether it is maintained.

  • Produce a list of direct dependencies from your package manager's lock file, with versions.
  • Run a dependency vulnerability scan and fix or document the findings.
  • Identify abandoned or end-of-life frameworks and runtimes, and note a plan to upgrade.
  • List the licence of each significant dependency. Some open-source licences place conditions on how you distribute or combine code, so check that none conflicts with how you use it. This is not legal advice; a lawyer can interpret the terms for your product.
  • Record paid services and APIs the product relies on, and what happens if one disappears.

Secrets and configuration

  • No credentials, tokens or private keys in the repository. Use environment variables or a secrets manager.
  • Keep an inventory of secrets: what each one is for, where it is stored and who can rotate it.
  • Use separate credentials for development, staging and production.
  • Test that you can rotate a key without downtime.
  • Keep sample configuration files with placeholder values, so a new developer knows what is needed.

Backups and disaster recovery

Reviewers like evidence. A backup that has never been restored is an assumption.

  • Automated database backups, stored away from the primary server and protected against deletion.
  • Uploaded files and other stateful data included in the plan.
  • A written, tested restore procedure. Do a restore drill and note how long it takes and what went wrong.
  • A short statement of how much data loss and downtime the business could tolerate, and whether your setup meets it.
  • Monitoring and alerting that tells a human when the site or a scheduled job fails.

Tests and CI

You do not need exhaustive coverage. You need enough automation that changes are not frightening.

  • An automated test suite that runs with a single command, covering the riskiest logic such as payments, permissions and data calculations.
  • A continuous integration pipeline that runs tests and linting on every change.
  • A repeatable deployment process, ideally automated, with a way to roll back.
  • A staging environment that resembles production.
  • A note on what is not tested, and why. Honest gaps are acceptable; hidden ones are not.

If parts of the system are fragile, our discussion of technical debt in startups helps you decide what to fix before a review and what to simply disclose. For security specifics, the OWASP-based security checklist is a good self-assessment.

Documentation that saves hours

A small amount of writing prevents long calls.

  1. A README explaining how to run the project locally and how to run tests.
  2. A one-page architecture overview: main components, data stores, external services and how they connect, with a simple diagram.
  3. A deployment and rollback guide.
  4. A list of environments and where each one lives.
  5. A short log of key decisions and known issues. Our guidance on documentation and handover goes further.

Putting it together

Prepare a single shared folder with the access list, dependency and licence list, architecture overview, backup and restore notes, and known-issues list. Walk through it yourself as if you were the reviewer, and fix what is quick. The rest becomes an honest roadmap. If you want an outside engineering team to review the code or close gaps, see how we work with Tel Aviv startups.

Frequently asked questions

What do technical due diligence reviewers ask for?

Usually an architecture overview, repository and cloud access lists, dependency and licence inventories, security and secrets handling, backup and restore evidence, test and deployment practices, and a list of known issues. They also ask how dependent the product is on individual people and whether the company owns its code.

How long does preparation take?

It depends on the state of the codebase, the size of the system and how much documentation exists. A tidy small product may need little more than writing a few documents, while one with shared logins, missing backups and no tests needs real engineering work. Start an audit of yourself early to find out.

Do open-source licences matter in diligence?

Yes, reviewers often ask for a list of dependencies and their licences because some licences attach conditions to how code is distributed or combined. Keep an inventory and flag anything unusual. This is not legal advice; ask a qualified lawyer to interpret how the licences apply to your product.

Related articles

🚀 Start Now