The Buyer Believes Your Technology. They Still Have to Operate It.

Industrial adoption rests on two judgements. One is whether the technology works. The other is whether the company can live with it, through installation, integration, production interruptions, staff time, liabilities and the chance of a rollout that underperforms.

Operations, engineering and risk teams raise the second set of questions because their approval depends on the answers. A founder who has the answers written down before the questions arrive gives those teams a way to say yes.

This guide covers the risk the buyer carries once the technology is on site. The account a lender or investor needs for a first commercial project, with six evidence states, is in How to Present FOAK Risk Without Pretending the Risk Is Gone.

Walk the deployment phase by phase

Operating risk changes as the deployment moves. Set out the phases first, then list what the buyer's site carries in each.

Phase	What the buyer's site carries	What operations will ask
Preparation	Site survey, permits, utilities, data access	What do we have to provide before you arrive?
Installation and commissioning	A production stop, contractors on site, safety inductions	How long is the line down, and who sets the date?
Ramp-up	Operator training, parallel running with the current process, acceptance tests	When does the current process switch off, and who signs that off?
Steady operation	Maintenance, spares, consumables, service visits, data	Who fixes a fault out of hours, and how fast?
Underperformance or exit	Fallback to the current process, removal, remediation	What happens if it misses the target, and who pays?

The phases are our working frame. Rename them to match the buyer's own project stages, and add any phase their process has that this one leaves out.

Write one row for each risk

Record seven things for each risk.

Keep technical, operational, commercial, regulatory and counterparty risks in separate groups. A new process may hit its target yield in a controlled trial and still need a production shutdown to install. Those are two risks. Trial data answers the first. Scheduling, engineering plans and a contract clause answer the second, and a slide of laboratory results leaves it open.

Name who carries what remains

“Risk mitigated by supplier support” reads well until a stoppage. Ask who provides the support, who pays, how fast they respond, which performance obligations are in the contract and who accepts the exposure that remains.

Some risks are shared. A startup can deliver equipment to specification while the buyer trains operators and schedules the integration. Write a responsibility matrix that covers both sides. The rows below show the format, and your own rows come from the register.

Task	Supplier	Buyer	Third party
Equipment built and delivered to specification	Owns	Inspects and accepts on delivery	Carrier, if used
Site utilities and connections	Specifies	Provides	Installer, if contracted
Operator training	Delivers	Releases staff time	Training provider, if used
Production schedule during installation	Advises	Decides	Host site contractors
Spares and service response	Holds stock and meets the agreed response time	Reports faults	Service partner, if used

Put the buyer's share of the work on the page early. Once operations can see how many hours and which people the deployment needs, they can assemble the internal team to carry it. Work the buyer first meets after signature lands on people who had no part in agreeing to it.

Run the bad-day test

Pick the three failures most likely to reach the buyer's production. For each one, answer five questions in order.

If an answer reads “the supplier will support”, the row is still open. We give this test its own step because the bad day is the part of a deployment that operations will have to explain to their own management.

Label what each mitigation rests on

A mitigation is as strong as the evidence behind it. Mark each one by what it rests on, using the labels already in your pilot record. From Pilot to Purchase uses observed, inferred, unresolved and next proof. For a first commercial project, the six evidence states in the FOAK risk guide go further.

The labels keep each claim at its stage. A throughput model describes expected performance. A trial on one feedstock covers that feedstock. A technical partner's interest records interest, and a letter of intent records intent. Each can still support the opportunity, and each tells the buyer what the next commitment has to prove. When a claim moves to a new stage, update the register so last quarter's assumption stays labelled as an assumption.

Size the next commitment to the open risks

Where a full purchase is premature, propose the next bounded decision and name the risk it is designed to resolve. It might be a paid demonstration, a qualification run, a design study, an engineering package, conditional supply terms or a reserved production slot.

Shrinking the ask until nobody has to decide is the opposite mistake. A useful stage creates new evidence, names a responsible party and changes what can be approved next.

Carry the top risks into the approval page

Procurement reads the register for contract and supplier readiness. Operations reads it for the installation sequence and service terms. Finance reads it for total cost and the working capital the rollout ties up. Keep one register and let each function read the rows it owns.

The five risks with the largest operating consequence, with their owners and the next proof, belong in the Deployment plan and Economics and risk fields of the one-page internal approval case. The full register sits behind that page as the source the champion can send. When the owners have to become contract terms, the commercial proposal writes each one in as an obligation.

If the risks are understood, owned and staged and the project still cannot move, the cause may sit in economics, authority or capacity. The Belief Diagnosis starts there and finds where the decision stopped, because the next move may be an engineering, financing or procurement change that a new narrative would leave in place.

Questions people ask

How can customer case studies reduce a buyer's perceived risk?

A credible reference shows the customer's context, the alternative they compared, how the implementation went and the outcome, with its limits. Another buyer can then estimate their own risk without assuming the result transfers unchanged. Permission, comparability and specific measurements carry more weight than an enthusiastic testimonial.

How do we explain the total cost of adopting a new industrial technology?

Compare it with the current process, covering equipment, downtime, training, qualification, supply continuity, energy, waste, service and financing where they apply. State the assumptions and the ranges. Purchase price alone can mislead in either direction, and a price projected at future scale is a different offer from the one available today.

What does a deployment-readiness case look like for climate hardware?

It states which system has run, under what conditions, at what scale and how repeatably. It names the approvals and partners still required and what the next deployment will test. A rendered factory image shows intent. Put progress and uncertainty side by side so operations can weigh both.

Sources and further reading

• How to Present FOAK Risk Without Pretending the Risk Is Gone, Brighter Future, 2026
• From Pilot to Purchase. The Internal Approval Pack, Brighter Future, 2026
• Why Successful Climate Tech Pilots Do Not Always Become Purchases, Brighter Future, 2026
• I Believe You. I Cannot Sign This., Brighter Future, 2026
• The Belief Diagnosis, Brighter Future