What we are building, and in what order.

Read this first.

The phases

1. 1Foundation built

   Platform foundation and the core ESG journey

   The foundations everything else depends on: one shared way of organising ESG information and the evidence behind it, a history that is added to rather than overwritten, access control for each organisation, and the core working journey running from start to finish — Configure, Generate Requirements, Collect, Validate, Resolve Gaps, Calculate, Review, Approve & Lock.

   This is the stage where telling missing apart from zero is built in rather than added on. Missing, unavailable, not applicable and approved estimate exist as distinct answers from the very beginning, because adding them later would mean rebuilding everything above them.

   It also carries the parts of a service an enterprise buyer asks about before anything else: how each organisation is kept separate, how people sign in, how the platform is operated and recovered, and the connected desktop client that works against the same service rather than holding a copy of its own.

2. 2Foundation built

   Full ESG breadth — social, governance, materiality and suppliers

   The same approach extended across the rest of ESG rather than separate tools placed alongside it. Social and governance topics carry the same evidence, ownership and approval discipline as environmental data, on one shared record.

   Double materiality assessed in both directions — impact on the world and financial impact on the organisation — against that same record. Targets with their baselines, the initiatives beneath them, and progress read from the evidence rather than from a slide. Suppliers taking part through structured requests, with evidence attached as it is submitted, findings and corrective actions.

   What this phase does not mean is a finished product. The foundation beneath these areas is built and tested; the customer-facing screens, reports and day-to-day workflows on top of it are the work of the phases below.

3. 3In progress

   Framework mapping

   Structuring the record so it can answer what a disclosure framework asks for, without keeping a separate copy of the truth per framework. Each mapping is versioned, and where a requirement has no mapping yet the platform is built to say so rather than leave a gap that reads like a zero.

   The GHG Protocol and IFRS/ISSB S1 & S2 mapping packs are built and tested. GRI, ESRS in its CSRD context, and SASB sector overlays are being built now. TCFD-style climate disclosure, CDP, UN SDG mapping and configurable regional templates follow after those.

   A mapping is not a certification, not a statement of compliance and not an assurance opinion. It structures the information a framework asks for; deciding what applies to an organisation remains a human and professional judgement.

4. 4Next

   Enterprise reporting, the evidence pack and change review

   Turning a closed period into the documents an organisation actually has to produce: the GHG Inventory, the Executive ESG Summary, the Board & Risk Pack, the Detailed Calculation Annex, and the Audit Evidence Pack — the last of these readable both by a person and by a reviewer’s own tools.

   The goal for this stage is repeatability. A report drawn from a closed period should give the same numbers whenever it is run, and every figure in it should lead back through the calculation and the method to the evidence it rests on. It also brings the assurance and submission workspaces, so a reviewer works against a closed period in a shared workspace rather than through an email thread.

   And the part that begins after the report is filed: when a source figure, an emission factor, a method or an organisational boundary changes, the platform is being built to show which current and draft outputs that change reaches, and what needs looking at again. Periods already closed and locked are not rewritten — a correction is made as a governed revision, in the open.

5. 5Planned

   Industry packs, integrations and release readiness

   The industry packs we build and verify, carrying the methods and activity types a particular industry needs — added to the same platform, never a separate product. The first three are Financial Services, Real Estate & Facilities, and Construction & Infrastructure; the rest follow on the same factory, and any industry without a named pack is served by the universal enterprise pack rather than turned away.

   Connections to the systems the data already lives in — finance, HR and cloud among them — where each connector is tested against the real system before it is claimed. Onboarding new organisations, and administration at scale.

   And security hardening as a distinct, deliberate stage rather than an assumption: penetration testing, formal review of how each organisation’s information is kept separate, and pursuing the independent certifications an enterprise buyer will ask for. We hold none today. When we hold one, we will name the certification, the certifying body and the date.

We will update this. We will not backdate it.

Planned launch — January 2027.