Research3 Originator Persona

LATAM Carbon Project Developer — Originator Persona Ethnography

Research date: 2026-04-25 Scope: Day-in-the-life ethnography for eight personas at LATAM carbon project developers (Brazil, Mexico, Colombia, Peru, Paraguay, Argentina), recurring cross-functional rituals, time-and-motion estimates by team scale, pain-point clusters, and a synthesized v1 product wishlist. Method note: Direct LATAM operator quotes are thin in public material. Where direct evidence exists (Carbonext interviews, Mombak Q&As, Permian Global testimonials, Quadriz public PDDs, Toroto public materials, Mongabay/SUMAÚMA reportage), it is cited verbatim. Where it does not, BlueLayer customer materials, Sylvera analyst commentary, CarbonHQ founder framing, and Microsoft/Symbiosis published guidance are used as triangulating proxies — each so flagged in-line.

Part A — Persona profiles

A.1 Project Director / Head of Carbon (“Diretor de Carbono” / “Gerente Senior de Carbono”)

Identity. Title in PT: Diretor de Projetos de Carbono, Head de Carbono; ES: Gerente de Proyectos de Carbono, Director de Originación. Education: forestry engineer (ESALQ-USP, UnB, UFV, La Molina, UNAL), agronomist, or biologist; usually a Master’s or Ph.D., often a second-career hire from large industrial forestry (Suzano, Klabin, Smurfit Kappa) or conservation NGOs (CI, TNC, WWF). The archetype is Mauricio Penteado, COO of re.green, “former COO of Suzano [who] has managed operations in over 600k hectares of planted forest and the planting of 100k ha per year” (re.green People page). Salary band, total comp 2025: São Paulo R$600k–R$1.2M (~USD 120k–240k; senior comp tracks ERI’s “Director” range of R$372k base + R$138k bonus, with carbon-sector premiums on top — SalaryExpert Brazil Director); Mexico City MXN 2.0–4.5M; Bogotá COP 350M–700M; Lima USD 80k–160k. CSO-equivalent senior comp in São Paulo runs BRL 800k–1.5M (DigitalDefynd CSO benchmark).

Day-in-the-week.

• Monday 08:00–10:00 — Pipeline review with originación / sales: which projects move from term-sheet to contracted? Which need a verification cycle accelerated to hit Q3 issuance?
• Monday 14:00–18:00 — Board / IC reading week: financial covenant report drafts for BNDES Fundo Clima (Mombak’s R$100M facility includes covenant reporting — BNDES press release) and AXA IM Alts off-balance-sheet vehicle reporting.
• Tuesday — Donor/buyer travel: Climate Week NYC, COP, Climate Asset Management LP visits, often two trips/month.
• Wednesday 09:00–12:00 — Cross-functional standup: MRV lead presents satellite anomalies; field coordinator presents asamblea outcomes; compliance lead lists Verra Project Hub items pending VVB response.
• Wednesday afternoon — Methodology committee / steering: VM0048 transition decisions, ABACUS label decision, ART vs Verra dual-listing.
• Thursday — Hiring loops, 1:1s with persona Heads. Doubling field teams (Mombak: from 200 to 400 agronomists/forest technicians during 2025 scaling — Carbon Herald) is a recurring agenda.
• Friday — Investor / press / IETA / ICVCM external. Janaina Dallan (Carbonext founder) sits on ICVCM and CONAREDD (Carbonext About) — public-facing standards work is structurally part of the role.

Tools used today. Email (Outlook/Gmail), Microsoft Teams or Google Meet, WhatsApp Business (the dominant Brazil/Mexico/Colombia text channel — see WhatsApp’s growth in those markets per Cities Today). Excel/Google Sheets for everything financial. Box / SharePoint / Google Drive for project documents. Salesforce or HubSpot for buyer pipeline at mid-size+ firms; nothing at early-stage. No purpose-built carbon OS at most LATAM developers — except Carbonext (proprietary CarbonEye), Mombak (proprietary stack), Permian Global (BlueLayer — Carbon Herald BlueLayer/Permian). Power BI or Tableau for board decks.

Top three frustrations.

1. Issuance lag burns runway. Standard Verra issuance cycle is 6–8 weeks of cross-team scramble before the credits hit the registry account, and that’s after a ~12-month VVB validation window (Carbon Insurance lifecycle guide; Sustain-Cert on Verra). Verra’s 2025 4-year-low issuance figures and VVB suspensions amplify this (QC Intel; Verra suspension notice).
2. Reputational landmines outside her control. Mongabay/SUMAÚMA investigations have repeatedly exposed land-tenure and timber-laundering issues in Amazon REDD+, dragging in Carbonext and others; that forces ad-hoc audit responses and buyer reassurance that consumes weeks (Mongabay 2024 Amazon investigation; SUMAÚMA “Carbon Cowboys”).
3. Methodology version migration. When Verra ships VM0048 / VM0047 v1.1 / new ABACUS gate, every project re-baselines — third-party data inputs, six-year baseline validity, new requantification procedures (Verra VM0048 FAQ; Verra requantification procedure). The Director carries the cost-of-replan to the board.

What they wish for. A “single source of truth” across project, inventory, and contract data — exactly the language Permian’s Edward Rumsey uses about BlueLayer: “To ensure we are ready for sustainable and continued success, it was important for us to find a partner that gives us peace of mind” (BlueLayer Permian case study). Forecast accuracy at portfolio level: “The ability to quickly generate insights at both project and portfolio levels with BlueLayer has improved our decision-making and boosted our forecast accuracy” (Rumsey, same source).

