Take on a podcast episode from Reversing Climate Change, originally published Thu, 25 Ju. Listen: https://podcasters.spotify.com/pod/show/reversingclimatechange/episodes/405-Does-Managed-MRV-imply-the-existence-of-Unmanaged-MRV--w-Varsha-Ramesh-Walsh--Offstream-e3l8cev

TL;DR

  • Offstream is repositioning from a DMRV (digital monitoring, reporting, verification) software vendor to “Managed measurement, reporting, and verification (MRV)” — they do the work, not just provide a dashboard. Useful naming of an under-articulated category.
  • Walsh’s claim: the head-of-MRV in-house hire is often more expensive than outsourcing the whole function. Plausible for small biomass developers, untested at scale.
  • Most operational data in carbon projects still passes through a human at some point — bills of lading, odometer photos, clipboard entries. Honest admission worth hearing from a vendor.
  • Thesis: every owner of a physical asset eventually becomes a carbon project developer. Big swing; light on the path to get there.
  • Long surveillance-capitalism tangent eats ~20% of the runtime. Skippable.

Ross Kenyon hosts Varsha Ramesh Walsh, cofounder/CEO of Offstream, on episode 405 to explain why Offstream stopped trying to be pure software and embraced what Walsh calls “Managed MRV” — a services-plus-platform model targeting biomass-based durable CDR developers (biochar, lumber mills with waste streams) and increasingly 48E ITC tax-credit work.

The substantive piece here is the category articulation. Walsh argues every monitoring, reporting, verification stack has a manager — the question is whether it’s a $200K/year in-house head of carbon wrestling with a SaaS dashboard, or an external team with reusable tooling across dozens of projects. Her observation that customers kept asking Offstream to “just do the work” while the team tried to automate humans out of the loop is a real pattern in this market, and it lines up with what we’ve seen at registries and verifiers: the bottleneck is judgment calls, not data pipes. Her framing — “everyone thinks compliance is black and white, but it’s actually just a bunch of gray area” — is the load-bearing claim. If true, fully-automated DMRV is a category error for current methodologies.

The second worthwhile thread is her candor about data provenance. Walsh estimates 95%+ of projects today have human-touched data somewhere in the chain, and the working solution is triangulation — a clipboard entry corroborated by two other signals — not panopticon-grade sensorization. That’s a more honest baseline than most MRV vendor pitches give you, and it matters for buyers diligencing biomass credits where the feedstock chain-of-custody is the integrity weak point.

The “everyone with a physical asset becomes a project developer” thesis is the speculative part. It rhymes with the broader infrastructure-as-CDR-asset framing you see from biomass aggregators and from buyer coalitions like Frontier, but the path from today’s startup-led developer base to lumber-mill-as-carbon-developer runs through methodology simplification that hasn’t happened yet. Worth holding next to ongoing debates about Isometric and Puro.earth protocol stringency — if Walsh is right that operators want flexibility, registries pulling the other direction is the live tension.

Useful for: biomass CDR developers weighing build-vs-buy on MRV staffing, and buyers trying to understand what’s actually happening behind the dashboards they’re shown in diligence. Skip if you want technical depth on specific methodologies — this is a category/strategy conversation, not a protocol one.