Industry · Utilities

Custom utilities app development. For energy, water, gas and heat.

We build apps for utility companies that do more than display an invoice. Hourly smart meter data, dynamic pricing on the EPEX feed, outage reporting with location, demand response with opt-in and solar feed-in in a single customer flow — built within the framework of the Dutch Energy Act, ACM supervision, GDPR and the Heat Act 2. For energy suppliers, grid operators, water companies, heat networks, energy cooperatives and aggregators.

SectorEnergy & gas
SectorWater
SectorHeat
SectorSmart meters & EV

The Dutch utilities sector in numbers.

~8M
Electricity and gas connections
~10
Water companies nationwide
~600k
Connections to a heat network
2,3M+
Households with solar panels

Source: ACM Energy Monitor 2024, Vewin Drinking Water Statistics 2024, CBS Renewable Energy 2024.

A legacy portal can no longer do what customers expect in 2026.

Most utility portals were built around one central flow: show the invoice, renew the contract, submit the annual meter reading. That was fine when energy was a static product with one tariff per year, one supplier per home and a meter reader who came to the door. In today's market, it no longer works.

Customers want to see their real-time usage by the hour, follow their dynamic tariffs, know how much they have fed back into the grid and when their home battery can charge most cleverly. They want to report an outage in two taps, not through a seven-screen form. A house move should be completed in a single session, with automatic meter handover. A choice between fixed, variable and dynamic tariffs should be easy to explain, without the customer first having to read a four-page tariff document.

At the same time, back-end complexity has grown considerably. There are more data streams (P4 for hourly data, market communication via EDSN, EPEX prices, IoT feeds from solar inverters, charge points and home batteries), more regulators with more requirements (ACM, GDPR, the Energy Act 2025, Heat Act 2), and more customer segments that each need a different flow. A standard portal that tries to do everything does nothing well.

A custom app tackles this differently: the flow sits close to the smart-meter data, EPEX prices and the CRM, and your customer service team no longer gets the same ten questions every day about usage peaks or balance. Overall: fewer calls, a higher NPS, and a connections database that stays intact through a tariff switch or merger. What's more, a dedicated customer app is increasingly becoming a differentiator. In a market where tariffs can be compared on comparison sites within seconds, the quality of the digital experience is the most important retention tool left.

Software that fits your segment.

An energy supplier has a different customer flow from a grid operator or a heat network operator. For each segment, we show what we typically build.

Energy supplier

For mid-market energy suppliers and energy cooperatives, a dedicated customer app is the most important retention tool. The combination of dynamic pricing, feed-in and home batteries has turned the customer from a passive consumer into an active participant, and they want to see everything that's happening on a single screen.

We build apps that pull smart-meter data from P4/P1 channels, visualise EPEX hourly prices, apply net metering correctly and optionally offer a demand-response flow for customers with a charge point or battery. Our deep energy-domain knowledge comes from our energy software projects, in which we have previously worked on back-office systems, billing integrations and market communication via EDSN.

For grid operators, the emphasis is on outage reporting, planned maintenance and connection requests: flows where the number of interactions per customer per year is lower, but where every contact moment has a high impact. For heat networks, the focus is on transparency of tariff components, linked to meter readings per delivery point.

  • Hourly usage visualisationP4 data channel, colour coding per tariff block, comparison with the average and with the neighbourhood.
  • Dynamic pricing with EPEX integrationDay-ahead price in the app, push notification at price peaks or troughs, automatic charging at the trough.
  • Solar feed-in and net meteringOwn generation shown separately, net metering overview per year, scenario calculator.
  • Demand-response flowOpt-in for charging pauses at peak times, credit for avoided usage, transparent settlement.
  • Outage reporting in two tapsGas, electricity or water leaks, automatic geolocation, progress tracking in the app.
  • House moves and connectionsMeter reading via camera, automatic handover to the grid operator.
  • Fixed / variable / dynamic tariff choiceExplainable components, ACM-compliant, scenario per household.
  • Carbon footprint and notificationsPersonal CO₂ impact, contract-end alert, price update, outage update.
  • Multi-location and family accountBusiness + second home + shared meter on a single login.

