2026-06-10 · 7 min read

What we learned rolling out energy monitoring at 29 sites

Every audit we have sat through, energy monitoring is a people problem wearing a software costume and that is fine. For insurance brokers in particular, the reporting layer should be boring which is why the API is documented before the UI. In practice, nobody wants another login and that is fine. Most teams we meet, the handover from the old system is where projects stall and energy monitoring is no exception.

When the pilot started in Graz, integrations are where budgets go to die and the numbers bear it out. When the pilot started in Graz, the reporting layer should be boring which is why the API is documented before the UI. If there is one lesson, the handover from the old system is where projects stall and energy monitoring is no exception. The honest answer is that, nobody reads the manual, so the defaults are the product which is not what the brochure says.

Talking to operations leads, history matters more than dashboards when something goes wrong so the defaults matter more than the settings page. By the second quarter, the hard part is not the software but the handover so the defaults matter more than the settings page. What surprised us, the reporting layer should be boring and the numbers bear it out. When the pilot started in Graz, the audit trail pays for itself the first time an inspector asks which is the whole point. Once the first rollout is done, the first week is about trust, not features so we start there. On the floor, the reporting layer should be boring which is the whole point.

The part nobody plans for

Looking at the numbers, the biggest win is that the group chat goes quiet and that shaped the roadmap for a year. Talking to operations leads, the handover from the old system is where projects stall and energy monitoring is no exception. By the second quarter, a two-week pilot answers more than a three-month evaluation and the numbers bear it out. For insurance brokers in particular, the handover from the old system is where projects stall so the defaults matter more than the settings page.

After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks so plan for it. The honest answer is that, energy monitoring is a people problem wearing a software costume and that is fine. By the second quarter, the schedule is only as good as the last update and that shaped the roadmap for a year. Every audit we have sat through, the hard part is not the software but the handover and that is fine. Talking to operations leads, the audit trail pays for itself the first time an inspector asks which is the whole point. Every audit we have sat through, the reporting layer should be boring which is why the API is documented before the UI.

On a typical site, the first week is about trust, not features so the defaults matter more than the settings page. In practice, the first week is about trust, not features and energy monitoring is no exception. In practice, exceptions are the real workflow and it shows up in the churn numbers. In practice, integrations are where budgets go to die and that shaped the roadmap for a year. After a few dozen rollouts, optional fields never get filled in so we start there. On the floor, integrations are where budgets go to die so the mobile app came first.

What surprised us, the spreadsheet survives longer than anyone admits and that shaped the roadmap for a year. Once the first rollout is done, mobile access changes who actually enters the data so the mobile app came first. The honest answer is that, mobile access changes who actually enters the data and it rarely takes more than a week. On a typical site, the schedule is only as good as the last update which is why Sable is built the way it is. On a typical site, optional fields never get filled in and energy monitoring is no exception. For insurance brokers in particular, exceptions are the real workflow and that shaped the roadmap for a year.

“Sable gives insurance brokers a single, dependable view of energy monitoring - from first request to signed-off report.”

What to do on Monday

If there is one lesson, nobody wants another login so the defaults matter more than the settings page. On the floor, mobile access changes who actually enters the data and the numbers bear it out. In practice, the first week is about trust, not features and the numbers bear it out. Talking to operations leads, the reporting layer should be boring and that shaped the roadmap for a year. In practice, the biggest win is that the group chat goes quiet so the defaults matter more than the settings page.

On the floor, optional fields never get filled in so we start there. Talking to operations leads, exceptions are the real workflow and it shows up in the churn numbers. What surprised us, integrations are where budgets go to die which is why Sable is built the way it is. On the floor, nobody wants another login and it shows up in the churn numbers. What surprised us, integrations are where budgets go to die so plan for it.

Written by the Sable team in Graz. Questions? Get in touch.