Demonstrating that a technology works leaves a separate industrial question: can the proposed organisation repeatedly deliver the product at the required volume, cost and quality?
A successful prototype can establish that a technology is promising while leaving the production plan largely unproven. The demonstration may depend on specialist attention, limited material or a process that has not been repeated at the proposed volume. Those conditions do not invalidate the technical result. They define a different set of questions for the next investment.
Technology readiness and manufacturing readiness help separate those questions. One concerns the maturity of a technology for its proposed use; the other examines the industrial ability to realise a product through a particular production arrangement. A defence startup deciding how to spend its next funding round needs both perspectives, especially when a customer begins discussing quantities and delivery dates.
GAO’s Technology Readiness Assessment Guide overview focuses on technology maturity and the evidence for integrating technology into systems. That assessment can identify development uncertainty without resolving how a supplier will produce and deliver the resulting product repeatedly.
The 2025 Manufacturing Readiness Level Deskbook examines areas including materials, process capability, quality, workforce, facilities and cost. It explicitly describes itself as best practice rather than a DoD requirement. Its value for this discussion is the breadth of the industrial questions, not an automatic certification or universal contractual threshold.
An illustrative company might demonstrate a commercial monitoring device using a carefully assembled prototype. The next decision could concern a pilot production run. Funding another technical demonstration and funding the establishment of a repeatable assembly and acceptance route would produce different evidence, even if both activities contribute to the same product programme.
Manufacturing readiness belongs to a proposed production arrangement. Identify which organisation performs the work, which suppliers provide the relevant inputs and which activities remain with the product company. A strong internal prototype workshop does not establish the capability of a future contract manufacturer, and an experienced manufacturer does not automatically remove product-specific transfer work.
For the monitoring-device example, the startup may plan to retain final configuration and acceptance while outsourcing assembly. Its industrial plan must cover both organisations and the handover between them. Evidence about the subcontractor’s general facilities is relevant but incomplete if the customer-controlled release step remains a constraint.
The commercial assessment should also identify the intended volume and product configuration. A route that supports occasional engineering units may require different resources for a sustained order. Conversely, a modest customer requirement may not justify the fixed cost of an ambitious production expansion. Readiness should be considered in relation to the actual commitment.
A manufacturing programme can be advanced in one area and immature in another. Equipment may be installed while staff are still being assessed, or material supply may be established while the accepted yield remains uncertain. A single reported level can be useful shorthand only if the underlying evidence remains accessible.
The Deskbook’s separate manufacturing threads provide a way to consider those differences. For a commercial team, the practical approach is to identify which gap constrains the next delivery decision and who owns it. There is little benefit in improving an already adequate activity while leaving the critical dependency unresolved.
This also improves investor communication. Instead of describing all remaining work as scale-up, a company can explain whether it needs to qualify a route, transfer production data, secure a constrained input or establish an acceptance process. Each task has a more assessable cost, dependency and outcome than the broad label alone.
The production plan should recognise the circumstances behind the demonstrated unit. Did senior engineers perform work that the future route expects trained production staff to handle? Was material specially selected? Were records assembled retrospectively? Such conditions can be reasonable during development, but they should be visible when forecasting repeat deliveries.
For the illustrative device, an engineer may have resolved an assembly issue through an undocumented adjustment. That intervention is useful learning. Before the task becomes repeat production, the organisation needs an approved way to reproduce the intended result and handle departures. The issue is transfer of responsibility, not criticism of experimental work.
The industrial competence guide examines this handover from another angle. A production plan needs people capable of the assigned work and sufficient supervision, rather than only a headcount target. That evidence may mature on a different schedule from the technology itself.
A pilot run should be designed around the production uncertainty it is intended to reduce. Its useful outputs can include accepted quantities, the work required to achieve them, unresolved process issues and the records needed for customer acceptance. The significance lies in what the run demonstrates about the proposed route.
The company should state how representative the run is. An unusually small quantity, a temporary production team or a different material source may limit the conclusions that transfer to later orders. Those limits do not make the activity worthless; they help define the next industrial step.
The yield and unit-cost guide explains why gross output alone is insufficient. A funding proposal should distinguish units started, units accepted and the resources consumed by rework. Otherwise a technically successful production exercise can support an overly optimistic forecast of cost or schedule.
Buying equipment is one way to address an industrial gap, but the comparison should include the complete route it enables. Installation, qualified staff, process establishment and acceptance capacity may remain necessary after the purchase. The investment case should explain which constraint is removed and which dependencies remain.
An outsourced route may avoid some initial capital expenditure while introducing transfer costs, minimum commitments or reduced control over scheduling. Neither arrangement is inherently preferable. The decision depends on demand, the product’s requirements and the evidence that the selected route can support the proposed commitment.
Working capital deserves separate treatment. A business may need to buy material and fund production before receiving customer payment. A technically mature product with a credible process can still require financing for that interval. The funding plan should distinguish expenditure that establishes capability from expenditure that supports orders through the cycle.
Industrial evidence can show that a product design needs adjustment before a larger commitment. A component choice or documentation approach that worked during development may create avoidable cost in repeat production. The plan should allow the company to evaluate such findings through its normal design and acceptance responsibilities. Treating every production difficulty as a request for more capacity can miss a simpler product change. Any revised configuration then needs the evidence appropriate to the change before earlier results are carried forward.
A useful industrial milestone names the evidence the next stage should produce. It might establish a controlled production handover, demonstrate an agreed accepted quantity or resolve the availability of a critical input. The milestone should identify its configuration, scope and dependencies, rather than promise an unexplained increase in readiness.
Where a named public programme is involved, its current rules and decision process remain decisive. A manufacturing assessment does not itself establish eligibility, a contract award or customer demand. It can make a proposal more informative by showing what the requested support will change.
The strongest transition plan therefore connects the technical result to a specific industrial route and a sequence of evidence-backed commitments. It gives founders, customers and funders a shared view of what works today, what can be delivered today and what additional work would justify the next scale of production.
The 2025 MRL Deskbook cover, scope, thread descriptions and criteria were read in the complete PDF now hosted in the current MRL website’s public storage. It explicitly presents best practice rather than a DoD requirement. GAO’s TRA guide overview supplies the technology-assessment comparison.
Suggest a correction