Built within the strictest utility frameworks.

Compliance is non-negotiable in this sector. From the very first sprint, we work within the framework of the Energy Act, ACM supervision, GDPR and Heat Act 2.

Energy Act 2025

New division of roles between supplier & grid operator

The revised Energy Act brings changes to data access, metering responsibility and consumer protection. Among other things, the separation between supplier, balance-responsible party and grid operator is tightened, and new rules are introduced for dynamic-pricing contracts and consumer rights when switching supplier or moving home. We model the roles in the app architecture so that a change in regulatory rules does not lead to a refactor.

ACM supervision

Transparent tariff display

The ACM requires clear information on tariffs, contract types and cancellation options. We build tariff-selection flows in which every component (supply, transport, tax, surcharge) is visible and the right to cancel remains reachable within a single screen.

GDPR & smart-meter privacy

Consumption data as personal data

In legal terms, hourly metering data is personal data and falls under the GDPR. We build with data minimisation as the starting point: only the granularity the customer has approved themselves, with explicit opt-in for demand response or comparison with neighbourhood data.

Drinking Water Act

Supply guarantee and quality data

For water companies, the Drinking Water Act is the framework within which we publish outage notifications and quality reports. Our apps show the most recent quality data and link outage notifications to the GIS of the pipe network — more on this in our water technology software projects.

Heat Act 2

District heating tariff regulation

The revised Heat Act introduces new transparency requirements for heat tariffs. We model tariff components so that a customer can see exactly what they pay for supply, fixed charge and meter — including the annual recalibration by the ACM.

EU AI Act

Responsible AI in forecasting

For AI features (consumption forecasting, anomaly detection, smart charging), we map out the risk classification. Customer-facing AI calls for explainable models and an opt-out — we build in both as standard.

Seamlessly connected to the utility ecosystem.

We integrate with the billing engines, grid operator data streams and market platforms your organisation already works with. The app complements your back office rather than replacing it.

SAP IS-U
Enterprise billing
SAP S/4HANA Utilities
Next-gen platform
Oracle Utilities
Customer Care & Billing
Salesforce E&U Cloud
Energy & Utilities
EDSN
Market communication
EPEX SPOT
Day-ahead prices
P4 / P1 port
Smart-meter data
DigiD & iDIN
Identification

No project-by-project integrations.

We have standardised the integrations above in an abstraction layer. For a new assignment, we deploy the same adapters: fewer edge cases, faster turnaround, and your IT team can manage them itself if we step out. For smart-meter data, we work via the official P4 route (grid operator portal) and P1 port (local in the home), with explicit customer authorisation as the basis. Market communication between supplier and grid operator runs via EDSN formats — we model the associated business events (moving home, switching supplier, meter replacement) as first-class objects in the architecture.

For specific billing engines (Centric Energy, in-house Java legacy, custom middleware) we build case by case. This takes extra time in the planning phase but prevents integration debt later on. For IoT components such as smart thermostats, batteries and charging points, we draw on patterns from our IoT app projects. For the wider customer flow around onboarding, push notifications, account management and support, we reuse the design work from our B2C app projects. At the UX layer, a utility app is ultimately a B2C application with a back end of its own.

From customer research to go-live in clear steps.

An implementation project for a utility organisation has its own rhythm. Five phases that recur for every segment.

01 · Audit

Customer and data flow mapping

Mapping your existing portal data and customer journeys. Which questions dominate the service desk? Which flows are legacy? Which smart-meter data is already coming in via P4, and which still needs to be unlocked?

02 · Design

Scope per segment

For each target group: which flow goes into the app, which integrations take priority (SAP IS-U, EPEX, P4 channel, EDSN) and which features come later. The result is a scope document plus a wireframe set that both your compliance officer and your product owner can sign off.

