Feedstock is not secured. It is managed.
A recent LinkedIn post by Clément Gourrierec, CEO at Crystalchain, raised a point that deserves more attention than it usually gets. The idea is simple. Long term feedstock contracts in biochar projects are far less solid than they appear.
This matters because many projects still rely on a clean story. Feedstock is secured. Operations run smoothly. Revenues follow. It is a sequence that looks logical on paper and works well in presentations.
In practice, biomass does not behave like a fixed input waiting to be processed. It moves. It responds to demand. It shifts between uses depending on price, access, and timing. The same material that feeds a biochar plant today can be redirected tomorrow to energy generation, pellets, or other industrial uses.
As more industries compete for the same resource, stability becomes harder to claim. Contracts reflect this. They are often shorter than expected, flexible in volume, and open to price adjustments. From a financing perspective, this weakens the assumption of certainty. A contract exists, but it does not guarantee continuity.
This is where many projects begin to struggle. Not at the pilot stage, where conditions are controlled and volumes are small, but when they try to scale. A supplier finds a better buyer. Seasonal gaps reduce availability. Moisture levels shift and affect performance. Transport distances increase costs beyond what the model anticipated.
None of these issues are unusual. They are normal features of biomass markets. The problem is not that they happen. The problem is that they are often underestimated or ignored in early project design.
At the same time, it would be too easy to conclude that long term supply is not possible. There are cases where it is more stable. Vertically integrated operations, agro-industrial systems with captive residues, or waste streams with limited alternative uses can offer more predictable supply. But even in these contexts, stability depends on operations, incentives, and consistency over time. It is never absolute.
This shifts the discussion from contracts to systems. Strong projects do not assume feedstock is secured. They build conditions that make supply more resilient. They work with multiple suppliers, even if it adds complexity. They think about geography, not as a detail but as a risk factor. They invest in storage and pre-processing to manage variability. They document chain of custody because traceability becomes critical once carbon claims enter the picture.
None of this is simple. It adds cost. It requires coordination. It forces trade-offs that are not always comfortable, especially in early stages when projects are trying to move quickly and keep budgets tight. But avoiding these decisions does not remove the risk. It only postpones it.
A more useful question is not whether feedstock is secured, but how the system behaves when conditions change. If prices increase, do suppliers stay? If one source drops, what replaces it? If quality shifts, does the system absorb it or fail?
These are not edge cases. They are expected scenarios.
As the sector moves from pilots to infrastructure, this distinction becomes more important. Feedstock is no longer a background assumption. It is a central element that shapes whether a project operates consistently, delivers credible carbon outcomes, and maintains trust with buyers and investors.
The takeaway is not that feedstock cannot be managed. It is that it cannot be treated as a fixed input. It has to be actively designed, monitored, and adjusted over time.
Projects that recognize this early tend to build systems that hold under pressure. Those that do not often discover the limits of their assumptions later, when the cost of correction is much higher.
Sorry, there were no replies found.
Log in to reply.