On September 24, 2026, Codibly and Derapi co-hosted a session on moving utility demand response from separate programs to something coordinated. The conversation covered both ends of the problem: getting devices enrolled in programs, and running many programs as one resource once they exist.

Stina Brock, CEO of Derapi, presented alongside Enoch Lenge, Head of US, Energy Practice at Codibly.

Webinar highlights

1. Demand response started with phone calls
The first programs called on a few large commercial and industrial customers during summer peaks, by phone and day-ahead email. Connected thermostats, EV chargers and batteries changed what a utility can control and how often it can read the data.

2. Every device type becomes its own program
A regulatory framework, a program design, a bid to select an aggregator, a launch, then regulatory reporting. The cycle repeats for each device type, and each program ends up with its own aggregator, its own team and its own reports.

3. Bring Your Own Distributed Capacity
Stina Brock set out Derapi’s framework in which large new loads, such as data centers, fund local distributed energy that provides capacity and peak reduction for the grid and benefits for the community around it.

4. Three things utilities now ask for across programs
Regulatory reporting without pulling data from each aggregator by hand. Validation of what programs delivered against meter data, including the same customer counted in two programs. And coordination between the grid operations team and the program teams.

5. A layer above the aggregators
Enoch Lenge walked through a proof of concept for a utility-side layer that maps each aggregator’s terms to one taxonomy, reconciles reported delivery with meter and event data, and gives one portfolio view. It replaces none of the aggregators’ systems.

6. Without customers, there is no data
Customer experience matters as much as the data behind it. A simple reason to take part, a smooth enrollment and value outside events decide whether customers stay enrolled.

Watch the full webinar below:

The written version

The argument at the centre of the session is written up in full, with the recording embedded: Demand Response Orchestration: What Utilities Ask for Across Programs.