Andreas Petrovits

01

greenimpact.io

End-to-end product design

A first-build SaaS toolkit turning CSRD compliance into something SMEs could actually finish — guided onboarding, an ESG dashboard, and a bookable specialist for the moments the FAQ couldn't cover. Tested internally, then in a closed beta with 40 SMEs.

Client
greenimpact.io
Year
2025
Role
Visual & UX designer
Status
Closed beta · not publicly launched

greenimpact.io loop

greenimpact.io interface walkthrough

The brief

greenimpact.io was built to give SMEs one place for sustainability reporting instead of ten: a Green Impact Score, CSRD templates, CO2 tracking, and a specialist to call when the software alone wasn't enough. It was the platform's first version — nothing existed yet to react to, so every screen had to work for someone with zero CSRD knowledge.

The problem

SME owners were pulling emissions data from utility PDFs, old Word docs and email threads, with no idea if any of it added up to a compliant report. 78% called their ESG data scattered; 40% couldn't produce a usable report without outside help.

My role

Visual & UX designer, working alongside product managers, developers and sustainability engineers. I owned onboarding and interface design end-to-end, partnering closely with the sustainability engineers to keep the CSRD logic honest.

Research artefact — competitive audit matrix
(Normative, Valified, Briink, Ignite) annotated with the SME gap

Where existing tools assumed CSRD literacy, we saw the opening to design for zero prior knowledge.

Early flow diagram — configurable dashboard (rejected)
vs. linear guided wizard (shipped)

Testing showed flexibility raised drop-off: users didn't yet know what they needed to configure.

Process

01

Discovery

Interviews with owners, compliance officers and sustainability managers, plus a 50+ respondent survey and an audit of Normative, Valified, Briink and Ignite. The insight that changed direction: SMEs weren't short on information about CSRD — they lacked confidence they were doing it right. The product's job was to remove ambiguity, not add more explanations.

02

Structure & flows

The first version was a flexible, configurable dashboard. It tested badly — people didn't know what to configure. We rebuilt around one linear path: a guided CSRD wizard that produces a working report before the user ever sees an empty dashboard.

03

Interface & system

Role-based views for compliance officers, sustainability managers and owners, plus a shared component library so report layouts stayed consistent. Templated rather than fully custom report branding — a deliberate trade-off to keep the first build testable.

Wireframe — onboarding wizard,
steps 1–3
Component system —
role-based views & report blocks
Final screen — Green Impact
Score dashboard
"Interpreting CSRD feels like navigating a labyrinth without a map."
— SME owner, user interview

The design

The onboarding wizard turns "I don't know where to start" into a first compliant data point, one plain-language question at a time — the report visibly fills in behind it as the user answers.

The standout feature: a bookable specialist. When the FAQ and walkthrough videos weren't enough, users could schedule real time with someone who'd talk them through their specific case — something none of the competitor tools offered.

Visibility mattered almost as much as compliance. The Green Community turns a finished report into something shareable, not just filed away.

Hero screen — CSRD onboarding wizard,
question + live report preview

Every question maps visibly to a filled-in section of the report — progress the user can see, not just trust.

Detail — booking a specialist,
triggered from the FAQ/video screen
Detail — mobile, Green Community
profile & shared progress update

Outcome

This was tested internally first, then opened to a closed beta of 40 SMEs. Onboarding completion rose and half the beta group went on to share progress in the Green Community — signs the guided approach was working. But greenimpact.io never reached public launch: building the specialist-booking and support tooling reliably enough to run at scale proved harder than the beta timeline allowed, and the project wrapped as a design and validation exercise rather than a shipped product.

40SMEs in the closed beta
+30%Onboarding completion vs. the original dashboard-first flow
50%Of beta users shared progress in the Green Community