A.2 Project Manager / Coordinator (“Coordenador de Projeto” / “Coordinador de Proyecto”)

Identity. PT: Coordenador(a) de Projetos REDD+/ARR. ES: Coordinador(a) de Proyecto. Education: forest engineer / environmental engineer / geographer; 5–10 years’ experience; often runs one ~50,000–500,000 ha project end-to-end. Salary band: São Paulo R$180k–R$300k base; Mexico City MXN 600k–1.1M; Bogotá COP 110M–180M.

Day-in-the-week.

• Monday — PDD section ownership review: each project ID has 30+ documents (PDD, monitoring report, FPIC files, baseline rationale, risk reports). Quadriz’s public Corazón Verde del Chaco PDD (2023.02.28 PDD PDF) is the visible 100-page artifact; the working version lives in Word + Box.
• Tuesday — Field-data reconciliation: plot inventory CSVs from KoboToolbox / ODK / Survey123 are emailed in by foresters; the PM merges them into a master XLSX, hand-resolving GPS / species code mismatches (KoboToolbox docs).
• Wednesday — VVB Q&A response: typical Verra audit produces 80–250 corrective action requests; the PM owns the spreadsheet that tracks “CAR-12: clarify additionality test” → who responds → due date → status. Verra’s PRRs (Project Request Reviews) now run digitally through the Project Hub but VVBs and proponents still operate on PDFs (Verra Project Hub).
• Thursday — FPIC ongoing compliance: confirms next month’s asamblea dates with the Community Engagement Officer, reviews the benefit-sharing payment schedule.
• Friday — Internal monthly sync: handoff between MRV, finance, and sales on whether the Q3 monitoring report is on track.

Tools used today. Word/Google Docs (for PDDs), Excel/Google Sheets (for everything else), Box/SharePoint/Google Drive, QGIS or ArcGIS Pro to spot-check shapefiles, KoboToolbox / ArcGIS Survey123 / ODK Collect form output, WhatsApp groups per project, Slack or Teams internally, Verra Project Hub, ART portal, Cercarbono Ecoregistry portal (Cercarbono–Ecoregistry alliance).

Top three frustrations.

1. Document chaos. The PDD lives in five places at once — Word draft, Box folder, registry portal upload, VVB SharePoint, buyer data room. Every revision has to be copied into all five.
2. Field-data reconciliation by hand. “Drowned in Excel” is the framing CarbonHQ founder Allan Fan uses to describe the legacy state (PropelAuth case study).
3. Audit Q&A loops blow up the calendar. A PRR can ricochet between the proponent, two consultants, the VVB, and Verra over four weeks for a single CAR.

What they wish for. Methodology-specific evidence templates with built-in audit logs — the explicit value-prop of BlueLayer’s dMRV Workspace, which “provides templates for evidence collection (soil samples, satellite imagery, lab certificates) and keeps a complete audit log, making third-party verification faster and easier” (BlueLayer how-it-works).

A.3 MRV / Geospatial Analyst (“Analista de Geoprocessamento” / “Analista MRV”)

Identity. PT: Analista de Geoprocessamento e MRV. ES: Analista de Sensores Remotos / MRV. Education: geographer, forest engineer, remote-sensing M.Sc.; often INPE-trained in Brazil, La Molina or USP-Pirassununga in others. Salary band: São Paulo R$140k–R$240k; Mexico City MXN 480k–900k; Bogotá COP 90M–150M.

Day-in-the-week.

• Monday — Pull weekly Sentinel-2 mosaic, cross-reference INPE PRODES/DETER deforestation alerts and MapBiomas Alerta refinements. MapBiomas Alerta uses PlanetScope 3-m imagery and publishes weekly validated deforestation/regeneration alerts (MapBiomas Alerta method).
• Tuesday — Run the project-area mask in Google Earth Engine; refresh canopy cover statistics against the project shapefile. Carbonext built CarbonEye in partnership with the Google Accelerator for Startups, “uses computer vision algorithms to process satellite imagery and detect threats to forest integrity” (Carbonext High Integrity).
• Wednesday — Plot inventory ingestion: receive KoboToolbox export, run allometric equations, reconcile with previous monitoring period. Pachama/Carbon Direct framework: “satellite imagery, LiDAR data, and machine learning… assess carbon stocks across forest projects with unprecedented accuracy and efficiency” (Carbon Direct acquires Pachama).
• Thursday — Baseline maintenance under VM0048: under VM0048 the baseline is jurisdictionally allocated by Verra using third-party data, with a six-year validity (Space Intelligence VM0048 FAQ). Analyst’s job is increasingly “QA the data Verra/Space Intelligence pushed me,” not “set my own baseline.”
• Friday — Ad-hoc buyer requests: “send the satellite time-series for the project polygon” — typically delivered as PNG screenshots in PowerPoint.

Tools used today. QGIS, ArcGIS Pro, Google Earth Engine, Python (rasterio, geopandas), R (terra). Imagery: Sentinel-2, Landsat, Planet (PlanetScope, SkySat), Maxar tasking for high-res, INPE PRODES/DETER, MapBiomas Brasil/Colombia/Amazonía, Global Forest Watch, ESA WorldCover. dMRV proxies: Pachama (until Carbon Direct acquisition), Sylvera screening data, BlueLayer dMRV Workspace, Restor for restoration projects, Boomitra (soil C). For grassland/SOC: Boomitra (“digital MRV that fuses multi-satellite imagery and AI with an unparalleled archive of 1M+ lab-analyzed, georeferenced soil samples” — Boomitra Science & Tech).

Top three frustrations.

