Crusoe ended its $1.25 billion Boom turbine partnership.1
That is the factual anchor. The fictional facility below is ours. It has a magnificent rendering and a finance director who would prefer a less magnificent range of dependencies.
The problem with a beautiful infrastructure story is that every component can make the others sound more inevitable. The equipment enables the facility. The facility enables the customer. The customer justifies the equipment. By the end of the presentation, nobody remembers which commitment still needs to become a working machine.
Procurement is permitted to have an opinion
Our imaginary developer needs electricity at a specific site. A proposed supplier offers an ingenious system. Another supplier offers a less interesting system with a different delivery history. The developer has to compare them.
The interesting supplier deserves an honest assessment. Novel equipment can improve the available options. The developer also needs to know how it will be installed, maintained, and supported; what a delay does to the rest of the project; and which promises survive a change in circumstances.
Those questions are about buying equipment. They are not a referendum on whether the engineer is visionary.
A procurement team can make a dull choice for good reasons. It can also make a bad choice out of habit. The work is to distinguish them. We cannot do that from the dramatic quality of the rendering.
Our fictional investor has suggested that the procurement team's spreadsheet may be insufficiently appreciative of the future. The procurement team has suggested adding the future to the approved-vendor list once it supplies references.
A partnership has two businesses inside it
Suppose the fictional supplier wants an initial customer to help establish a new product. Suppose the developer wants a dependable input for a facility whose own customers have deadlines.
Those interests can align. They can also separate without either business becoming fraudulent or the underlying engineering becoming worthless.
The supplier may tolerate uncertainty while improving a prototype. The buyer may need confidence before making a commitment that cannot easily be reversed. A promising partnership therefore needs more than mutual enthusiasm. It needs a way to handle the moment when one participant's learning schedule becomes the other's construction delay.
A contract can allocate some of that risk. It cannot abolish the possibility that the two companies eventually need different things.
The replacement part is not a narrative failure
When our imaginary developer changes suppliers, its earlier presentation looks less tidy. The site might still become a useful facility. The rejected equipment might still find an appropriate customer. Neither outcome has to preserve the original announcement.
This is an ordinary feature of execution that becomes embarrassing only after the announcement has been promoted into destiny.
The relevant questions concern what changed and what it means for the project: cost, timing, reliability, and the commitments that remain. The company should explain those consequences. The audience should resist filling the gaps with either triumph or apocalypse.
The finance director updates the model. The engineer revises the design. The communications team searches for a sentence in which changing the plan was always part of the plan.
Fortunately, the facility can operate without that sentence. It cannot operate without the equipment.