Where it holds, where it doesn’t
There is a persistent version of the Wire Arc Additive Manufacturing (WAAM) narrative that centres on efficiency gains: less material wasted, fewer process steps, shorter lead times, and a more direct route from design to part. These claims are not incorrect. Under specific conditions, the process can deliver precisely those advantages, and in some cases it does so in ways that are difficult to replicate with conventional manufacturing. The difficulty is not that the narrative is wrong, but that it is incomplete. For example, sometimes it describes outcomes without fully accounting for the path required to reach them.
In practice, the business case does not begin with the first part that looks acceptable. It begins much earlier, with the effort required to make that part possible in a repeatable way. This distinction is easy to overlook when the process is framed at the level of capability, but it becomes unavoidable when it is framed at the level of use. The question is not simply whether a part can be produced, but what must be invested for it to be produced consistently, within tolerance, and under the constraints of an industrial environment. That investment is not a side consideration. It is the dominant term.
The unit of comparison
Most economic discussions of WAAM are structured around a comparison between a part produced additively and the same part produced through a conventional route, typically forging followed by machining. The comparison is framed in terms of material usage, cycle time, and nominal cost, and it often produces a favourable result for the additive route, particularly for large components with high buy-to-fly ratios. This framing is intuitive and, at a surface level, useful.
What it excludes is everything that happens before the comparison becomes valid. Process parameters need to be developed and stabilised, build strategies need to be defined and refined, distortion needs to be understood and managed, and material behaviour needs to be characterised and validated. These activities are not optional, and they are not marginal. They determine whether the additive route can be considered at all. Without them, the comparison does not exist in practice, even if it appears to exist in theory.
The implication is that the relevant unit of comparison is not the part, but the programme that produces it. One pathway relies on established processes whose behaviour is well understood and whose costs are predictable. The other requires building that understanding as part of the process itself, with time, capital, and uncertainty embedded from the outset. The difference is not incremental. It turns a cost comparison into an investment decision.
The weight of non-recurring effort
The effort required to industrialise WAAM is often acknowledged, but it is rarely placed at the centre of the business case. It includes the full sequence of work needed to transform a demonstrable capability into a reliable process: parameter development across materials and geometries, iterative builds, destructive and non-destructive testing, validation of properties, establishment of inspection strategies, and the generation of data required for qualification and certification. Each of these steps carries cost, and more importantly, they interact in ways that are not always predictable.
Progress is rarely linear. Certain aspects stabilise quickly, while others require repeated cycles of adjustment and validation, particularly when the process is extended to new geometries, new materials, new operating conditions. Improvements in one area can expose limitations in another, and the system reveals its behaviour gradually rather than all at once. This is not inefficiency. It is how the process is understood.
A part does not meaningfully exist at the point of deposition alone. It becomes real in an industrial sense only when it can be trusted to meet requirements, not once, but repeatedly, and under conditions that extend beyond the specific circumstances in which it was first produced. That transition from physical artefact to reliable outcome is where most of the effort sits, and where the cost of industrialisation accumulates.
Capability, robustness, and the gap between them
It is often assumed that once a part can be produced, the primary challenge has been addressed, and that what follows is a matter of scaling or optimisation. In practice, the gap between capability and robustness is substantial. A system may produce acceptable results under controlled conditions, on a specific geometry, with known materials and experienced operators. Extending that performance to different geometries, longer builds, or industrial environments introduces variability that is not always manageable within the same framework.
Robustness is not a property that emerges automatically from capability. It requires the process to behave consistently across variation, and to do so without relying on continuous intervention or implicit knowledge. This is where differences between systems become apparent. Hardware may look similar, and baseline performance may appear comparable, but behaviour diverges when the process is pushed beyond the conditions under which it was first stabilised.
In practice, the distinction only becomes visible when the system is required to operate under constraint, whether that constraint is geometric complexity, extended build duration, or the need for repeatability across multiple parts. It is under these conditions that the limits of process control are exposed, and where what initially appeared equivalent begins to separate in a way that is difficult to ignore.
When the decision framework changes
In the early stages of a WAAM programme, decisions are often made within a context that tolerates uncertainty. Projects are typically driven by research or innovation budgets, where the objective is to explore what is possible and to establish feasibility. Under these conditions, variability is expected, and progress is measured in terms of what can be achieved rather than how consistently it can be delivered.
This changes as the process moves closer to industrial use. Responsibility shifts toward operations, finance, and supply chain functions, where the emphasis is on predictability, repeatability, and risk management. The same process is now evaluated against different criteria, and the tolerance for uncertainty decreases. What was previously acceptable becomes a liability, and the burden of proof increases accordingly.
At this stage, the underlying technology has not fundamentally changed, but the framework within which it is assessed has. The transition is not driven by a new technical limitation, but by a shift in how risk, cost, and reliability are weighted in decision-making. The process is the same; the expectations are not.
Pricing, context, and perceived value
The variability in how WAAM systems are priced reflects this shift in evaluation. Systems that appear similar at the level of hardware can command significantly different prices, and this variation cannot be explained solely by differences in configuration. It is shaped by the context in which the decision is made and by how value is perceived within that context.
In cost-driven environments, WAAM is evaluated as a substitute for established processes, and it is benchmarked against manufacturing routes that have been optimised over decades, and whose development and industrialisation costs have been sunk also for decades. In these settings, margins are understood, failure modes are known, and supply chains are stable. Price sensitivity is high, and non-recurring effort weighs heavily on the decision. The additive route must justify itself against a baseline that is both efficient and predictable.
In other environments, the logic is different. When availability, lead time, or strategic capability dominate over cost efficiency, the same process is evaluated in terms of outcome rather than optimisation. Repair of critical assets, defence applications, and scenarios where supply chains are constrained fall into this category. Here, the cost of not having a part can exceed the cost of making it, and the willingness to invest reflects that shift.
The variation in pricing behaviour is therefore not driven by intrinsic differences between customers, but by the context in which decisions are made. What appears as inconsistency at the surface level becomes more coherent once the underlying constraint is identified, and the value of the solution is assessed in relation to that constraint rather than in isolation.
What is being purchased
This helps explain why customers are often willing to pay a multiple of the cost of a conventional robotic welding system for solutions that, at a surface level, appear comparable. The hardware is only one layer of the offering. The value is attributed to the ability to deliver a result: to produce a part that meets requirements, to do so with a degree of confidence, and to reduce uncertainty in the process.
In this sense, WAAM systems are not purchased solely as machines. They are purchased as a means of changing what is possible within a given operational context. A large build volume does not guarantee that a large part can be produced reliably, and a high deposition rate does not guarantee productivity. The system creates potential, but the value lies in the extent to which that potential can be realised in practice.
What is being acquired is therefore not only physical capability, but a shift in constraint. The system is a vehicle through which limitations that were previously fixed can be moved or redefined, and the economic value is tied to how effectively that shift can be achieved and sustained over time.
Capital, time, and industrialisation
The scale of effort required to industrialise WAAM is often discussed qualitatively, but the order of magnitude becomes clearer when viewed through publicly available data. The case of Norsk Titanium, a listed company with plenty of publicly available data, provides a useful reference point. Over more than a decade, the company has raised and deployed capital that, in aggregate, approaches the high hundreds of millions of US dollars when considering equity rounds, debt, and associated programme expenditure. The outcome is technically significant, but narrow in scope: a limited number of qualified aerospace components have reached production relative to the scale of investment required to achieve certification.
The exact figure is less important than what it represents. Whether the total capital deployed is closer to $200m or $400m (probably $500m?), the implication does not change materially. The threshold to move from early capability to certified, flying parts is high enough to fundamentally shape the economics of the process. It is not a matter of scaling a machine or refining a parameter set. It is the development, validation, and documentation of an entire process chain to the standard required by certification authorities, with each step contributing to cumulative cost and timeline.
A similar dynamic can be observed, at a different scale and in different markets, in companies such as AML3D, where revenue generation coexists with continued capital deployment to expand capability, stabilise processes, and support customer adoption. The gap between revenue and cash consumption is not an anomaly. It reflects the cost of turning technical feasibility into industrial practice, where process stabilisation, qualification, and market development proceed in parallel rather than sequentially.
At this level of capital intensity, the economic logic becomes explicit. The initial investment must be absorbed by subsequent activity that is both sufficiently scaled and sufficiently valuable to generate acceptable returns for the firms’ shareholders. If that scaling does not occur, or if the value captured is diluted across too many participants, the underlying economics become difficult to sustain, with shareholders value progressively eroded.
The supplier-side constraint
Indeed, the business case for WAAM is often analysed from the perspective of the end user, yet the same dynamics apply, in a different form, to the companies that build and supply the systems. The accessibility of the technology, which enables entry at the system level, also creates a competitive environment in which differentiation is difficult to sustain and pricing is subject to pressure. Hardware components are largely sourced from established OEMs, integration approaches converge over time, and the visible elements of the system become comparable across suppliers.
This creates a structural tension. On one hand, suppliers need to invest in process development, application engineering, and customer support in order to deliver credible outcomes. On the other, the market often evaluates their offering at the level of hardware, where comparability is highest and pricing pressure is strongest. The elements that require the most investment are the least visible, and therefore the hardest to monetise directly.
The result is a compression between cost structure and revenue potential. Multiple entrants pursue similar opportunities, often targeting overlapping applications, while the total addressable market for industrially viable WAAM remains limited by the very constraints described earlier in this series. In such an environment, not all business models can be sustained at the same time, particularly when capital has been deployed on the expectation of rapid scaling.
The economic challenge is therefore not confined to adoption. It extends directly to supply. A market characterised by accessible entry, limited visible differentiation, and high underlying development cost does not naturally support a large number of independent providers, each carrying its own cost of capital and development burden. Some level of consolidation, specialisation, or failure is not an outcome to be avoided. It is a structural consequence.
Organisational constraints
WAAM adoption takes place within industries that are structured around risk, certification, and long-established supply chains. Aerospace, defence, and energy operate under conditions where failure carries significant consequences, and where changes to manufacturing processes are introduced cautiously. This context shapes not only how technologies are evaluated, but how they are implemented over time.
Programmes unfold over extended periods, often longer than the cycles through which organisations allocate resources and make decisions. Industrialisation requires continuity, while organisations operate in phases. This creates a dependency between technical progress and organisational stability, where the success of a programme depends not only on the maturity of the process, but on the ability to sustain effort across time.
In practice, the presence of technical capability does not guarantee adoption. It must be supported by structures that allow it to be developed, validated, and integrated in a consistent manner. Where that support is fragmented or intermittent, progress slows, regardless of the underlying potential of the technology.
When WAAM makes sense
Taken together, these elements explain why WAAM behaves differently across applications. It is effective where it addresses a constraint that is both significant and difficult to resolve through conventional means, and where the value created is sufficient to absorb the cost of industrialisation. It struggles where it is positioned as a marginal improvement, particularly in environments where cost and predictability dominate decision-making.
The same system can therefore be compelling in one context and unconvincing in another, without any change in its underlying capability. What changes is the economic and operational frame within which it is evaluated. This is not a contradiction, but a reflection of how value is defined in different settings, and how the same set of characteristics can be interpreted in different ways depending on the constraints that are being addressed.
The implication is that the business case cannot be generalised across applications. It emerges from the interaction between the process and its context, and it holds only where that interaction produces a sufficiently strong alignment between cost, risk, and benefit.
Closing
The relevant question for WAAM is not whether the process works, but under what conditions it justifies the full cost of making it work. That cost includes not only the system itself, but the development effort required to stabilise it, the organisational commitment needed to integrate it, and the risk associated with adopting it in environments where reliability is critical. These factors are not secondary. They define the economics of the technology once it moves beyond demonstration.
This applies not only to users of the technology, but to those attempting to build a business around supplying it.
Seen in this way, the variability in outcomes across the field is not surprising. The same process can deliver clear value in one application and fail to justify itself in another, depending on how the balance between cost, risk, and benefit is resolved. Treating WAAM as though its value should be self-evident once feasibility has been established leads to expectations that are difficult to meet. Understanding it as a process whose value depends on context provides a more reliable basis for decision-making.
The final article turns to what follows from this. If the business case is conditional, the question becomes how the technology evolves as those conditions change, where durable value is likely to emerge, and what kind of focus is required for WAAM to move from broad promise to selective, sustained industrial relevance.
Leave a Reply