Scope 3 Emissions: The Hidden Challenge Most Startups Ignore
When most founders think about carbon emissions, they think about electricity bills and maybe business travel. That's Scope 1 and Scope 2. Controllable, measurable, and honestly, pretty small for most software companies.
Scope 3 is different. It's everything else — and for most tech companies, it's 80-95% of their actual climate impact. It's also the category that's driving investor due diligence, CSRD reporting requirements, and customer procurement decisions. And it's the one almost no startup has figured out.
This post explains what Scope 3 actually is, why it's suddenly urgent for growth-stage companies, and what a realistic data collection strategy looks like.
The GHG Protocol: How Emissions Are Categorized
The Greenhouse Gas Protocol Corporate Standard is the baseline framework almost every reporting regime references — GRI, ESRS, TCFD, and SEC climate disclosure rules all build on it. It divides emissions into three scopes:
Scope 1: Direct emissions from sources your company owns or controls. A server room with diesel backup generators. A company vehicle fleet. On-premise HVAC systems. For most software companies, this is near zero.
Scope 2: Indirect emissions from purchased energy — primarily electricity. Your AWS bill generates Scope 2 emissions at the data center level. This is now well-understood and often market-based (you can purchase renewable energy certificates to reduce it).
Scope 3: Everything upstream and downstream in your value chain that you don't directly control. This is where it gets complicated.
The GHG Protocol divides Scope 3 into 15 categories:
| Category | Direction | Description | |----------|-----------|-------------| | 1. Purchased goods and services | Upstream | Emissions from producing what you buy | | 2. Capital goods | Upstream | Emissions from producing your hardware/equipment | | 3. Fuel and energy activities | Upstream | Extraction/transport of fuels you consume | | 4. Upstream transportation | Upstream | Freight before it reaches you | | 5. Waste generated | Upstream | Emissions from disposing your waste | | 6. Business travel | Upstream | Flights, hotels, rental cars | | 7. Employee commuting | Upstream | Your employees' daily travel | | 8. Upstream leased assets | Upstream | Leased assets operated by others | | 9. Downstream transportation | Downstream | Shipping your products to customers | | 10. Processing of sold products | Downstream | How customers further process your product | | 11. Use of sold products | Downstream | Lifetime emissions from using your product | | 12. End-of-life treatment | Downstream | Disposal of your products | | 13. Downstream leased assets | Downstream | Assets you own but tenants operate | | 14. Franchises | Downstream | Franchisee operations | | 15. Investments | Downstream | Portfolio company emissions |
For a B2B SaaS company, the most material categories are typically: 1 (cloud compute, SaaS tools, contractors), 6 (business travel), 7 (employee commuting), and 11 (customer energy consumption from running your software).
Why Scope 3 Is Suddenly Urgent for Growth-Stage Companies
Three years ago, Scope 3 was a Fortune 500 problem. Today it's filtering down fast, for three reasons:
1. CSRD and ESRS E1 Create Supply Chain Pull
Under ESRS E1 (Climate), large EU companies required to report under CSRD must disclose their Scope 3 emissions across all 15 categories deemed material. To do that, they need data from their suppliers — which means you.
If your product is used by a company with €250M+ revenue and EU operations, expect to receive supplier questionnaires asking for your Scope 1, 2, and 3 data. Your inability to answer credibly becomes a procurement risk. Some enterprise procurement teams are already adding "ESG data sharing" as a contract requirement.
2. Series B Investors Are Asking
The LP base of major growth equity funds has shifted. Institutional LPs — pension funds, endowments, sovereign wealth funds — have their own ESG reporting obligations. This pressure flows down: VCs now ask portfolio companies for ESG metrics as part of annual reporting. By Series B, expect your investor data room to include basic carbon footprint data. By Series C, expect it to be audited.
3. The SEC Climate Rule (For US Companies)
The SEC's climate disclosure rules (still in litigation, but directionally durable) will require large accelerated filers to report Scope 3 if material. For software companies with significant cloud infrastructure costs, it almost always is. Companies planning IPO tracks need to start building Scope 3 measurement capability now.
Why Scope 3 Data Collection Is Hard
The reason most startups haven't tackled this isn't laziness — it's genuine technical complexity.
The Boundary Problem
Who's in your value chain? A 10-person startup might use 40+ SaaS vendors, 3 cloud providers, a network of freelance contractors, and ship physical hardware. Each of those represents a Scope 3 Category 1 emission. Mapping them all and deciding which are "material" requires both judgment and data.
The Data Availability Gap
Your cloud provider knows the energy mix of their data centers. But they may not share it in a format you can use. Most vendors don't publish emission factors for their services. You end up estimating — using spend-based methods (convert $ spent to kg CO₂e using industry-average emission factors) rather than activity-based methods (actual energy consumed × real emission factor).
Spend-based methods are inaccurate by design — they can be off by 2-10x for specific categories — but they're often the only practical starting point.
The Double-Counting Problem
Scope 3 emissions can overlap between companies. Your cloud provider's Scope 1 and 2 emissions are your Scope 3 Category 1. If your enterprise customer is also measuring Scope 3, your product's energy consumption appears in their Category 11. This double-counting is intentional in the framework — it's about driving accountability across the entire chain — but it means aggregating industry numbers is meaningless.
The Emissions Factor Library Gap
Emission factors translate activity data (kWh, km, $ spend) into CO₂e values. You need factors specific to your geography, time period, and industry. Sources include:
- DEFRA (UK, high quality)
- EPA (US, decent coverage)
- EXIOBASE/EORA (global multi-regional input-output tables, spend-based)
- ecoinvent (gold standard for lifecycle data, expensive license)
- Climatiq API (aggregated, API-accessible, good for SaaS tooling)
Using the wrong emission factor — or factors from the wrong year — can materially misstate your footprint.
A Realistic Scope 3 Data Collection Strategy
Here's how we recommend growth-stage companies approach this:
Phase 1: Materiality Assessment (Week 1-2)
Don't try to measure everything. Use a spend analysis to identify which Scope 3 categories are likely material (>5% of total estimated emissions). For a 50-person SaaS company, this almost always narrows to:
- Cloud infrastructure (Category 1)
- Business travel (Category 6)
- Employee commuting (Category 7)
- Use of sold products (Category 11, if you have energy-intensive features)
Everything else — packaging, downstream logistics, franchises — is typically immaterial and can be marked as "not applicable with rationale."
Phase 2: Data Source Inventory (Week 2-3)
For each material category, identify data sources:
Cloud infrastructure: AWS Cost and Usage Reports (CUR) give you service-level spend. AWS Customer Carbon Footprint Tool gives you estimated Scope 1+2 for your usage, broken by region. GCP and Azure have equivalents. Export monthly.
Business travel: Your corporate card data (Brex, Ramp) + travel booking platform (TripActions, Navan). Most have ESG export features now. Get distance data, not just spend — distance × emission factor is more accurate than spend-based for flights.
Employee commuting: Survey-based. Annual or semi-annual surveys asking employees their commute mode, distance, and frequency. Annoying but effective. Sample size of 30%+ is sufficient for a credible estimate.
Purchased SaaS/services: Spend-based for the long tail. Use EXIOBASE or Climatiq's spend-based factors for "Computer programming, consultancy" and "Data processing, hosting" sectors. Not precise, but defensible.
Phase 3: Calculation and Normalization
Once you have activity data, apply emission factors and normalize to CO₂e (carbon dioxide equivalent — accounts for other greenhouse gases like methane and nitrous oxide using their 100-year global warming potential).
Build this as a structured data model:
activity_data {
category: string // "cloud_compute", "business_travel"
source: string // "aws_cfr_export", "navan_export"
period: date_range
quantity: float
unit: string // "kWh", "passenger_km", "USD"
emission_factor: float // kgCO2e per unit
emission_factor_source: string
co2e_kg: float // quantity × emission_factor
confidence: enum // "measured", "estimated", "spend_based"
}
Total footprint = SUM(co2e_kg) across all records, grouped by scope.
Phase 4: Audit Trail and Documentation
Even if you're not legally required to have your Scope 3 verified, building an audit trail now saves pain later. Document:
- What data sources you used
- What emission factors you applied and why
- What you excluded and why (materiality reasoning)
- Who reviewed and approved the numbers
- What period the data covers
Store this alongside your raw data exports. When an enterprise customer sends a supplier questionnaire or an investor asks for your methodology, you can answer credibly.
Automation Workflows for Scope 3 Data Collection
Manual Scope 3 data collection is where most companies get stuck. Automation workflows that materially reduce the burden:
- Cloud spend auto-tagging — Tag cloud resources by product line at source; automated exports then split emissions by business unit without manual re-allocation
- Travel data pipeline — Direct API integration with Navan or Concur exports flight/hotel bookings nightly, calculates emissions, and stores results with source reference
- Commute survey automation — Scheduled survey distribution and automatic result ingestion into your GHG model
- Supplier questionnaire workflows — Automated reminders and response ingestion for annual supplier data requests
If your procurement processes already intersect with SOC2 vendor security reviews, bundling ESG data requests into your existing vendor assessment workflow is efficient — and positions your company as a sophisticated buyer. Our Security & SOC2 Compliance offering covers vendor security assessment automation alongside ESG supplier workflows.
Tools That Help
The landscape for Scope 3 software has matured:
Watershed — Enterprise-grade, used by Stripe and Airbnb. Strong on supply chain. Expensive (~$50-100k/year) but integrates directly with accounting systems and generates auditable reports.
Persefoni — Strong TCFD and CSRD alignment. Good for companies with complex financial structures. Audit-ready output.
Greenly — Better price point for Series B companies ($15-30k/year). Good API integrations for cloud spend. Has a startup plan.
Climatiq API — If you want to build your own calculation layer, this gives you a global emission factor database via API. Pay-per-call. Used by a lot of ESG SaaS companies internally.
Spreadsheet + Climatiq — Totally valid for early-stage. A well-structured Google Sheet with Climatiq API calls for emission factors is defensible and cheap. We've built this for clients.
What Investors Actually Want to See
At Series B, you don't need a fully audited Scope 3 inventory. You need:
- A documented baseline — even if spend-based, covering your top 3 material categories
- Year-over-year tracking — showing you're measuring consistently (trajectory matters more than accuracy)
- A reduction narrative — what you're doing to reduce, even if small (renewable energy for cloud, remote-first policy for commuting)
- Awareness of your Category 11 exposure — if customers run your software at scale, what's the energy profile?
Series C and beyond, expect pressure toward third-party verification and CSRD-aligned ESRS E1 disclosure if you have EU operations.
The Bottom Line
Scope 3 is genuinely hard. The data is fragmented, the methodologies are imperfect, and the standards are still evolving. But "it's hard" is no longer a sufficient reason to skip it. Enterprise procurement teams, institutional investors, and EU regulators are all pulling in the same direction: they want supply chain emission transparency, and they want it now.
The companies that build Scope 3 measurement capability at Series B will be in a dramatically better position at Series C than those scrambling to reconstruct two years of data under investor pressure.
100xAI builds ESG data infrastructure for growth-stage companies — from materiality assessments and data source mapping to calculation pipelines and investor-ready reports. If you're approaching Series C or preparing for CSRD supplier questionnaires, talk to our ESG team.
Related Resources
More articles:
Our solutions: ESG Compliance Engineering · Security & SOC2 Compliance
Glossary:
Comparisons:
Free Tool: Use our free ESG checklist to ensure your Scope 3 reporting is investor-ready. → ESG Compliance Checklist