Many companies come to us with a list of carbon credit requirements: a budget, a preferred region, a project type they want or want to avoid, or a rating agency they trust. Each preference is reasonable on its own. However, when combined, they can shrink the list of projects a buyer can support to a handful, and sometimes to none.
This post walks through how requirements stack up and the approach we use to help buyers set priorities, so they still end up with a diversified portfolio that puts climate impact first.
The starting pool of high-quality projects
Less than 4% of projects are eligible for our portfolios. To qualify, a project has to pass our diligence review, be highly rated by independent rating agencies, and have credits available for purchase. Every additional requirement a buyer has narrows that small pool further.
Budget sets the ceiling
For most buyers, the budget is fixed or close to it. It may be a total spend, a price per tonne, or both. Either way, it rules out some projects before any other requirement comes into play.
Prices vary widely by project type and region. Sylvera's analysis puts the average price of North American afforestation, reforestation and revegetation credits at $16.97 per tonne, compared with $9.88 in Asia. In one improved forest management project we reviewed, removal credits were priced in the high $20s per tonne, while avoidance credits from the same project were in the teens. A portfolio that mixes project types and price points gives buyers more room to work within their budget.
Common preferences that narrow the list
After quality and budget, we often see preferences for:
- Geography: US projects only, or projects in regions where the company operates
- Project type: Excluding a type, such as REDD+, or preferring certain types, such as superpollutant or carbon dioxide removal (CDR) projects
- Rating agency: Accepting ratings from only one carbon credit rating agency
- Industry or impact fit: Only projects tied to the buyer’s industry or interests, such as education or biodiversity
An example: one buyer’s requirements
Earlier this year, we worked with a buyer that wanted US projects only, recent vintages, and a rating of BB or higher from Calyx Global. For landfill gas projects, they also wanted the captured gas used to generate electricity rather than flared.
With all of those requirements applied, only three landfill gas projects qualified, and two of those had credits available. Once the buyer dropped one of those requirements, their options widened considerably.
When requirements ask for more than the market offers
It's fairly common for a buyer to ask for a portfolio that doesn't exist. For example: at least four projects, all in the US, removals only, for less than $10 per tonne. Based on Sylvera's regional prices above, North American reforestation credits average well above that ceiling on their own.
When that happens, we help the buyer decide which requirements matter most.
How we help buyers set priorities
This is the approach we use with buyers:
- Start with quality. Quality isn't negotiable, so every portfolio starts from the small pool of projects that pass our diligence.
- Use budget as a guide. Whether a company has set an internal carbon fee or an overall budget, that number shapes what it can purchase.
- Rank everything else. Stack-rank the remaining requirements by importance and look at the portfolio that results. If the list gets too short, loosen or drop the lower-ranked ones.
- Mix targeted and broader projects. Pair the specific projects that fit the buyer’s story with excellent projects less closely tied to its brand. This keeps the purchase in budget and spreads risk across project types and regions, while still telling the story the buyer wants to tell.
Applying this to your purchase
Every company has preferences and constraints to weigh against what the market offers. Starting from quality and ranking the rest keeps the pool wide enough to build a portfolio that fits your needs.
If you’d like to walk through your preferences and see which projects align, talk to our team.



.png)