1. MRV reconciliation triangulation. Satellite says canopy cover X; plot says biomass Y; allometric model says C-stock Z; nobody owns the canonical number.
2. Imagery licensing and credit budgets. Planet, Maxar, even Earth Engine compute have line-item costs that the geospatial analyst has to defend each quarter.
3. The shapefile scavenger hunt. Sylvera publicly notes that “the most common type of data missing is a shapefile (the geographic boundary of the area for which credits are being claimed), with Sylvera making repeated requests to developers… in many cases they have received no response” (Sylvera ratings process). The analyst is the one digging through Box folders to find which version is canonical.

What they wish for. A workspace where canonical project geometry, current monitoring period, methodology version, and last issuance vintage are linked — and where every shapefile push automatically refreshes downstream dashboards. This is the gap Sylvera + BlueLayer’s February 2025 “Live Carbon Project and Inventory Data Set” partnership tries to fill (Sylvera blog; QC Intel).

A.4 Field Coordinator / Forester (“Coordenador de Campo” / “Brigadista”)

Identity. PT: Coordenador de Campo, Engenheiro Florestal de Campo. ES: Coordinador de Campo, Brigadista. Education: técnico florestal or junior forest engineer; based in Manaus, Belém, Rio Branco, Iquitos, Pucallpa, Mérida, Campeche; spends 2–3 weeks/month in the field. At Mombak the field tier is being doubled “from 200 to 400 agronomists and forest technicians, recruiting primarily from local communities. Trainees receive certification in silviculture best practices” (Carbon Herald Mombak Series A). Salary band: junior R$60k–R$90k (Brazil), MXN 250k–450k (Mexico), USD 18k–35k (Peru). Senior field coordinators 1.5–2× that.

Day-in-the-week. A field rotation looks like:

• Day 1–2 — Travel + asamblea or community meeting, often via boat and 4×4. Confirm access permits, brigade rosters.
• Day 3–7 — Plot inventory: DBH, height, species ID, soil sample collection. Carbonext’s GIS-on-mobile approach is explicit: “on-the-ground human agents, often hired from local communities and trained to collect survey data about forest integrity using GIS apps on mobile devices” (Esri WhereNext Carbonext profile, indexed in search results).
• Day 8–10 — Patrol / threat verification: check fire scars, illegal logging tracks flagged by satellite the prior week.
• Day 11–14 — Nursery / planting QA at ARR projects (re.green has 30,000 ha across 4 Brazilian states — re.green homepage).
• Evenings: WhatsApp updates to PM with photos, plot CSVs synced when they hit a town with cellular signal.

Tools used today. KoboCollect / ODK Collect / ArcGIS Survey123 on Android tablets (often Samsung A-series, ruggedized cases). Garmin GPSMAP for redundancy. SatPhone / Iridium GO! when out of cell range. Drones (DJI Mavic 3 Multispectral, Phantom 4 RTK) for plot validation. Paper field notebooks remain mandatory backup. WhatsApp Business for daily check-ins. Open Forest Protocol’s Forester app is increasingly used for community-led MRV: “collects forestry or conservation data, GEO-locates plots of land, inputs measurement data, takes pictures of trees, and instantly sends the array to the Project Dashboard” (OFP overview).

Top three frustrations.

1. Offline-first reality. Most field tools assume connectivity that does not exist 30 km up the Juruá or Madre de Dios. Sync queues drop, GPS coordinates vanish.
2. Form drift. Each project + each monitoring period gets a slightly different form. Forester opens the wrong version, captures the wrong attributes.
3. Translation gap. The form is in PT/ES; the brigadista community member speaks Yanomami / Kichwa / Maya / Guarani. Names of species, indicators of “degradation,” and FPIC consent fields don’t survive the round-trip.

What they wish for. Offline-first, single-app capture (plot + photo + GPS + community-name autocomplete) that syncs to a master record — and forms versioned per methodology. OFP’s pitch (“forestation projects of all sizes, regardless of location or funding… mobile app cross-checked with satellite, IoT, drone, AI” — OFP article) is exactly this.

A.5 Community Engagement / FPIC Officer (“Coordenador de Engajamento” / “Coordinador Socio-comunitario”)

Identity. PT: Coordenador de Engajamento Comunitário / Especialista em Salvaguardas. ES: Coordinador Socio-comunitario / Especialista FPIC. Education: anthropologist, sociologist, social-work background; often a local hire fluent in the regional indigenous language. The role exists because, as the Pulitzer Center documented at the Cumbal resguardo in southern Colombia, projects can be sold “from the indigenous reservation… without the knowledge of its inhabitants” (Pulitzer Center). Salary band: São Paulo / Belém R$120k–R$200k; Mexico City MXN 450k–800k; Bogotá COP 80M–140M.

Day-in-the-week.

• Monday — Pre-asamblea logistics: confirm the comisariado schedule (in Mexican ejidos, the assembly + comisariado are the legal decision unit — Earthly on Felipe Carrillo Puerto), book travel, prepare translated materials.
• Tuesday/Wednesday — Field travel; conduct asamblea; facilitate Q&A; record consent and dissent. In Mexico’s Conhuás project (Toroto, Campeche) the population is ~900 ejido members on >58,000 ha (Toroto Conhuás).
• Thursday — Draft asamblea minutes, scan signatures, file in Box / SharePoint, send to legal review; trigger benefit-sharing payment requests to finance.
• Friday — Grievance log review; coordinate with field foresters on any conflict flags; respond to buyer due-diligence questions about FPIC adequacy.

