Most carbon projects fail commercially for ordinary reasons. The project is too small. The verification burden is too high. Revenue arrives too slowly. Or the expected credit price is optimistic compared with what buyers will actually pay. A feasibility pass should catch all of that before the project becomes expensive.
This is the practical question to answer early: if you combine annual credit volume, likely market price, project life and certification costs, does the project still generate enough margin to be worth building?
The four inputs that matter most
1. Annual credit volume
Start with the most defensible first-pass number you can. If volume depends on highly optimistic adoption rates, aggressive permanence assumptions or unusually high baseline emissions, the rest of the model becomes unreliable. Conservative volume is almost always more useful than aggressive volume.
2. Realistic price per credit
Price should reflect project type, quality, buyer demand and registry fit. A project that only works at the top of the market often does not work. This is why feasibility and pricing should be linked rather than modelled separately.
3. Fixed and recurring certification costs
Validation, verification and registry costs can destroy the economics of a small project. These are often the difference between a commercially viable project and an attractive-looking one that never reaches issuance.
4. Timing
Many projects are not profitable in year one because validation hits early and issuance comes later. A project can still be viable if the break-even timing is sensible and the cash burden is manageable. This matters especially for developers funding early work themselves.
What a useful feasibility pass should answer
- What is year-one gross revenue at conservative, base and optimistic prices?
- How much revenue remains after certification and registry costs?
- When does the project break even?
- At what minimum price does the project become commercially defensible?
- Does the project still work if credit volume is lower than expected?
A practical feasibility lens by project type
| Project type | Main commercial risk | What to test early |
|---|---|---|
| Cookstoves | Field delivery cost and fNRB assumptions | Whether annual volume is enough to absorb GS validation and recurring verification |
| Biochar | Feedstock economics and premium-price dependence | Whether Puro-style pricing still works after realistic production and verification costs |
| Forestry / ARR | Long timelines and buffer deductions | Whether the project still works after leakage, buffers and slower issuance timing |
| Solar | Lower commodity-style credit pricing | Whether scale is large enough to justify certification and monitoring effort |
| Water | Programme scale and monitoring burden | Whether household reach and fuel-saving assumptions support enough credits |
Try the feasibility modeller
Use the live calculator below to pressure-test revenue, costs and break-even timing before you move deeper into project design:
Use the full tool in The Carbon Workbench for saved calculations, PDF reports, and easier comparison across multiple project cases once this first-pass screen looks promising.
Use full tool in The Carbon Workbench →Where feasibility usually breaks down
Scale is too low
A small project can look compelling conceptually but still fail financially because fixed certification costs absorb too much of the first years of revenue. This is why verification cost analysis should sit next to feasibility rather than after it.
Price assumptions are borrowed from the best examples
Developers often model to a premium benchmark without asking whether their own project quality, narrative, geography and standard fit justify it. A stronger model uses a range and expects most projects to clear on the middle case, not only the top case.
Commercial timing is ignored
Even a profitable project can be difficult to build if the first issuance arrives too late or the validation burden is too front-loaded. Break-even year matters because it affects whether the project is realistically financeable.
What to do after the first feasibility pass
- If the project is promising, refine the methodology path and verification assumptions.
- If the project is marginal, test whether scale, pricing or standard choice materially changes the result.
- If the project only works under optimistic assumptions, treat that as a warning rather than a near miss.