There seems to be some misunderstanding about backlog.

Backlog does not equate to "backed up". It is not a delay. To conflate the two is incorrect.

Backlog is a measurement of projects won and not yet completed. More importantly (and specifically) it is revenue known to be on the horizon but not yet booked and accounted for.  It is a way to show future actual revenue outside of formal financial statements.

In no way is backlog a negative.

To that point, there is no number to which a client, potential client, or PyroGenesis would assess and say, whoa, backlog is too high, let's not do that order. Different projects are constantly in different phases, plus PYR's doubling of manufacturing space and its backup sub-contracting network are all there for infinite support.

As to the specific example, mass-produced cars on a lot are not highly unique, patented, multi-million dollar technology solutions that go through many months of bidding, assessment, business-case development, facility review, and so forth. That's a false equivalency. For the most part these are highly customized order where the vendor is chosen because their custom solution is a fit to your custom need.

Finally, there are no clients calling out for faster turnaround of PYR projects. In virtually all cases, PYR can make a product far faster than a client is ready to receive it. In fact, most projects are so large both physically and financially that the clients require the long-lead times to prep their own facilities and teams.

------