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.