Utilities Software Development: Infrastructure Meets Innovation.

Utilities software development in the UK is now shaped by targets that are published, measured and enforced. Smart metering is the clearest example.

At the end of 2025, 41 million smart and advanced meters were in homes and small businesses across Great Britain, which is 71% of all meters.

That volume of connected infrastructure changes what a customer expects. They can see their own usage, so they expect your systems to see it too, and to explain it back to them clearly.

We build the platforms that sit between the meter and the customer. Outage reporting, smart meter integration, billing and payment processing, asset management and monitoring, field service and engineer scheduling, and regulatory reporting all come through our utilities app development work.

The BoilerJuice ordering app is one version of that. We built the iOS and Android apps in Flutter from a single codebase, with a streamlined ordering process, tank level monitoring, transaction history and usage tracking.

Keeping business logic inside BoilerJuice's own backend was a deliberate choice. It meant the app integrated with the systems they already ran rather than forcing a rebuild behind it, which is usually the shape of this work: less about replacing infrastructure than about giving people a usable way to reach it.

Regulated targets are hard to hit when the reporting is manual. Ofwat's own performance report is blunt about it: the sector committed to reducing annual leakage by 16% across 2020 to 2025 and did not meet it, reducing leakage by 9% overall.

We have seen what manual reporting costs at close range. When we automated H2OiQ's water efficiency reporting, their engineers were producing up to 60 individual reports a week entirely by hand, compiled from complex spreadsheets and disconnected data sources with no central record of site history.

The platform we built ingests field data from their existing tools, runs it through the cascading calculations their engineers actually use, and generates the reports automatically. The point was not to replace their expertise. It was to stop them spending it on formatting.

We work the same way on customer-facing utility websites, designing for accessibility and resilience because a utility site is one people reach for on their worst day. Integration with legacy systems is assumed in our utilities software development rather than treated as an obstacle.

Security posture matters in a regulated sector. We follow protocols aligned with ISO27001 and ISO9001, and hold Cyber Essentials Plus certification. Support and data insight continue after launch, because the reporting requirements move even when the infrastructure does not.

AI earns its place in utilities where the data is already flowing and nobody has time to read it. Detecting usage anomalies, spotting continuous flow that indicates a leak, and building maintenance schedules from condition rather than from the calendar are all jobs that suit a model.

We are careful about where AI genuinely earns its place. In a regulated sector, a recommendation a person cannot explain to an auditor is a liability.

So we build systems that show their reasoning and keep a human in the decision. That is the same standard we hold the rest of our utilities software development to.

Can you build apps and websites for energy, water, or waste services?

Yes. We design custom apps and websites covering usage monitoring and reporting through to customer billing and outage notifications. We have delivered in all three, including work with H2OiQ on water efficiency and BoilerJuice on heating oil.

How do your apps and websites integrate with legacy infrastructure?

We design API-first platforms that connect to your existing systems rather than replacing them. That keeps disruption down and means business logic can stay where it already lives, which matters when the underlying system is regulated.

Are your apps and websites secure and compliant?

Yes. We follow established cybersecurity and data protection practice, and build to standards including GDPR and ISO27001. Access controls and audit trails are part of the build rather than something added when an audit is announced.

What do utility customers complain about most?

Billing and meter reading. Ofgem's most recent state of the market report finds they remain a significant driver of complaints, accounting for a share comparable to customer service. Most billing complaints start with a customer who cannot follow the figure they have been sent, so our utilities software development puts the usage data and the arithmetic behind a bill in front of them.

Do we have to replace our legacy billing system?

No. Most of what a utility runs on cannot simply be switched off, so utilities software development here starts by mapping your infrastructure, your user journeys and the operational goals you are measured on. That map tells us which parts of the estate to build against and which to leave alone, which is the same pattern we used on BoilerJuice.