Technical Due Diligence for Hardware and Software Products

A product demonstration shows what works on the day. Technical due diligence looks at what sits behind it: whether the design files exist and are complete, whether the software can be rebuilt, whether key parts are still in production and whether the code can legally be shipped. It is used by investors, acquirers and companies taking over a product from a supplier. This article explains what a review examines and the warning signs to look for.

At a glance

Ownership
Who holds the designs, code and licences the product depends on.
Licences
Open-source obligations that follow the code into the product.
Key people
How much of the product exists only in a few engineers’ heads.
Lifecycle
Whether key components are active, not recommended for new designs, or end of life.

The problem

A product can work well and still be expensive to own. Common hidden problems include design files held only as PDFs, firmware that builds on one machine, components nearing end of life and certification that was assumed but never completed.

These issues rarely show in a demonstration or a slide deck. They appear after the transaction, when the new owner tries to manufacture, modify or certify the product.

Ask to rebuild the product from its files. What cannot be rebuilt is not really owned.

What reviewers examine

For hardware: native schematic and layout files, the bill of materials with lifecycle status and alternate sources, test and certification reports, and manufacturing documentation. For software: a clean build from version control, the dependency list with licences, test coverage, security practice and the update mechanism.

Copyleft licences such as the GPL carry obligations when the software is distributed, so an inventory of open-source components matters. Findings are graded by severity, with an estimate of the effort needed to resolve each one.

What good looks like

Agree the scope and the questions the review must answer, then issue a document and access request.

Examine the evidence hands-on: rebuild the software, inspect design files and interview the engineers who know the product.

Report findings graded by severity, with the cost and time to resolve each, so they can inform the decision.

Evidence to request and warning signs
AreaAsk forWarning sign
Hardware designNative schematic and layout filesOnly PDFs or Gerbers available
ComponentsBOM with lifecycle status and sourcesSingle-source or end-of-life parts
SoftwareA clean build from version controlBuilds only on one machine
Open sourceDependency and licence inventoryObligations nobody has reviewed
TestingTest plans and resultsNo records beyond demonstrations
ComplianceTest reports and declarationsApprovals assumed, not obtained
A starting list. The scope depends on the product and the decision being made.

How a review runs

  1. Scope: Questions and decision
  2. Request: Documents and access
  3. Inspect: Rebuild, review files
  4. Interview: Engineers and suppliers
  5. Report: Graded findings with costs
Hands-on checks carry more weight than documents alone.

What it changes

Clear Picture

The real state of the product is known before commitment.

Priced Risk

Problems carry effort estimates that feed into the decision.

Smoother Handover

Gaps in documentation are found while the original team is available.

Legal Clarity

Licence obligations are identified before shipping.

Where to go next

Legal and licence questions identified in the review should be confirmed by a qualified lawyer. A technical review identifies them; it does not give legal advice.

If the product will move to a new team or factory, plan the knowledge transfer while the original engineers are still involved.

Problems this prevents

  • Design files that exist only as PDFs
  • Firmware that builds on one machine
  • Open-source obligations nobody tracked
  • Certification assumed but never done

Discuss your project

Email support@aavico.com or use Get in Touch when the website finishes loading.