Most of that attention goes to hardware and infrastructure, and hardware has genuinely become more efficient. But the software layer, where a lot of the impact is decided, stays an underused lever. Developers rarely have the tools, metrics or guidance to factor sustainability into daily work. That is the gap we set out to close.
Two tools, one delivery chain
Green IT tends to fail in the same place most transformations fail: between the people who set the direction and the people who do the work. Project managers need a method to lead it. Developers need tools to apply it while they code. We built one for each, designed to work together.
For developers: measure the code, then improve it
The developer tool puts a number on something most teams never see. It monitors the front end and back end of an application, collects performance and energy metrics, and estimates the energy and carbon behind that activity. From there it calculates a Green Score, an aggregated measure that lets developers visualize their impact rather than guess at it.
Alongside the score sit concrete recommendations and a best-practice checklist. The guidance starts generic and becomes more tailored to the context, the programming language and the IDE, because advice that fits the environment gets used, and advice that doesn't get ignored. Real care went into the interface, since adoption is what makes any of this count.
For project managers: make it a method, not a memo
Sustainability criteria that live outside the workflow don't survive it. So the second tool gives project managers, product owners and change managers a methodology they can actually run.
It is built on the ADKAR change model and aligned with Agile, which matters because that is where software work already happens. In practice it moves through six steps: prepare the support framework, raise awareness of why the transition matters, activate motivation to engage, build the knowledge and skills needed through training, support the operational deployment, then evaluate and improve. Each step comes with action sheets and deliverables, including how to assess a project's carbon footprint and turn that diagnosis into a prioritized plan. A paper detailing the framework is forthcoming
Why this matters now
Regulatory pressure is rising and energy costs are climbing. Reducing the environmental impact of digital services now sits alongside CSR goals and client expectations, not below them.
Hardware efficiency has done its part. The software layer is the lever still sitting mostly unused. Measuring impact at the code level, and giving teams a method to act on it, is how Green IT moves from a slide to something a team runs every day.
