GuideDue diligence

    Technical due diligence checklist: what to check before you invest in or buy a software company

    Short answer

    A technical due diligence answers three questions for an investor or buyer: does the technology do what the company says, what will it cost to keep and grow it, and which risks could change the price or the deal. It covers ten areas, from architecture and code to security, cloud cost, the team and open-source licences. The useful output is not a score but a short list of findings, each with its impact on the deal, and a costed plan to fix what matters.

    Checklist

    The ten areas and what to look for

    Technical due diligence areas
    AreaWhat to checkTypical red flag
    1. Product and architectureDoes the system match the pitch? Main components, data flows, third-party dependenciesCore feature is manual work or a vendor's product behind a thin layer
    2. Code qualityStructure, tests, review practice, hot spots, age of dependenciesNo tests on the money or data paths; one huge module everyone fears
    3. SecurityAccess control, secrets, encryption, penetration tests, incident historyProduction secrets in the repository; no record of past incidents
    4. Infrastructure and costCloud setup, environments, monitoring, backups, cost per customer or per transactionCloud cost grows faster than revenue; backups never restored
    5. ScalabilityLoad today and headroom, bottlenecks, what breaks at ten times the volumeA single database or service that cannot scale without a rewrite
    6. Delivery processRelease frequency, CI/CD, incident handling, roadmap predictabilityReleases by hand from a developer laptop
    7. Team and key peopleWho knows what, contractors vs staff, hiring pipeline, retentionOne person holds the knowledge and the access
    8. IP and open sourceCode ownership, contractor IP assignment, open-source licencesCopyleft code in a distributed product; contractors without IP assignment
    9. Data and compliancePersonal data map, GDPR, sector rules, data residencyCustomer data copied into tools nobody tracks
    10. AI useWhich models and vendors, what data goes to them, evaluation, costProduct depends on one model API with no fallback and no evaluation

    What changes a deal?

    Most findings in a due diligence are normal engineering debt: every company has some, and a good report says so plainly instead of padding the list. The findings that change the price, the structure or the decision are rarer, and they tend to fall into five groups:

    • The product is not what was sold. A core capability is manual, outsourced or a resold vendor product.
    • Ownership is unclear. Code written by contractors without IP assignment, or licences that conflict with how the product is distributed.
    • A rewrite is coming. The architecture cannot carry the growth plan without rebuilding a core part, and the plan does not budget for it.
    • Key-person risk. One or two people hold the knowledge and the access, and are not tied to the deal.
    • Security or compliance exposure. A breach, an unpatched critical issue, or a regulatory requirement the product does not meet and has no plan for.

    Extra checks for crypto and payments companies

    • Who can sign transactions, how keys are stored, and what happens if a key holder leaves. See our custody models guide.
    • Smart contract audits: by whom, on which version, and whether the deployed code matches the audited code.
    • Reconciliation between the ledger, the chain and the providers, and how mismatches are found.
    • Licences the product relies on, and whether they sit with the company or a partner. See our MiCA guide.
    • Concentration on one provider for custody, ramps or payouts, and the exit plan.

    Extra checks for device and firmware companies

    • Secure boot, signed updates and how firmware signing keys are protected.
    • An update path for every product line still on sale, and the support period promised to customers.
    • Readiness for the EU Cyber Resilience Act, which applies in full from 11 December 2027, and the reporting duty that has applied since 11 September 2026.
    • Third-party modules and SDKs: who supports them, and whether there is a software bill of materials.
    • Manufacturing: who can flash devices, and whether production keys are separated from development keys.

    Our CRA readiness checklist covers the device side in detail.

    How a due diligence runs

    1. Scope. Agree the questions that matter for this deal, the access and the deadline.
    2. Documents and access. Code, cloud accounts, bills, architecture and security documents, under NDA.
    3. Interviews. The CTO, two or three engineers, and the person who runs infrastructure.
    4. Analysis. Code and dependency scans, a cloud and cost review, the architecture against the growth plan.
    5. Findings review. Walk the findings with the company's CTO to correct facts.
    6. Report. Findings ranked by impact on the deal, and a costed remediation plan.

    What should the report give you?

    • A one-page summary a partner or board can read in five minutes.
    • Each finding with evidence, its impact on the deal, and the effort to fix it.
    • A remediation plan in order, with the cost in team-months, for the first 100 days after closing.
    • Questions to put in the deal terms: warranties, conditions before closing, retention of key people.
    • What is fine. A report that only lists problems makes it hard to see the real risks.

    Why us

    We have built and run the kinds of systems we review: payment and stablecoin platforms, wallet and custody infrastructure, device firmware, and AI workflows for regulated teams. Our founders built Stablerail, Transatron and Pitchbreeze. We use the same delivery method as in our builds: a written scope and fixed price before we start. See how our tech due diligence review runs.

    FAQ

    Q01Who needs a technical due diligence?

    Investors before a round, buyers before an acquisition, and boards or new CTOs who need an independent view of what they own. Companies preparing to raise often run one on themselves first, so nothing surprises them in the investor's.

    Q02What access does the reviewer need?

    Read access to the code repositories and the issue tracker, a read-only view of the cloud accounts and their bills, the architecture and security documents that exist, and interviews with the CTO and two or three engineers. Everything stays under NDA.

    Q03What is the difference between a red-flag review and a full review?

    A red-flag review looks only for findings that change the deal: price, structure or whether to go ahead. A full review covers every area in depth and ends with a remediation plan and its cost.

    Q04Will the team we review see the report?

    That is the client's choice. We recommend sharing the findings with the CTO before the report is final, so factual errors are corrected and the remediation plan is realistic.

    Sources

    Next step

    Investing in or buying a software company?

    A 30 minute call with Mykhailo about the deal, the questions that matter and the access a review needs.

    See the red-flag review

    Mykhailo Tiutin

    CTO, Vareger

    Mykhailo Tiutin, CTO, Vareger