Tools used today. Word for minute templates; phone camera + scanner app (CamScanner / Adobe Scan) for signature pages; Box / SharePoint for archive; WhatsApp for community comms. There is no purpose-built benefit-sharing ledger — payments are tracked in Excel and processed via Pix (Brazil), SPEI (Mexico), or wire transfer. Toroto explicitly emphasizes “horizontal collaboration among all involved parties, implementing rigorous social safeguards… territorial climate action provides dignified and fairly compensated work for community partners” (Toroto About) — but the technology to track that is absent in public materials.

Top three frustrations.

1. Paper-bound process. Asamblea consent is captured on paper, scanned, filed, sometimes lost. There’s no offline mobile FPIC consent module.
2. Benefit-sharing opacity. Communities receive payments but cannot see, in one place, the relationship between credits issued, revenue earned by the developer, and their share. The Forest Carbon Partnership Facility, Rights and Resources Initiative, and UN-REDD all emphasize benefit-sharing transparency as the #1 social-integrity challenge (RRI carbon-rights report; UN-REDD social integrity post).
3. Buyer-side scrutiny is escalating. Mongabay/SUMAÚMA exposés, ICVCM CCP rules, and the Microsoft/Symbiosis FY25 procurement guidance all force the FPIC officer to evidence robust consent processes well past Verra’s documentation requirements (Microsoft FY25 CDR guidance PDF).

What they wish for. A native-language, offline-capable consent capture app + a benefit-sharing ledger with a community-facing read-only view; the ability to register grievances against a single project ledger so the developer can demonstrate response time. None of the current dMRV platforms (Pachama/Carbon Direct, BlueLayer, Boomitra, Sylvera) ship a community-facing FPIC module today.

A.6 Compliance / Registry Liaison (“Coordenadora de Conformidade” / “Coordinadora de Acreditación”)

Identity. PT: Especialista em Conformidade e Registros. ES: Especialista en Estándares. Background: environmental consulting (ERM, SCS, AENOR, EY Climate), prior VVB-side stint. The role is brutally administrative and often outsourced to firms like SustainCERT for the actual VVB function (SustainCERT Verra services). In-house, the persona owns Verra Project Hub access, ART portal access, and Cercarbono Ecoregistry credentials. Salary band: São Paulo R$160k–R$260k; Mexico City MXN 500k–950k; Bogotá COP 100M–170M; Lima USD 35k–70k.

Day-in-the-week.

• Monday — Open Verra Project Hub, ART portal, Cercarbono/Ecoregistry, Gold Standard Registry, Puro Registry. Triage open items per project per registry.
• Tuesday — Submit monitoring reports to Verra Project Hub. As of November 2025, “PRRs are processed digitally through the Verra Project Hub, which allows VVBs to prepare and submit responses to Verra’s PRRs and the required documentation directly through the platform” (Verra Project Hub). In practice: re-keying values from Word/PDF into web forms.
• Wednesday — Coordinate with VVB (e.g., AENOR, TÜV SÜD, EPIC) on outstanding CARs; chase signed audit reports.
• Thursday — Multi-registry interop: many projects now dual-list (Verra + Cercarbono, Verra + Isometric for ARR, Puro + Verra for biochar). The Ecoregistry/Cercarbono platform alliance (Cercarbono–Ecoregistry) and Cercarbono’s Meta Registry connectivity through S&P Global (S&P press release) are the closest thing to interop today.
• Friday — Issuance ceremony: validate vintages, sign off on retirement requests, reconcile registry account balance with internal inventory spreadsheet.

Tools used today. Verra Project Hub web UI (projecthub.verra.org); ART/TREES portal; Cercarbono Ecoregistry portal; Gold Standard Impact Registry; Puro.earth registry (“BlueLayer To Provide dMRV & Project Data Infrastructure For Puro.earth” — Carbon Herald); Excel sheet tracking fees + validation/verification SLAs; SharePoint / Box for archive; PDF readers for signed audit reports. Crucially, none of these registries currently expose a developer-facing API for outbound submission — all submission is web-form upload. (Verra’s recent fee changes also squeeze developer margins — S&P Global on Verra fees.)

Top three frustrations.

1. Registry portal pain. Each registry’s UX is bespoke, no API, manual data re-entry, session timeouts, frequent login resets, no “diff” between draft and submitted versions.
2. Auditor handoff. “Auditors arrive with PDFs, leave with PDFs.” VVB-side tooling is also bespoke; reconciling a 200-line CAR list by email + Word is the norm.
3. Multi-registry double-keying. Same project data — area, vintage, monitoring period — entered four times across Verra/Cercarbono/Puro/Isometric in the worst case.

What they wish for. A submission orchestrator that holds canonical project data + monitoring reports + corrective-action responses, and pushes via API to every registry that exposes one (Cercarbono via Meta Registry; Puro via BlueLayer’s data infrastructure deal). Plus PDF generation that matches each registry’s exact format requirements.

A.7 Carbon Sales / Commercial Lead (“Diretor Comercial” / “Director Comercial”)

Identity. PT: Diretor Comercial / Head de Vendas de Carbono. ES: Director Comercial. Background: trader from Vitol/Trafigura/STX, M&A from BTG/XP/ItauBBA, or sustainability consultancy (ERM, McKinsey Sustainability). Owns offtake contract negotiation, RFP responses (Symbiosis, Frontier, Microsoft), and the buyer data room. Joshua Holland’s role at Permian — Business Development Associate — is the analyst tier supporting this lead (BlueLayer Permian). Salary band: São Paulo R$300k–R$700k base + variable; Mexico City MXN 1.0M–2.5M; Bogotá COP 200M–450M.

Day-in-the-week.

