An energy supplier, grid operator or renewable energy project developer in the Netherlands runs on a dense stack of industry systems. Schneider Electric EcoStruxure or Siemens Spectrum Power for grid and SCADA operations, ABB Ability and Hitachi for substation automation, Itron and Landis+Gyr for smart metering and MDM, Utiligize for network planning, EnergyCRM for customer administration and switching, plus the usual ERP and CRM layer for finance and sales. For standard utility processes, that stack works well.
We don't replace those platforms. We're asked to build the layer around or on top of them: a custom energy management platform that reports across multiple sources, a customer portal for consumption insight and switching, software for energy installers that links certification and materials to scheduling, a trading cockpit built on top of EPEX and ICE Endex, or an ESCO monitor that tracks savings against baseline for each performance contract. For the broader context of what we do in software development, see our main page.
The target group is broad. Energy suppliers such as Vattenfall, Eneco, Greenchoice and Budget Energie. Grid operators such as Stedin, Liander, Enexis, TenneT and Gasunie. Renewable energy project developers in solar, wind, geothermal and battery storage. Energy cooperatives, ESCOs with performance contracts, solar panel and heat pump installers, EMS and ESS providers, energy traders in gas, electricity, CO₂ allowances and Guarantees of Origin, property managers with an energy portfolio, and large energy users under MJA3. Each of these roles has a differently configured systems landscape, but the pattern is the same: a dense enterprise core surrounded by workflows that are difficult to squeeze into off-the-shelf packages.
At the same time, the entire sector is moving further into the energy transition. Decentralised storage, vehicle-to-grid, congestion management, hybrid heating projects, and solar parks participating in imbalance markets. These new data fields, contract types and KPIs are not yet structurally covered by packages such as EcoStruxure, Spectrum Power or Itron, while your operation still needs to measure them, invoice them and demonstrate them to ACM or an EED auditor. A lightweight custom layer on top of your existing systems is often more practical than waiting for your vendor to release a module for it.