ImmersaEngineering / Technology development
Independent review of what will survive scale-up.
Advancing a technical concept to operating scale: what to prove next, the cost of establishing it, and which current assumptions will not hold at production scale. Prepared for technology owners, and for boards and investors assessing them.
What is reviewed
Eighteen areas, from experiment to commercial deployment.
The questions change at every stage. A programme that is well run at bench scale can still be unfundable, and a technology that works can still be uneconomic — both are worth knowing before the next tranche is committed.
Readiness and programme
Where the technology genuinely sits, and whether the plan to advance it is designed to answer the right question next.
- Technology readiness evaluation against a defined application and relevant environment, with the readiness framework named and adapted where it originates in another sector
- Research and development programme planning and prioritisation
- Experimental programme design and test-rig specification
- Innovation portfolio structure and stage-gate governance
Scale-up and evidence
Whether the data supports the claim, and whether the mechanisms that dominate at bench scale are the ones that will dominate in a commercial unit.
- Scale-up strategy — laboratory to pilot to demonstration to commercial
- Proof-of-concept and pilot data interpretation and validation
- Independent review of technical claims and performance data
- Manufacturing bottleneck, throughput and capacity analysis
Commercial case
What it costs to make, what it is worth, and what a buyer or an acquirer will test first.
- Techno-economic assessment and cost-of-production modelling
- Commercialisation planning and route-to-market assessment
- Technical and technology due diligence for boards, investors and acquirers
- Commercial due diligence — unit economics, cost build-up and the operating model behind the technology
- Build-versus-buy and technology selection assessments
- IP landscape orientation, disclosure strategy and technical issue-spotting to brief a patent attorney — not a freedom-to-operate or patentability opinion, which is legal work
Capability
Whether the organisation can actually execute the programme it has written, whether it can measure its own product to the standard the market requires, and whether its modelling can be relied on.
- R&D organisation design, capability building and laboratory set-up
- Analytical method and instrumentation strategy
- Computational capability review — simulation strategy, stochastic methods including Monte Carlo, and whether input distributions, dependence between inputs and model form justify the confidence claimed
- Machine-learning and data-driven models — data provenance, leakage, train and test separation, drift and out-of-distribution behaviour, and the distinction between prediction and causal process understanding
How it is delivered
For technology owners, and for the people funding them.
The same review is read very differently by a development director and by an investment committee. The deliverable states the technical position plainly enough for both.
Technical due diligence
Whether the technology is proven, whether claimed performance is achievable at scale, whether the capital estimate is credible, and what belongs on the risk register that is not on it yet.
One to three weeks, timed to a transaction or a funding decision.
Scale-up strategy
Laboratory to pilot to production. What to build, what to procure, what to prove next, and which current assumptions will not hold at operating scale.
A workshop and a written position.
Typical findings
What a review of this kind turns up.
Illustrative and non-attributable. Each is invented; no engagement lies behind any of them.
- A technology readiness level (TRL) 6 claim resting on a rig that shared no scaling parameter with the commercial unit.The bench unit was heat-transfer limited and the commercial design mass-transfer limited. The data was sound and did not support the claim made from it.
- A cost-of-production model with no allowance for off-specification product.First-pass yield at pilot scale was 71%. The model assumed 100%, and the difference exceeded the projected margin.
- A pilot programme designed to confirm the concept rather than to break it.Every run had been conducted inside the operating window. Nothing in the dataset established where the window actually ended.
- An analytical method that could not resolve the specification it was measuring against.The product specification was tighter than the method's stated reproducibility, so conformance could not be demonstrated at any yield.
Invented for illustration. Nothing arising from a real engagement is reused, retold or cited as a credential.
See the deliverable
Read one before you commission one.
The specimen is a process design review rather than a technology assessment, so the subject differs from the work on this page. The reasoning standard is the same: every assumption stated so it can be tested, findings ranked by consequence, and the limits of the conclusion written down.
It carries the assumptions relied on, a sensitivity table, the items examined and found sound alongside those that were not, the residual risk that remains after the recommended actions, and a passage setting out where the conclusion could be wrong. Every page is marked SPECIMEN; the facility, the client and the findings are invented.
Have a technology or a programme reviewed.
A short description of the problem, the document set or the decision is enough to confirm suitability, propose a structure and give an indicative cost. A mutual non-disclosure agreement is executed before technical detail is exchanged.
Discuss a requirement