• Monday — RFP triage: Symbiosis Coalition’s first joint RFP (Google + Meta + Microsoft + Salesforce, run with Pachama / Carbon Direct / Xilva for diligence — Symbiosis on its first RFP; Trellis on Symbiosis) is the canonical 2025 example.
• Tuesday — Term-sheet drafting: forward purchase, prepay, vintage hedge.
• Wednesday — Buyer due-diligence response: Microsoft’s CDR diligence “takes 2–3 months to complete… For projects aiming for a multi-year contract, diligence and negotiation may take 6–9 months or more” (Microsoft FY25 CDR Procurement Guidance, PDF). The Sales Lead owns the response document, which routes to MRV, Compliance, FPIC, and CFO.
• Thursday — Pricing committee + inventory forecast (which vintages are clear to sell vs. ringfenced under an existing offtake).
• Friday — Industry event circuit: Carbon Forward, Climate Week NYC, IETA, COP, Carbon Pulse roundtables.

Tools used today. Salesforce or HubSpot CRM; DocuSign for term sheets; Excel for pricing models and forward curves; Argus / S&P Platts / Carbon Pulse / Sylvera price feeds; Senken / ACX / CTX / AirCarbon Exchange marketplace dashboards (BlueLayer–Senken partnership announced 2025 — BlueLayer/Senken). Sylvera’s “Connect to Supply” centralized ~200 supplier database, now wired to BlueLayer with 80+ projects introduced and 4M credits of buyer demand catered to (Sylvera–BlueLayer launch).

Top three frustrations.

1. Buyer-side scrambling forces archaeology. Every diligence request triggers a fresh dig through Box / Google Drive / GIS server / VVB email threads.
2. Inventory truth is downstream of compliance. Sales can promise vintages that compliance can’t deliver because issuance slipped — exactly the workflow problem Permian’s John Peachey describes: “Thanks to BlueLayer, our workflow complexity is a thing of the past. They’ve transformed our inventory management and distribution into a streamlined process” (BlueLayer Permian case study).
3. Quality-tier pricing dispersion. ICVCM CCP-labeled credits trade at ~25% premium and ABACUS commands further premium (ICVCM Impact Report 2025; Calyx Global on ABACUS) — the sales lead lives the cost of not having the right labels.

What they wish for. A live inventory ledger, contract management, pricing and forecasting in one place — Permian’s Joshua Holland summarizes: “BlueLayer has added value by improving data accessibility and auditability within our carbon sales team by tracking our inventory against our sales orders” (BlueLayer Permian). Plus reusable buyer data rooms that auto-populate from canonical project data.

A.8 CFO / Finance (“Diretora Financeira” / “CFO”)

Identity. Mombak’s archetype: Gabriel Silva, ex-Nubank CFO; vertically integrated finance + project equity + bond + offtake. Salary band: São Paulo R$700k–R$1.8M total comp at scale; Mexico City MXN 2.5M–5M; Bogotá COP 400M–800M.

Day-in-the-week.

• Monday — Treasury: FX management between USD-denominated offtake revenue (Microsoft, Google, McLaren — Mombak has $150M offtake contracts mostly in USD — ESG News Mombak Series A) and BRL-denominated cost base (planting, payroll, BNDES debt). Hedge program review.
• Tuesday — Loan covenant compliance for the BNDES Fundo Clima R$100M (with R$80M from Fundo Clima + R$20M Finem, Santander guarantee — BNDES press release) and any IDB / IFC facilities. AXA IM Alts off-balance-sheet vehicle reporting (Silva: “we have raised financing into off-balance sheet project equity vehicles of which AXA IM Alts is the largest investor” — AXA IM Alts Q&A).
• Wednesday — Tax strategy: Brazilian Lei 15,042/24 (effective Jan 2025) clarified that carbon-credit revenue is exempt from PIS/COFINS, ICMS, ISS, and IPI; IRPJ/CSLL applies as capital gain or net gains regime depending on stock-exchange vs. off-exchange sale (Mayer Brown carbon tax note). IBS/CBS treatment from 2026 is unsettled. CFO + outside counsel monitor monthly.
• Thursday — Project-level finance: cost-per-tCO₂ forecast, productivity tracking. Silva: “The key is to increase productivity and bring down production costs while expanding” (AXA IM Alts).
• Friday — Investor reporting: monthly LP letters, quarterly impact reports for impact-aligned LPs, annual GRI / TNFD / TCFD / SBTi alignment narratives.

Tools used today. SAP S/4HANA, Oracle, or Brazilian-native TOTVS Protheus for ERP; Contpaqi/Aspel in Mexico SMEs; QuickBooks at the early-stage end; Power BI / Tableau for management reporting; Bloomberg Terminal or Refinitiv for FX; treasury-management system (Kyriba at scale); Excel for everything else. Project-finance models live as 50-tab .xlsx files. No off-the-shelf carbon-specific finance tool — the finance team builds bespoke.

Top three frustrations.

1. Revenue recognition under uncertainty. When credits are issued is uncertain, when the buyer takes delivery is uncertain, FX rate at delivery is uncertain — and audited financials want a number.
2. Covenant reporting demands a data model that doesn’t exist. BNDES, IDB, AXA, and bondholders each want different cuts of “tCO₂ planted, tCO₂ verified, tCO₂ sold, tCO₂ retired” — and the source data lives in MRV / sales / compliance silos.
3. Brazilian tax reform timing risk. Lei 15,042/24 just settled the indirect-tax question, but IBS/CBS implementation in 2026+ reopens it (Mayer Brown).

What they wish for. A unified project-revenue ledger that ties tCO₂ verified → tCO₂ contracted → tCO₂ delivered → cash received, with FX overlay and covenant-pack auto-generation. Today this is the CFO’s biggest spreadsheet liability.

