← Watershed
Something new at Watershed

Compare portfolio changes without rebuilding the analysis in Excel

You’re the software engineer. Your team is in the room. Printed Oct 15, 2026.

Portfolio decisions need emissions totals and data quality to move together.

Fast scenario comparison protects investment review speed, while traceable portfolio inputs protect confidence in the result.

Who you’d be doing this for

“The investment committee asked what the rebalance does to data quality, and I had three spreadsheets open.”

Athena Alvarez · Sustainability Reporting Manager

Prepares financed-emissions analysis for an asset manager's investment and disclosure reviews.

What is at stake

Reporting managers are exporting portfolio data because proposed holding changes and PCAF scores cannot be compared together. You have to weigh a useful first scenario workspace against results users can trace back to the underlying data.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • fast portfolio comparison vs traceable underlying data
  • simple decision surface vs visible methodological uncertainty
  • pilot learning speed vs durable frontend architecture
  • emissions movement vs PCAF score interpretation

Why Watershed

Financial-institution customers already model portfolios, assets, and holdings alongside financed-emissions data.

Written with these in mind

product-minded full-stack engineerdata-intensive frontend engineerclimate technology builder

Not your kind of problem? 12 more at Watershed, or browse every organization.

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.