Interconnection teams
Every connection request moved on without a chase.
75%of the capacity that asks to connect is withdrawn before it is built
We build outage response, billing, complaints, connection paperwork and meter operations into the billing, metering and field systems you already run.
Applications, studies and deposits move by email and PDF, and deadlines live in spreadsheets. We build the tracker that keeps every project moving, inside the systems you already run.
Study reports read for their costs, upgrades and dates, and every new study compared with the last.
Electricity and gas suppliers, network operators and utilities, renewable developers, installers of solar, heat pumps and chargers, and the field service firms that work for them.
Every connection request moved on without a chase.
75%of the capacity that asks to connect is withdrawn before it is built
Every bill checked before it reaches the customer.
56%of the disputes that reach the energy ombudsman are about billing
Every complaint answered and sent the right way the first time.
43%of the cases that reach the ombudsman were pointed there correctly by the supplier
Connections, outages, bills and meters, each beside what changes once it is built.
Every project's deadlines, studies and costs sit in one place, and nothing lapses because an email was missed.
Meters that stop reporting found the day they stop, from the read data itself, remote fixes tried first, and visits booked and grouped by area.
Stopped reporting
Remote reset sent, reading again at 09:31
Reads late since Monday
Visit booked Tuesday with two homes nearby
Working as an old meter
Likely fix a new comms hub, from 41 similar visits
Battery offline overnight
Back online after a firmware update at 06:10
Export reads missing
Filled from the inverter's own data, no visit needed
The assets most at risk ranked before a storm, every bill explained from the customer's own reads and tariff, and every project's next deadline in sight.
Software for the rules, the timers and the record, and models for reading the calls, emails and reports, with your engineers and agents deciding.
ConnectionsNothing lapses because an email was missed.
From the first call to software that runs, in six steps, with the price agreed before any work starts.
Talk through how outages, billing, complaints or connection projects run today, and where the hours go.
A written map of every system, handoff and manual step, from the meter read or the first call to the bill, the crew or the signed agreement.
What we build first, what it replaces and what it costs, agreed before any work starts. It usually starts with the billing exceptions and complaints that reach a person every day.
Built inside your billing, meter data, outage and field service systems, with every action logged for the regulator.
Reviewed with operations and customer service, then switched on one region, one tariff or one project at a time.
We watch every run, fix what breaks and add the next piece when you are ready.
Safety, switching and every decision about a customer's supply stay with your engineers and agents. The software keeps the rules, the timers and the record, and the models read the calls, emails and reports and draft the replies.
Billing and customer systems, meter data management, outage management, GIS and asset registers, field service apps, network alarms, a CRM, email, and the regulator's and network operator's portals.
On the first call we go through that process, billing exceptions or outage updates for example, with you: which systems it touches, where the work waits and which steps are done by hand. The call ends with a written map of what we would build first, and the price is agreed in the plan before any work starts.
No. We build on top of the systems you already run and connect them, so your people keep working where they work today.
Not without a person. Anything that changes a supply, a meter or the network goes to an engineer for approval, and every action is logged.
Only the engineers on your project, and only in the systems you open for them. You decide what each automation can read and what it can change, and every run is logged.
It depends on the work. The plan names what goes live first, when, and the price, before any work starts.