For investors and acquisition teams
See what has been demonstrated. Know what still has to work.
A successful demonstration is one piece of evidence. Technical due diligence examines the conditions behind that result, the dependencies that could limit repeatability and the engineering still needed for the next stage.
01 / Key questions
Which questions could change the investment decision?
01
Is the performance representative?
Were the tests run under conditions that match the intended application, with a configuration the team can reproduce?
02
What could constrain progress?
Does the next milestone depend on an architectural change, a supplier, scarce expertise or evidence that has not yet been generated?
03
What does the roadmap require?
Which engineering activities, resources and validation steps underpin the proposed cost and schedule?
02 / Review scope
What the technical review covers
01
Claims and performance evidence
Compare product claims and specifications with test methods, results, limitations and the intended use. Identify where the evidence is strong and where a targeted check is needed.
02
Architecture and dependencies
Review the interfaces between hardware, software and controls, together with critical components, suppliers and engineering know-how. Trace dependencies that could affect reliability or scale-up.
03
Development and validation plan
Assess the technical work remaining between the current system and the stated milestone. Examine the basis for resource estimates and flag assumptions that could materially change delivery.
03 / Typical outputs
Findings for the investment decision
01
Technical assessment
A decision-focused account of demonstrated capability, material risks and open questions, with the supporting evidence identified.
02
Risk and dependency register
A prioritised view of engineering issues, their possible effect on cost and timing, and the assumptions behind that assessment.
03
Follow-up review plan
Specific information requests, questions for the engineering team and proposed checks to resolve the most consequential uncertainty.
04 / Working together
How the review is scoped
We agree the investment question, review depth and access to materials before work begins. The review can combine document analysis, discussions with the engineering team and a scoped examination of demonstrations or site activities. Conclusions distinguish observed evidence from reported claims and analytical assumptions.
What needs to be true for the technology to succeed?
Tell us about the system, the milestone and the technical questions behind your decision.