03 · Build

Two-week sprints

One working flow delivered every sprint. Customer service and the compliance team test alongside us from the start. The first flow goes live within a few sprints, with smart-meter data and EPEX already integrated.

04 · Cutover

Phased rollout

First one customer segment or region, then the next. With every rollout: training, documentation, a monitoring dashboard and hand-over to the product owner.

05 · Maintenance

Ongoing

We adapt the app for OS updates, EPEX protocol changes and Energy Act amendments. Fixed monthly price, first-line support during office hours, security patches with an SLA.

When does a custom utility app make sense?

Not every organisation needs custom software. For the large national players (Eneco, Vattenfall, Greenchoice, Essent, Stedin, Liander, Enexis, Vitens), there is usually an in-house IT organisation or a fixed platform partner behind them, and custom development is no longer part of their procurement. For those organisations, we deliver at most specific white-label components or short partial flows.

We mainly build custom apps when one of these patterns applies. Mid-market energy suppliers or start-up suppliers that want to stand out on customer experience without the overhead of a large platform contract. Energy cooperatives with a shared-ownership model that fits no standard suite, such as voting-rights flows, local generation allocation or revenue distribution. Specific flows that go beyond the standard package: dynamic pricing with smart charging, solar plus battery, demand response or EV fleets for business customers.

We also build white-label apps for smaller providers that don't want to set up their own development department, and components with deep integration with smart-meter data, EPEX and grid data for those who want to make energy management a core proposition. AI-augmented forecasting (consumption forecasting, anomaly detection on meter data, smart-charging optimisation) is a speciality we get asked about more and more, usually in combination with an in-house energy platform or an energy management company.

If your organisation runs entirely on SAP IS-U or Oracle Utilities and you are looking for an end-to-end platform replacement, a project with SAP or Oracle themselves is almost always the more logical choice. We come into the picture once the question shifts to "we have a standard back office, but the customer app needs to be distinctive".

Work from the utility sector.

Energy supplier · Mid-market

Customer app with dynamic pricing

P4 integration, EPEX price visualisation, push notifications at price peaks and home-battery charging advice.

−38%
fewer service desk calls about consumption
+19 pts
NPS among solar customers
Water company · Regional

Outage reporting app with GIS

Customers report a water main failure with a photo and geolocation; back-office integration with the pipe network GIS.

~4 min
from report to assignment
12 regions
rolled out centrally
EV charging & heating · National

Energy management app

Smart charging of EVs at home based on the EPEX tariff plus own generation, linked to a heat buffer and home battery.

~22%
lower energy bill
5.000+
active households

Recognised in the utility sector.

ACM Energy Monitor 2024

"The growth of dynamic-pricing contracts and home batteries calls for customer applications that make the complexity of the new energy system understandable for the end user."

Energie+ Magazine, spring 2025

"Mid-market suppliers are increasingly looking for their own development partners to stand out on customer experience, rather than relying on a shared standard stack."

Energy cooperative customer survey

"The app has reduced the number of questions about consumption and net metering by more than a third, visible within the first months after going live."

Answers for the utility organisation going digital.

The questions we hear most from product owners, CTOs and compliance officers in this sector.