Part B — The recurring rituals

B.1 Pre-issuance dry-run cycle (≈6–8 weeks)

Six to eight weeks before submission, the PM convenes MRV, FPIC, Compliance, Sales, and Finance. MRV finalizes monitoring period numbers; FPIC compiles asamblea minutes for the period; Compliance reconciles with VVB; Sales freezes inventory forecasts; Finance updates revenue recognition. The 6–8-week window is industry-standard (Carbon Insurance lifecycle; Eos.com on issuance process). When VM0048 jurisdictional baselines refresh on a six-year cycle, this dry-run also includes baseline-shift requantification (Verra requantification procedure; Space Intelligence VM0048 FAQ).

B.2 Annual audit / verification cycle

Validation phase typically takes ~12 months with multiple VVB Q&A rounds; subsequent annual verifications run 4–6 months and produce 100–250 CARs per project (Sustain-Cert on Verra; Ecobase blog). The PM owns the CAR tracker. VVB suspensions (Verra suspended four VVBs over 37 China rice projects in March 2025 — Verra notice) can force audit-mid-stream re-routing.

B.3 Buyer due-diligence response cycle

A Microsoft / Carbon Direct / Symbiosis / Frontier diligence packet runs 80–250 questions across additionality, permanence, leakage, MRV adequacy, FPIC, biodiversity, finance (Microsoft FY25 CDR procurement guidance; Symbiosis quality criteria; Carbon Direct on technical diligence). Microsoft expects 2–3 months to a “go” decision; multi-year contracts 6–9+ months. The Sales Lead routes sections internally; the average mid-size LATAM developer answers 5–15 such packets a year. Each one is an archaeology project across Box, GIS server, Drive, email.

B.4 Methodology version migration

When Verra publishes VM0048 (consolidated REDD), VM0047 v1.x updates (ARR), or ABACUS labelling rules, every project decides: stay on legacy, transition, dual-list. Each decision triggers re-baselining, new shapefiles to Verra’s third-party data provider (Space Intelligence et al.), buyer reassurance mailings, and possibly a new VVB engagement (Verra VM0048 FAQ; BeZero on VM0047; Verra ABACUS announcement). Cost: typically R$200k–R$1M per project in consultant fees alone, plus 2–4 months of internal ops.

B.5 FPIC ongoing compliance

Asamblea cadence varies — Mexican ejidos run formal assemblies every 1–6 months; Peruvian comunidades nativas per their internal statute; Brazilian terras indígenas often via FUNAI-mediated formal consent for entry. Benefit-sharing payments sit in finance’s run-the-business ledger. Grievance mechanism logs sit in the FPIC officer’s file, not a system. The Pulitzer Center / Mongabay / SUMAÚMA reportage cluster (Pulitzer Cumbal; Mongabay 2025 Chevron-on-indigenous-land; SUMAÚMA Carbon Cowboys) is the public-record proof that “ongoing” FPIC compliance is the segment most likely to fail.

B.6 Registry portal submission ceremony

For each issuance, the Compliance Liaison: (1) uploads validated monitoring report + corrective-action responses to Verra Project Hub; (2) Verra performs internal QA review (a few months at minimum — SustainCERT); (3) credits are issued to the developer’s registry account; (4) the Liaison reconciles to internal Excel; (5) Sales’ Salesforce/HubSpot is updated. Manual sign-offs at multiple steps; no API.

B.7 BNDES / IDB loan covenant reporting (Brazil-specific especially)

Quarterly: financial statements + impact KPIs (ha planted, tCO₂ verified, ha under restoration). Annual: full audit + impact narrative. Any covenant breach triggers waiver discussions with Santander / BNDES (in Mombak’s case Santander provided the bank guarantee enabling Mombak to access the BNDES facility — BNDES note; Reuters on Santander/BNDES).

Part C — Time-and-motion estimates

The table below allocates ops hours by % of team time at three developer scales. Values are triangulated from BlueLayer/Permian customer story, Sylvera’s analyst commentary on data availability, Microsoft’s CDR procurement guidance, the 6–8-week issuance window data point, Carbonext’s stated 50-person methodology+GIS+community team (S&P Carbonext interview), and Mombak’s 350+ employees across 10 farms (Carbon Herald Mombak). Where direct LATAM data is missing, ratios are inferred from BlueLayer’s published case study language and stated as inference.

Inferred allocations within ops time (BlueLayer Permian case study describes the “before” state as manual spreadsheet entry across registry, sales, and inventory — implying a meaningful share of ops time in pre-OS state goes to data wrangling vs. value-add):

• Pre-software baseline: ~30–40% of compliance / sales / MRV time on data reconciliation, copy-paste between systems, and document gathering for buyer DD. (Inference from BlueLayer/CarbonHQ value-prop framing — direct LATAM time-survey data not public.)
• Post-software ceiling (Permian case study): “minimized possibility of errors,” “fewer errors, faster decisions” (BlueLayer Permian).

Part D — Pain points by persona (heatmap)

Symbology: ●●● = recurring/systemic, ●● = frequent, ● = occasional/role-specific.

Selected supporting evidence (per theme):

