Sentinel Operating
Mid-cap industrial operator · 14 facilities
From a 47-tab quarterly Excel to a defensible Scope 1-2-3 dashboard
Produce defensible Scope 1-2-3 emissions reports without an army of consultants.
A mid-cap operator needed to publish defensible Scope 1-2-3 emissions every quarter. The existing process was a quarterly Excel scramble across 14 facilities. We built a small data platform and a reporting dashboard that mirrors the GHG Protocol categories.
New · Climate / ESG
Scope 1.
Produce defensible Scope 1-2-3 emissions reports without an army of consultants.
Sample mockup · illustrative only
- Industry
- Climate / ESG
- Timeline
- 5 weeks
- Team
- 3
- Service
- Web + Software
- Project tier
- Web App MVP / $19,995 + Software / $9,995
The Problem
What was broken.
Each facility submitted a different Excel template every quarter. Emission factors were applied inconsistently. The sustainability team spent six weeks per quarter consolidating, and the auditors still flagged inconsistencies. Investors had started to ask harder questions and the team needed a defensible story.
Our Approach
How we framed it.
Modeled the data layer against the GHG Protocol categories explicitly — Scope 1 (direct combustion + fugitive), Scope 2 (electricity location + market), Scope 3 (15 categories with a per-category methodology note). dbt models with full lineage. Dashboard surfaces both the number and the methodology behind it.
Capability proof
What this case demonstrates.
This case makes the hidden work visible: strategy, architecture, delivery control, quality evidence, and handoff.
01 / Product judgment
Problem framed before UI
Each facility submitted a different Excel template every quarter. Emission factors were applied inconsistently. The sustainability team spent six weeks per quarter consolidating, and the auditors still flagged inconsistencies. Investors had started to ask harder questions and the team needed a defensible story.
02 / Technical depth
8 stack decisions
Next.js 15, TypeScript, Postgres, dbt, Snowflake, Recharts
03 / Delivery discipline
4 delivery checkpoints
Methodology workshop / Schema + dbt models / Facility submission UI
04 / Handoff quality
6 shipped artifacts
Snowflake schema with versioned emissions factors / dbt models with lineage + tests / Per-facility submission UI with audit log
Production artifacts
Inspect the work behind the visible result.
Each case exposes the surfaces, systems, evidence, and handoff package that make the shipped product usable after launch.
Experience layer
Buyer or user surface
Live Scope-3 dashboard with category drill-down, top-emitter alerts, GHG Protocol auto-mapping.
Proof 01
Produce defensible Scope 1-2-3 emissions reports without an army of consultants.
Proof 02
Two days with the sustainability lead and the external auditor walking through GHG Protocol category by...
Proof 03
Per-facility submission UI with audit log
Production signals
Observable
Errors, logs, alerts, or dashboards included.
Risk-aware
Security and compliance boundaries named.
Release-ready
Deployment or store-release path included.
Handoff-ready
Owner can keep operating after delivery.
Before / after · product UI mockup
Industry · Climate / ESG
Before:Scope-3 emissions calculated quarterly in a 47-tab Excel sheet — wrong half the time.
After:Live Scope-3 dashboard with category drill-down, top-emitter alerts, GHG Protocol auto-mapping.
How the engagement ran.
- 01Week 1
Methodology workshop
Two days with the sustainability lead and the external auditor walking through GHG Protocol category by category.
- 02Week 2
Schema + dbt models
Built the canonical schema in Snowflake, modeled emissions factors with effective dates.
- 03Week 3-4
Facility submission UI
Web form per facility with category-aware validation. Versioned submissions, audit log on every edit.
- 04Week 5
Dashboard + handoff
Dashboard with drill-down to source rows. Handoff playbook for the next reporting cycle.
- 1
Week 1
Methodology workshop
Two days with the sustainability lead and the external auditor walking through GHG Protocol category by category.
- 2
Week 2
Schema + dbt models
Built the canonical schema in Snowflake, modeled emissions factors with effective dates.
- 3
Week 3-4
Facility submission UI
Web form per facility with category-aware validation. Versioned submissions, audit log on every edit.
- 4
Week 5
Dashboard + handoff
Dashboard with drill-down to source rows. Handoff playbook for the next reporting cycle.
Deliverables
What we shipped.
- ✓Snowflake schema with versioned emissions factors
- ✓dbt models with lineage + tests
- ✓Per-facility submission UI with audit log
- ✓Investor-facing dashboard with drill-down
- ✓Methodology note appendix versioned alongside data
- ✓Handoff runbook for the next reporting cycle
Outcomes.
engagement targetsPlan: quarterly close goes from ~6 weeks to ~5 days
Plan: every emissions number traceable to its source rows + factor + methodology note
Plan: methodology notes versioned alongside the dbt models
Plan: auditor-friendly: lineage graph generated per report
Plan: facility submission UI mirrors GHG Protocol categories explicitly
Honest challenges
What we got wrong (or almost wrong).
The pretty version of any case study skips this part. We don't.
- 01
Emission factors update annually mid-cycle — we modeled them with effective dates so historical reports stay stable.
- 02
One facility's energy bills came as PDFs; built a small parser with a human-in-the-loop review queue rather than over-automating.
- 03
Scope 3 categories 1 and 11 are inherently estimate-heavy; surfaced uncertainty bars on the dashboard so investors could see what was modeled vs. measured.
In our own words
ESG numbers earn investor trust by being defensible, not by being big. Anchoring every figure to a dbt lineage graph and a versioned methodology note turned an audit conversation into a five-minute walk-through.
From the Hayaiti team
Engineering · design · security
Technical blueprint
How the work holds together.
Buyers should see that the visual layer is backed by architecture, quality gates, and operational ownership.
Experience
1Application
2Data
3Operations
4Security
5Stack used
8 technologiesRelated
Other cases like this.
Northwind Studios
Onboarding rebuild · Series A SaaS
Cut signup-to-aha-moment from 9 minutes to under 90 seconds.
HealthcareHelix Health
HIPAA-ready intake portal
Replace clipboard intake with a 7-minute, accessible, HIPAA-ready web flow.
FintechFoundry Capital
Broker API + nightly reconciliation
Stand up a reliable broker integration with nightly reconciliation in three weeks.
Want a case study like this?
Want this level of production quality on your project?
Send a short brief and we'll reply with scope, timeline, price direction, and the first technical recommendation.