“Over the years we’ve invested significantly in our field data team - focusing on producing trusted ratings. While this ensures the accuracy of our Ratings, it doesn’t allow the scale across the thousands of projects that buyers are considering.”
For more information on carbon credit procurement trends, read our "Key Takeaways for 2025" article. We share five, data-backed tips to improve your procurement strategy.
One more thing: Connect to Supply customers also get access to the rest of Sylvera's tools. That means you can easily see project ratings and evaluate an individual project's strengths, procure quality carbon credits, and even monitor project activity (particularly if you’ve invested at the pre-issuance stage.)
Book a free demo of Sylvera to see our platform's procurement and reporting features in action.
The landscape has changed
A decade ago, methodology selection was relatively forgiving. Verification requirements were lighter, buyer scrutiny was lower, and the market wasn't particularly sensitive to quality distinctions between project types.
That’s changed more recently. Methodologies like Verra's VM0047 - the new high standard for Afforestation, Reforestation, and Revegetation (ARR) projects - now require developers to demonstrate, quantitatively and at scale, that their project is generating real carbon outcomes.
VM0047 uses a dynamic performance benchmark to assess additionality and determine the crediting baseline at each verification. So, not a one-time snapshot, but an ongoing, data-driven comparison between growth inside the project and comparable control plots outside it.
Buyers and investors are following suit. Sylvera ratings data shows a widening premium between high-rated and low-rated credits, with AAA-rated ARR projects commanding significantly more per credit than BBB equivalents.
The methodology you choose, and how well your project is designed to meet its requirements, is increasingly showing an impact on where on that spectrum your credits land.
Where developers see challenges
Many methodology-related problems are not discovered at the design stage. They surface at validation, at the first verification event, or when a buyer's due diligence team looks under the surface.
The common issues:
Choosing on familiarity rather than fit. Developers default to methodologies they know, or that their consultants have used before, without modelling how design choices will perform under that methodology's requirements at verification.
Underestimating data requirements. To comply with VM0047, for example, project developers must source up-to-date geospatial data, including jurisdictional boundaries, ecoregions, policy environments, and land tenure information (and that's before the performance benchmark data requirements). Many developers discover these requirements after committing to a site and a methodology.
Proxy data that won't survive scrutiny. NDVI-based approaches are common but increasingly problematic. NDVI saturates quickly in dense canopy and doesn't reliably track real biomass change, which means the performance benchmark comparisons built on it don't hold up when a VVB examines them closely.
No signal on rating until it's too late. Developers typically don't know what quality rating their project is likely to achieve until credits are issued and assessed. By then, the design decisions that determine that rating are locked in.
Why it matters commercially
The gap between a project designed with methodology compliance in mind and one that scrapes through verification isn't just reputational, it's financial.
Credits that achieve a strong Sylvera rating command a meaningful premium over lower-rated equivalents. Buyers paying for quality, particularly those with CORSIA obligations or SBTi commitments, use ratings as a primary filter. A project that fails to achieve a BBB+ rating is effectively excluded from a growing share of the market.
Verification delays compound the cost further. Every month between project registration and first issuance is revenue not generated. Projects that go into their first VVB review without a clean evidence base - traceable data, consistent methodology, auditable outputs - typically spend months in back-and-forth before credits can be issued.
What good looks like
The developers navigating this successfully typically do the following:
They model methodology fit before committing to a site, using market data on which methodologies achieve high ratings across different geographies and project types, and which design choices within those methodologies drive quality scores.
They build data infrastructure early. For VM0047 projects specifically, the methodology relies on remote sensing data to establish a project's baselines and test its additionality, which means the data strategy needs to be in place at inception, not retrofitted before the first verification.
And they get an independent read on expected quality before registration, not after. Pre-issuance assessment (understanding your likely rating and the specific actions that would improve it while there's still time to act) is increasingly the difference between projects that achieve premium pricing and those that don't.
Getting it right: Two examples
A developer in Southeast Asia receives a Pre-Issuance assessment on their IFM project six months before registration. The assessment identifies two design decisions - monitoring protocol coverage and the additionality argument structure - that are likely to limit the project to a B rating under current design. With time to act, they revise both. At issuance, the project achieves a BBB+ rating, and they sell the first vintage at a price 40% higher than their original pricing model assumed.
A developer in East Africa is evaluating three potential ARR sites under VM0047. Rather than committing field teams to all three, they use Sylvera's Biomass Atlas to compare biomass density, canopy height, and 20-year historical trajectory across all sites simultaneously. One site emerges as clearly stronger, with lower existing carbon stock (which simplifies baseline establishment) and a surrounding landscape that provides a clean donor pool for control plot matching. They focus resources there, build the VM0047 package on actual biomass data, and enter validation with a complete, traceable evidence base. VVB review takes weeks, not months.
How Sylvera helps
Sylvera Ratings and Pre-Issuance Assessments give developers an independent read on expected project quality before credits issue, including specific improvement actions while there's still time to implement them.
Market Intelligence reveals the quality-price relationship across 300,000+ verified transactions showing exactly what premium a given rating commands across your methodology or geography, and what buyers are actually paying for comparable projects. As part of this, Methodology Profiles show which approaches achieve high ratings across different project types and geographies, so methodology selection is grounded in market evidence rather than assumption.
Biomass Atlas provides the wall-to-wall, field-calibrated carbon stock data that methodologies like VM0047 require. This supports site selection, baseline establishment, control plot matching, and performance benchmarking at scale, without the cost and delay of traditional consultant-led approaches.
This helps answer two of the most important early-stage design questions: will my project meet VVB requirements? and will it command a premium price? Get clear, data-backed answers to these before you commit.
If you’d like to see how you can model project outcomes, meet methodology requirements, and build the evidence base that secures project revenue - discuss your project with us here.
