FoundationState

FoundationState Insights

Better questions. Clearer product and technology decisions.

Practical guides for business leaders, investors and acquirers: technical risk, product execution and the evidence behind a decision.

Public due diligence worked report

Start with the output

Inside a due diligence report

An explained, ungated 14-page worked example.

Explore the report →

31 guides · Page 2 of 4

16 August 20269 min read

DevOps and Delivery Maturity in Due Diligence: What Release Practices Reveal

A DevOps maturity assessment helps investors test whether release practices, CI/CD, incident response and delivery evidence support the roadmap.

DevOpsEngineering Teams
Read Insight
9 August 20269 min read

Scalability Due Diligence: Can the Platform Support 10x Growth?

Scalability due diligence helps investors test whether architecture, cloud economics, bottlenecks and delivery capacity can support the growth plan.

ScalabilityArchitecture
Read Insight
3 August 202610 min read

SaaS Metrics Due Diligence: ARR, Churn, NRR and Cohorts

Verify ARR, churn, net revenue retention and cohorts against customer evidence, with practical questions and an example of how headline growth can mask retention risk.

SaaS MetricsProduct Due Diligence
Read Insight
26 July 202611 min read

Engineering Due Diligence: Team Strategy, Capability and Key-Person Risk

Build an engineering due diligence strategy around the growth plan, critical team capabilities and knowledge transfer, with evidence requests and investor interview questions.

Engineering TeamsTechnical Due Diligence
Read Insight
19 July 20268 min read

GDPR and Data Protection in Due Diligence: What Acquirers Inherit

GDPR due diligence helps acquirers understand the data protection obligations, breach history and operational controls they inherit with a target company.

GDPRData Protection
Read Insight
16 July 20269 min read

Open Source Licence Compliance in M&A: The Risk Hiding in the Dependency Tree

Open source due diligence helps acquirers test licence obligations, dependency visibility, SBOM quality and code provenance before IP risk affects deal value.

Open SourceIntellectual Property
Read Insight
15 July 20269 min read

Source Code Review in Due Diligence: What Actually Gets Assessed

Source code due diligence tests whether the codebase can support the investment case, from maintainability and tests to security patterns and dependency health.

Technical Due DiligenceArchitecture
Read Insight
14 July 20268 min read

Assessing Product-Market Fit in Due Diligence: Beyond the Growth Story

Product-market fit due diligence tests whether retention, engagement, customer pull and differentiation evidence support the growth story behind a deal.

Product-Market FitProduct Due Diligence
Read Insight
13 July 20268 min read

How Long Does Technical Due Diligence Take? Timelines by Deal Size

Technical due diligence usually takes 1-8 weeks, depending on deal size, evidence readiness, access and how much confidence investors need before signing.

Technical Due DiligenceDeal Teams
Read Insight