01
02
03
04Sections
FOAK has become a convenient label for projects that feel large, difficult or commercially important. Used loosely, it hides more than it explains. The useful version of the term identifies exactly which part of the asset, process or commercial configuration is first and which parts already have a reference class.
Before putting “first of a kind” on a deck, lender memo or project page, establish these eight things.
1. Define what is actually first
A project can be first because of the core process, the scale, the feedstock, the site integration, the product specification, the equipment configuration or the commercial arrangement. Those are different kinds of first.
Name the novelty precisely. “First commercial deployment of this process at this throughput with this feedstock” gives a reviewer something to test. “FOAK technology” leaves the whole project inside one undifferentiated risk label. Design can also shrink the novel part, and our FOAK guide quotes one investor's preference for scaling by connecting smaller units over building larger plants.
2. State what has already run and under which conditions
The previous demonstration needs a scale, duration and operating context. A pilot that ran for a thousand hours on one feedstock tells a reviewer about uptime at that scale, on that feedstock and in that operating range, and the evidence stops at those limits. Performance at ten times the throughput with a different feedstock and duty cycle sits outside them.
Write down the largest relevant system already operated, for how long, under which conditions and which elements of the new project fall outside that envelope.
3. Separate technical readiness from commercial readiness
A technology-readiness score does not tell a buyer whether supply is qualified, a lender whether the contracts support debt, or a host whether permits and integration are ready.
Keep the technical record, customer evidence, permitting, site work, supply, offtake and financing status visible as separate conditions. The test is that every TRL in the materials carries the status of supply, offtake, permits and financing beside it. A blank field counts as a fail.
4. Draw the boundary around the asset
FOAK financing is attached to a project as well as to a company. The reviewer needs to know what is being built, where the boundary sits, which infrastructure is included, what belongs to the host and which costs sit outside the project company.
The test is one page. Draw the boundary on it, place each cost inside or outside the project company, and name the host's share. This matters most when a venture deck is being reused for project capital, because the company can be compelling while the asset is still undefined.
5. Describe demand at the level the contract supports
Buyer interest, a letter of intent, a qualification programme, a conditional offtake and a binding purchase obligation create different evidence. They should not be grouped under “commercial traction”.
List what has actually been signed, what conditions remain, the period and volume where those details are public or shareable, and the uncertainty the commitment changes. Demand evidence should be precise enough that a capital provider can understand what it can and cannot underwrite.
6. Map who is waiting for whom
FOAK projects often contain a circular dependency. The buyer wants confidence in supply, the investor wants evidence of demand, the host wants a financing plan and the lender wants protections that depend on several of the others.
Put the parties in a dependency map and add a “waiting for” field. The order of commitments can matter more than another general pitch to everyone at once.
7. Name the non-technical conditions that can stop the project
Permitting, grid access, land rights, construction capacity, feedstock, product qualification, insurance and the financing timetable can all become the controlling constraint even when the core process works.
The project story should show which of these conditions are closed, which have a defined pathway and which remain open. A FOAK case becomes more credible when its unknowns are visible enough to manage.
8. Decide what project one must prove for project two
The first commercial project is also an evidence engine. If commissioning time, actual yield, maintenance, energy use, unit cost and customer performance are not logged in a form future capital can use, project two can be priced as another first-of-a-kind asset.
Define the record before construction. A FOAK case that names what is first today and what evidence will exist once the project has operated has also written the opening page of project two's case.
Sources and further reading
- What Is FOAK in Climate Tech?
- Why Are FOAK Climate Projects Hard to Finance?
- The First Plant Has More Than One Customer
- From FOAK to NOAK
- What Is an Offtake Agreement and Why Does It Matter for FOAK Climate Tech?
- Is a FOAK Project Fundable or Financeable?
- From Pilot Evidence to Project Evidence: What Changes at FOAK
- How to Present FOAK Risk Without Pretending the Risk Is Gone
Tell us what needs to move.
Bring the brief if it is clear. If it is unclear, tell us where the work is stuck.
Bring us the problem