Skip to content
East Wolf
Industries — Sustainability & ESG

Reporting the world
now requires.

Carbon accounting and ESG disclosure software. This category exists because legislation created it, which means the demand is not discretionary and the numbers have to survive an audit. We build the systems that produce them.

Carbon emissions reporting SaaS · Enterprise ESG reporting platforms
§ 01What we build here01 / 03

Six things
this work is made of.

An ESG platform is a data problem wearing a reporting interface. These are the parts we are repeatedly asked to build, in the order they tend to become difficult.

01

Emissions accounting

Scope 1, 2 and 3 calculation over whatever the organization can actually produce — meter readings, invoices, travel records, supplier returns. The arithmetic is the easy half.
02

Getting the data in

The numbers live in utility bills, ERP exports, questionnaires and spreadsheets nobody owns. Most of the engineering is pulling them out of there the same way every period.
03

Factors and methodology

Emission factors are versioned data with effective dates. A platform that hardcodes them cannot restate last year when the method changes, and the method changes.
04

Consolidation across a group

Enterprise reporting is a tree: sites, subsidiaries and joint ventures, each with its own boundary and its own share. Roll-up rules belong in the model, not in a final spreadsheet.
05

Disclosure output

Assembling the report itself, and the exports a reviewer asks for. The deliverable is a document with a date attached, not a dashboard.
06

Evidence and audit trail

Every published figure traces back to the file, reading or entry it came from, with who changed it and when. That is what separates reporting software from a calculator.
§ 02How it is engineered02 / 03

Numbers that
get audited.

None of this is engineered for a demo. A published ESG figure is a statement the company signs, read by someone whose job is to disbelieve it. That changes what the software has to do.

01

Restatement is a normal operation

Boundaries move, factors are revised, a supplier finally sends real data. The system has to recompute a closed period and show what changed, without losing what was originally published.
02

Estimated is not measured

Gaps are unavoidable, so they are labelled. Every value carries how it was obtained — measured, calculated or estimated — and that label survives into the report instead of being flattened on the way.
03

The deadline is in the legislation

Reporting periods are fixed dates set by someone else. Delivery is planned backwards from them, which means the unglamorous parts — imports, permissions, exports — get built first rather than last.
04

Multi-tenant from the first commit

These are enterprise SaaS products, not internal tools. Tenant isolation, role boundaries and per-tenant configuration are decisions taken at the start, because they cannot be retrofitted.
Note

The engagements behind this page are still being written up, and we will not publish a case study we cannot evidence. So there are no logos, no figures and no named platforms here yet. Ask on a call and we will walk you through the architecture and what we would reuse.

§ 03Start here03 / 03

Start with
one report.

Tell us what you have to report and what you are reporting it from today — a spreadsheet, a half-built platform, or nothing yet. We will tell you how we would build it, how long it takes and what it costs.

Twenty years of delivery and 100+ projects delivered. The core team is small and senior, in Bucharest, with a network of 50+ engineers to draw on when a reporting deadline needs it.

Start a conversationhello@east-wolf.com
Back to Home