1. Document chaos. CarbonHQ founder framing: developer “drowned in Excel” (PropelAuth case). Permian: “manually entering data into complex spreadsheets” pre-BlueLayer (BlueLayer Permian).
2. Registry portal pain. Verra Project Hub now digital but every interaction is web-form-bound; submission ceremony described in Verra Project Hub announcement.
3. Multi-registry interop. Cercarbono–Ecoregistry alliance (Cercarbono); Cercarbono on S&P Meta Registry (S&P press release); BlueLayer dMRV for Puro (Carbon Herald Puro).
4. Audit pain. Verra VVB suspensions and 12-month validation timelines (Verra suspension notice; Sustain-Cert).
5. FPIC documentation. RRI carbon-rights report (RRI); UN-REDD (UN-REDD).
6. Buyer-side scramble. Microsoft 2–3 month / 6–9 month diligence cycles (Microsoft FY25 guidance PDF).
7. MRV reconciliation. Sylvera on missing shapefiles and “no response” from developers (Sylvera ratings process).
8. FX, tax, banking. Mayer Brown on Brazil Lei 15,042/24 + IBS/CBS uncertainty (Mayer Brown). Mombak’s USD-denominated offtake vs BRL costs (Reuters on Mombak/BNDES).
9. Methodology migration. Verra requantification procedure (Verra); VM0048 jurisdictional baselining (Space Intelligence).
10. Indigenous-language UI gap. Inferred from absence in publicly documented dMRV stacks (Pachama/Carbon Direct, BlueLayer, Boomitra, Sylvera, OFP) — none ship Yanomami/Kichwa/Quechua/Maya/Guarani localization. Mongabay-documented Cumbal scandal evidences the outcome of this gap (Pulitzer Cumbal).

Part E — What they would pay for (v1 LATAM project-developer OS)

Ordered by stated frequency of pain in the source material:

1. Single source of truth for project, inventory, and contract data — synced to registries. This is exactly the BlueLayer pitch and the language Permian’s Edward Rumsey uses: “For Permian Global, having a single source of truth meant fewer errors, faster decisions, and complete confidence in their carbon credit portfolio” (BlueLayer Permian). Tabular: project ↔ vintage ↔ buyer ↔ retirement, with registry sync. Highest pain × highest pay-willingness, validated by Permian’s choice to deploy.

2. Methodology-aware evidence templates with audit-log capture. BlueLayer’s dMRV Workspace promises “templates for evidence collection (soil samples, satellite imagery, lab certificates) and keeps a complete audit log, making third-party verification faster and easier” (CanvasBusinessModel BlueLayer). For LATAM, templates per VM0048 / VM0047 / Cercarbono / ART would close the audit-loop nightmare directly.

3. Registry submission orchestrator (Verra + Cercarbono + Puro + Isometric). Cercarbono’s Meta Registry bet (S&P press release) and BlueLayer’s Puro deal (Carbon Herald Puro) prove that registry-side connectivity is a real wedge. A LATAM-native player can be first to ship Cercarbono + Verra interop as a default, since 70%+ of Cercarbono’s portfolio is LATAM (Cercarbono Who We Are).

4. Live buyer-data-room generator from canonical project data. Microsoft / Symbiosis / Frontier diligence is now the gating revenue event (Microsoft FY25; Symbiosis quality). Sylvera’s “Connect to Supply” + BlueLayer’s API integration is the proof that buyers will pay for the wired developer side (Sylvera–BlueLayer).

5. Offline-first field-data app (KoboToolbox + Survey123 + Boomitra + OFP, unified). With multi-language support including Yanomami/Quechua/Maya/Guarani at minimum. Boomitra’s farmer-app pitch in Mexico/Argentina (Boomitra For Growers) and OFP’s Forester app (OFP) prove demand; LATAM-language localization is the moat.

6. FPIC consent ledger + benefit-sharing transparency module. Captures asamblea minutes, signatures, consent geofence, payment schedules, grievance log, with a community-facing read-only view. Closes the gap that produced the Cumbal scandal (Pulitzer Cumbal) and the Mongabay Carbonext / Stoppe stories (Mongabay 2024).

7. CFO module: USD/BRL/MXN/COP FX management, BNDES/IDB covenant pack auto-generation, and tCO₂-revenue ledger. Brazilian Lei 15,042/24 (Mayer Brown) makes this a Brazil-specific regulatory wedge. Mombak’s CFO Gabriel Silva’s “vertically integrated” framing implies an in-house build that a vertical SaaS could absorb (AXA IM Alts Q&A).

8. Methodology migration co-pilot (VM0048 / VM0047 / ABACUS / CCP). When Verra ships an update, every project re-baselines; today this work is consultant-led and bespoke. A guided migration tool with diff-views (“here is your old baseline, here is the jurisdictional allocation, here is the credit-volume delta”) would save R$200k–R$1M per project per migration, based on consultant rate inferences from SustainCERT requantification offering (SustainCERT).

9. MRV reconciliation layer that holds canonical project geometry. With versioned shapefiles, automatic propagation into satellite analytics (Earth Engine, Planet, MapBiomas), and reconciliation against plot-inventory CSVs. Sylvera’s stated pain is the proxy: missing shapefiles, no developer response (Sylvera).

10. Multi-registry portfolio dashboard with vintage-level forecast accuracy. Permian’s Rumsey: “The ability to quickly generate insights at both project and portfolio levels with BlueLayer has improved our decision-making and boosted our forecast accuracy” (BlueLayer Permian) — that exact value, LATAM-native and Cercarbono-aware.

The structural arbitrage for a LATAM-native v1: BlueLayer is London-headquartered and Permian-shaped (REDD+ Asia/Africa biased). A LATAM-native OS that ships Cercarbono + Verra + Brazilian tax/FX + indigenous-language FPIC + offline field capture by default has a defensible local wedge against BlueLayer’s eventual LATAM expansion.

Key citations

