Even after a joint demonstration, a customer who calls the result ‘meaningful’ may not immediately sign the next contract. The reason to research together is not the same as the reason to pay for adoption. In research, confirming a new possibility can itself be an outcome; buyers, however, need to know what decision the result will allow them to make.
A paid climate-tech PoC can be designed as a contract to test whether a technology can be adopted within a limited period and scope. What the customer pays for need not be a positive reduction result. Measuring and analyzing to a pre-agreed standard so the customer can choose to expand, revise, or stop can itself be the product.
Start by narrowing the decision the customer must make
A livestock-methane PoC needs a more specific question than ‘test our technology.’ The design changes depending on whether a feed-development manager wants to decide if the effect of a particular feeding condition should move to the next trial, or whether a farm wants to see if it can absorb the additional work time. The same sensor may support different deliverables.
First distinguish the person who will use the result, the person who approves the cost, and the person who operates the site. A researcher may like the report, but the contract can stall if someone else controls the purchasing budget. A proposal is stronger when, alongside the deliverables, it states who will use the material to make which decision.
Technical-demonstration success and commercial success should not be joined in a single claim. The IEA’s energy-innovation demonstration tracker likewise explains that a project successful in its first demonstration does not necessarily become a commercially successful product. It is an energy-sector example, but it shows that market validation remains after a demonstration. IEA, Races to First in Energy Innovation
Fix what will be validated before signing the contract
In a paid test, the absence of the expected effect can reveal the quality of the design. Changing the subject of analysis until the customer’s desired number appears makes it hard to create material for the next decision. The measurement period, subjects, comparison conditions, primary indicators, and exclusion criteria must be agreed before the start.
The European Food Safety Authority’s 2024 guidance on assessing feed-additive efficacy emphasizes appropriate control groups and statistical assessment. It is intended for EU feed-additive authorization applications, not a contractual standard to apply unchanged to every domestic PoC. Still, it is a useful reference for designing a test around the effect to be examined. EFSA, Guidance on the assessment of the efficacy of feed additives
For example, even if a methane-related observation falls, more information is needed if feed intake or productivity changed at the same time. A PoC designer should explain which variables sit between a change in the observation and the effect the customer wants to know. If the conditions for collecting the necessary information do not exist, it is more accurate to leave that question as one this contract cannot answer.
A test of whether technical equipment operates must also be distinguished from a test that substantiates an amount of reduction. For the former, the data-collection rate and fault-response time can be important outcomes. The latter additionally needs an emissions-calculation method and a comparison design. Selling a report that equipment worked normally as if it were proof of a reduction effect misaligns customer expectations and the delivery scope.
Accept against the agreed procedure, not attractive numbers
In a paid PoC, the first document to make concrete is the table of contents for the results report. If it is set to include the test purpose, site conditions, measurement procedure, quality checks, analytical results, limitations, and the next decision, the customer knows what it will receive. The parties should also decide whether raw data or only summary results will be delivered.
ARRIVE 2.0 for reporting animal research specifies the information needed to judge reliability and advises considering experimental design, sample size, and statistical analysis from the planning stage. It helps explain why the delivery scope should include not only numerical results but also the path by which those results were produced. ARRIVE, The ARRIVE Guidelines 2.0
Practical acceptance criteria can separate the quality of execution from the direction of the effect. Whether the agreed subjects and period were measured, reasons for missing data were recorded, and reviewable analytical material was provided are matters of execution quality. Whether a reduction effect was observed is the result. If the design was appropriate and the procedure followed, a conclusion that no effect was confirmed can still reduce the customer’s unnecessary scale-up costs.
That does not mean a customer can be asked to accept every incomplete result. The parties should decide in advance how they will address supplemental measurement, schedule changes, or fee adjustments when the promised data cannot be obtained. A good contract does not conceal the possibility of failure; it identifies who responds to each type of failure.
Agree data use and disclosure scope first
Flexible cooperation between research teams can be an advantage in a joint demonstration. But using customer data from a paid PoC in later sales materials or model training requires a separate alignment of expectations. Paying measurement costs alone does not establish that one side owns or may reuse all data.
For contract discussions, it is practical to treat raw data, cleaned data, and analytical results separately. Document the range the customer may download, the range the service provider retains, and the range joint researchers may access. If there is a plan to use data to improve a model, its purpose and subject should be explained separately as well.
External disclosure is another matter. The scope for using a farm name, site photographs, a customer logo, or result graphs in promotion should be distinguished from access required to perform the work. Not treating payment or permission to access the site as consent to public disclosure is the starting point for preserving the relationship. These are practical issues to review for each individual contract.
The next contract may be a larger test or an operating service
If the post-PoC option is set automatically as an annual subscription, the customer’s needs may be missed. Where the effect is unclear, a redesigned trial is needed; where technical performance is confirmed but the operational burden is high, the installation and maintenance approach should change. Only customers whose conditions fit should move to ongoing monitoring or regular analysis.
Providers must look at actual delivery costs alongside revenue. Recording time spent on installation visits, calibration, analysis, and customer explanation shows what can be sustained in repeat sales. Adding every request free of charge in the first contract makes it difficult to set the price and delivery standard for the next customer.
Moving from a joint demonstration to a paid PoC is a broader change than adding an amount to an agreement. It connects the customer’s question, the answerable scope and deliverables, data rights, and the decision after the engagement ends. The clearer that connection is, the better the customer understands what it is buying and the more readily the provider can build a repeatable service. A paid PoC can help test customers’ willingness to pay and delivery costs together, enabling a repeatable proposal to emerge earlier. But becoming paid does not itself guarantee market leadership.