Who do you build utility apps for?
In practice, mainly for mid-market energy suppliers, local energy cooperatives, regional water companies and heat network operators. The big players (Eneco, Vattenfall, Stedin, Liander, Enexis, Vitens, Brabant Water) have their own IT organisations; there we deliver, at most, specific sub-flows as white-label. Our sweet spot is an organisation that wants to stand out to its customers but doesn't have an 80-strong IT department. Our client base also includes EV charging providers, demand-response aggregators and energy management companies (B2B energy consultancy).
How do you get customers' smart meter data?
Via two official routes. P4 is the grid operator channel: with the customer's authorisation, the app retrieves hourly data via the grid operator (quarter-hourly data for business customers). P1 is the local port on the meter itself, which a home energy manager, dongle or smart thermostat can connect to, for example. P1 gives the highest granularity (second-by-second to minute-by-minute data) but only works locally; P4 is ideal for the basic app flow in which the customer wants to see their data in the cloud. We combine both where it makes sense. We never use scraping or any workaround outside the official channels, as in this sector that puts both you and us at risk.
Can you build dynamic pricing with an EPEX integration?
Yes. We retrieve the day-ahead prices from the EPEX feed, map them to your tariff components (supply rate, transport, energy tax, renewable energy surcharge) and present the final price per hour in the app. This includes push notifications for price peaks or dips, and optionally charging advice for EVs and home batteries. The tariff display is always set up to comply with ACM (the Netherlands Authority for Consumers and Markets) requirements.
How does demand response work in the app?
Demand response is an opt-in flow: customers can indicate that they are willing to pause a consumer (EV charger, heat pump, battery) during peak hours in exchange for a credit. The app shows a notification, asks for explicit confirmation and logs the avoided consumption based on the baseline measurement. It suits both your own aggregator flow and integration with an external party. We have adapters for the most common OCPP implementations for charging points and Modbus integrations for batteries, so most hardware brands work out of the box.
Can you also build for grid operators?
Yes. The flow for a grid operator looks different from that of a supplier: more emphasis on outage reporting, planned work in the neighbourhood, connection requests and capacity upgrade requests. Fewer customer interactions per year, but each one has a high impact. We build these flows without forcing users through a tariff choice that doesn't exist for a grid operator, so they are segment-specific.
How do you handle GDPR compliance for consumption data?
In legal terms, hourly meter data is personal data, because it traceably reveals presence, daily rhythm and appliance use. From sprint 1 we work with data minimisation: only the granularity needed for the chosen function, explicit opt-in for demand response or neighbourhood comparison, and a DPIA at the end of the design phase. We define retention periods per data type, and data subject rights (access, erasure, data portability) are built into the architecture as standard. For AI features too (consumption forecasting, anomaly detection), we assess proportionality and build in an opt-out, in line with the direction of the EU AI Act.
What does a custom utility app cost?
A single customer segment with a basic flow (consumption, invoice, outage) is a more compact project than a platform with dynamic pricing, demand response and EV integration. The biggest cost drivers are usually not the UI build but the integrations: P4 integration, EPEX, EDSN market communication, the billing engine and, where relevant, OCPP for charging points. We work with a fixed sprint budget and give you a concrete price for the complete build after the planning phase. We give upfront estimates during the introductory call, based on your scope, segment, desired integrations and compliance level.
Can you integrate with SAP IS-U or S/4HANA Utilities?
Yes. Our app sits alongside your billing engine and connects via an API or a middleware layer (often via SAP PI/PO or your own integration bus). We have adapters for IS-U contracts, consumption postings and invoicing status. Replacing the billing platform has never been necessary in our projects, and it isn't desirable either, because it touches the core administration. For the broader context of utility CRM and invoicing, see our projects in energy software.
What about the EV charging flow for customers with a home charger?
For EV charging, we combine a smart charging algorithm (charging on solar surplus or at the lowest EPEX tariff) with an OCPP integration to the charging point and optional integration with a home battery and heat pump. We have developed this before in our EV charging app projects and reuse those patterns where we can. For a customer-facing release, we are also used to co-designing the wider B2C app flows (onboarding, push, account, support).
Do you also work white-label for smaller providers?
Yes. For energy cooperatives, smaller energy suppliers and regional heat networks, we can deliver a white-label version with your brand, your colours and your flow choices, on a shared codebase. That substantially reduces maintenance costs, and you automatically benefit from the ongoing development we do for our other clients. Pure branding adjustments at CSS level, with segment-specific flows switched on or off per feature flag.

Talk to us about your utilities app.

A half-hour introductory call with the product owner and, if needed, someone from compliance or IT. We listen to your segment, ask questions about your data stack and give you an initial direction. No obligation.

Edit content