What is Technical Due Diligence?

Technical Due Diligence evaluates platform architecture, infrastructure, security posture, and engineering capability to identify the risks involved in owning and scaling a technology platform.

What is Product Due Diligence?

Product Due Diligence evaluates product strategy, architecture alignment, roadmap feasibility, and delivery capability to determine whether the product organisation can support future growth.

How do Technical Due Diligence and Product Due Diligence work together?

Technical Due Diligence explains platform, infrastructure, security, and engineering risk. Product Due Diligence explains product strategy, roadmap feasibility, and delivery execution risk. Together they provide a fuller view of technology-driven businesses.

Does FoundationState offer different engagement sizes?

Yes. Technical Due Diligence is available in Small, Medium, and Large tiers depending on transaction complexity. Product Due Diligence is delivered as a single tailored engagement scoped around the target business and typically completes within 1-3 weeks.

What does a due diligence report include?

Outputs vary by assessment, but typically include a diligence report, executive summary, prioritised findings, roadmap or remediation recommendations, and investor-ready commentary on the issues most likely to affect value and execution.

Independent product & technology advice

Clearer decisions about your product and technology.

Understand what is working, what is holding progress back and where to act next. Independent reviews for business leaders; technical and product due diligence for investors and acquirers.

Arrange a discovery conversation

Free initial discovery · 1–2 hours · Bespoke scope

For business leaders: product & technology reviews →

For investors: technical due diligence · product due diligence

Inside an independent review

Product evidence

Roadmap & demand

E05 · Product plans

Technology evidence

Recovery runbook

E03 · Recovery evidence

FoundationState REVIEW

Finding F02 · E01 / E03

Keep the platform.
Prove the recovery.

Completed backups do not demonstrate recovery of the whole service.

Evidence gapRecovery unproven

Prioritised action

A02 · Prove service recovery

Agree recovery objectives
Exercise with a second operator
Record timings and reconciliation

Illustrated from the public worked report

Start with what can be demonstrated

Roadmaps, architecture, delivery records and customer signals give the review its foundation.

Relevant experience

Real businesses. Practical questions.

Explore all case studies →

Fractional CTO

myHappymind

Technical due diligence focused on security posture, hosting resilience, scale risk, and the remediation priorities needed to support growth with confidence.

Technical Due Diligence

View Case Study

Product Consultant

River Consultancy Group

Product due diligence focused on roadmap strategy, tooling choices, discovery, GTM activity, and the operating discipline needed to turn an offer into a scalable product.

Product Due Diligence

View Case Study

Recognise the situation?

When progress is harder than it should be

What is really slowing us down?

Understand whether priorities, capacity, ways of working or platform constraints are holding progress back.

A useful outputA view of delivery constraints, competing demand and the next decisions needed.

Scope is agreed after discovery; this explorer does not prescribe a package.

Explore the scope of a business review →

Page 5 of the public worked report: architecture and resilience, observation, commercial implication and recommended treatment.

See what the work produces

A finding is useful when you can act on it

Explore one excerpt from our public 14-page worked report: how evidence connects to a business decision.

Evidence

The backup log records completed jobs. The runbook covers the database; service reconstruction has not been demonstrated.

Download the worked examplePDF · 14 pages

Public and ungated. The worked example illustrates the reporting approach; it is not a client assessment.

How to read the report

A clear way to begin

Your question shapes the engagement

01
Discovery
Free 1–2 hour conversation about your business, pain points and decisions ahead.
02
Bespoke proposal
Agree the evidence, scope, deliverables, timing and quote before starting.
03
Independent review
Connect interviews and evidence across the product and technology questions that matter.
04
Readout & next steps
Discuss findings, ownership and practical priorities. Agree further advice where useful.

Ryan Musselwhite, FoundationState founder

Human judgement, grounded in evidence

Work directly with Ryan Musselwhite

Hands-on product and technology leadership, combined with independent transaction and business reviews. Findings explained in business terms, with practical next steps.

Meet the founder →

FAQ

Frequently Asked Questions

Get Started

What decision do you need to make?

Bring your business questions to a free discovery session. We will agree the review that would be useful.

Discuss your priorities