• BlueLayer customer story — Permian Global (testimonial source for inventory, audit, sales): BlueLayer Permian; Carbon Herald; TechCrunch BlueLayer; CanvasBusinessModel on BlueLayer; BlueLayer/Senken partnership; BlueLayer/Puro infrastructure deal.
• Sylvera × BlueLayer launch (Live Carbon Project Data Set, Feb 2025): Sylvera blog; QC Intel; Carbon Credits 2B.
• Sylvera ratings methodology / data-availability gap: Sylvera ratings process; Sylvera REDD+ Framework.
• Mombak (Brazil, Series A USV-led, BNDES Fundo Clima, Microsoft/Google/McLaren offtake, 350+ employees, doubling field team): Mombak.com homepage; Mombak news $100M strategy; Carbon Herald Mombak Series A; ESG News Mombak; BNDES press release; AXA IM Alts Q&A with Gabriel Silva; Reuters/Investing.com Santander+BNDES.
• Carbonext (Brazil, REDD+, CarbonEye, Janaina Dallan): Carbonext About; Carbonext High Integrity / CarbonEye; S&P Global Janaina Dallan interview; Sylvera IWD profile of Janaina; Esri WhereNext on Carbonext GIS workflow.
• re.green (Brazil, ARR, Atlantic Forest + Amazon, 30,000 ha, Mauricio Penteado COO ex-Suzano): re.green homepage; re.green People; Earthshot Prize 2025 Finalist; Mongabay 2026 on planting forests for credits.
• Toroto (Mexico, Conhuás ejido, Microsoft 234k credits): Toroto homepage; Toroto Conhuás project; Carbon Credits on Microsoft–Toroto deal.
• Quadriz (Paraguay, Corazón Verde del Chaco, public PDD): Quadriz site; Verra Corazón Verde case study; Quadriz PDD PDF.
• Biofílica/Ambipar (Brazil, REDD+ scale dev): Biofilica REDD+; Biofilica IETA membership.
• Permian Global (3rd-largest dev globally, BlueLayer customer): Permian About; Permian/Argus REDD+ conversation.
• Verra (VM0048, VM0047, ABACUS, Project Hub, fees, suspensions, requantification): Verra Project Hub; Verra VM0048 page; Verra VM0048/VMD0055 FAQ; Verra ABACUS; Verra VVB suspension; Verra requantification procedure; S&P Global on Verra fees 2025; QC Intel Verra issuance low.
• Cercarbono / EcoRegistry (Colombia-headquartered LATAM-dominant standard): Cercarbono homepage; Cercarbono–Ecoregistry alliance; S&P Global Meta Registry / Cercarbono; Cercarbono Who We Are.
• dMRV / MRV ecosystem (Pachama, Boomitra, OFP, Space Intelligence, MapBiomas): Carbon Direct acquires Pachama; Boomitra Science & Tech; Boomitra For Growers; Open Forest Protocol Medium overview; Space Intelligence VM0048 FAQ; MapBiomas Alerta method; MapBiomas Brasil; MapBiomas Colombia.
• CarbonHQ (founder Allan Fan “drowned in Excel”): PropelAuth case study; CarbonHQ site.
• Field-data tooling (KoboToolbox / ODK / ArcGIS Survey123): KoboToolbox docs; Esri ArcGIS Survey123.
• Buyer due-diligence ecosystem (Microsoft, Symbiosis, Carbon Direct, Frontier): Microsoft FY25 CDR procurement guidance PDF; Microsoft 2021 lessons paper; Symbiosis FAQs; Symbiosis Quality Criteria; Symbiosis first RFP insights; Carbon Direct technical diligence; Trellis on Symbiosis/Mombak.
• Issuance lifecycle / lag data: Carbon Insurance lifecycle 8 stages; Eos.com on issuance; Sustain-Cert on Verra; Ecobase Verra journey.
• Brazil tax/FX (Lei 15,042/24): Mayer Brown on carbon-credit consumption-tax reform; PwC Brazil tax summary.
• FPIC + indigenous-rights reportage (proves the gap): Pulitzer Center Cumbal investigation; Mongabay 2025 Chevron/indigenous land; SUMAÚMA “Carbon Cowboys”; Mongabay 2024 timber-laundering Carbonext; RRI carbon-rights report; UN-REDD social integrity; Forest Trends FPIC publication; Climate Action Reserve Mexico Forest Protocol ICVCM approval; Earthly Felipe Carrillo Puerto.
• Salaries (triangulated, no carbon-specific public data): SalaryExpert Brazil Director; SalaryExpert Brazil PM; Glassdoor SP Head of Projects; DigitalDefynd CSO benchmarks.
• ICVCM CCP / ABACUS quality labels: ICVCM Impact Report 2025; Calyx Global on ABACUS; BeZero on VM0047.

Method note on inference vs. evidence: Where the persona day-in-the-life timing, salary band, or pain-point ordering is asserted without a single primary citation, the assertion is triangulated from (a) BlueLayer/CarbonHQ customer-discovery framing, (b) Sylvera analyst commentary on data-availability friction, (c) Carbonext/Mombak/re.green/Toroto/Quadriz public team statements, (d) Microsoft/Symbiosis published diligence guidance, (e) Carbon Pulse / S&P Global / Mongabay / SUMAÚMA reportage. Direct LATAM operator quotes — Janaina Dallan (Carbonext), Mauricio Penteado (re.green), Gabriel Silva (Mombak), Edward Rumsey / John Peachey / Joshua Holland (Permian Global, REDD-globally relevant) — are cited verbatim where used. The Indigenous-language UI gap, FPIC paper-bound process, and methodology-migration cost ranges are inferences from the absence of any documented LATAM-native software shipping these features today; the inference is so flagged in-line.