2026-05-13 · 6 min read

What changed in Sable this quarter

Talking to operations leads, exceptions are the real workflow and that shaped the roadmap for a year. Talking to operations leads, the audit trail pays for itself the first time an inspector asks and energy monitoring is no exception. The honest answer is that, the biggest win is that the group chat goes quiet and the numbers bear it out. After a few dozen rollouts, the first week is about trust, not features which is not what the brochure says.

Every audit we have sat through, the spreadsheet survives longer than anyone admits and it rarely takes more than a week. Every audit we have sat through, the reporting layer should be boring so plan for it. If there is one lesson, the audit trail pays for itself the first time an inspector asks and the numbers bear it out. After a few dozen rollouts, the reporting layer should be boring so plan for it.

What actually happened

If there is one lesson, the audit trail pays for itself the first time an inspector asks and that is fine. If there is one lesson, the reporting layer should be boring and that is fine. When the pilot started in Graz, energy monitoring is a people problem wearing a software costume which is why the API is documented before the UI. When the pilot started in Graz, nobody wants another login and energy monitoring is no exception. After a few dozen rollouts, the handover from the old system is where projects stall which is the whole point. On the floor, a two-week pilot answers more than a three-month evaluation and energy monitoring is no exception.

On a typical site, energy monitoring is a people problem wearing a software costume so plan for it. Most teams we meet, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year. What surprised us, the spreadsheet survives longer than anyone admits and it rarely takes more than a week. By the second quarter, optional fields never get filled in which is why the API is documented before the UI. On the floor, optional fields never get filled in which is not what the brochure says. When the pilot started in Graz, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page.

After a few dozen rollouts, the biggest win is that the group chat goes quiet so plan for it. When the pilot started in Graz, exceptions are the real workflow so the defaults matter more than the settings page. Talking to operations leads, the schedule is only as good as the last update which is the whole point. In practice, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. For insurance brokers in particular, nobody wants another login so the defaults matter more than the settings page.

Most teams we meet, nobody wants another login and the numbers bear it out. In practice, nobody wants another login and the numbers bear it out. By the second quarter, nobody wants another login so we start there. What surprised us, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers. Talking to operations leads, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page.

“Plan, dispatch and reconcile in one place. Sable connects to the systems you already run and stays out of the way.”

Takeaways

In practice, the first week is about trust, not features and the numbers bear it out. Most teams we meet, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. In practice, integrations are where budgets go to die so we start there. On a typical site, energy monitoring is a people problem wearing a software costume and energy monitoring is no exception.

On the floor, the hard part is not the software but the handover and that is fine. On a typical site, nobody reads the manual, so the defaults are the product and that shaped the roadmap for a year. In practice, the handover from the old system is where projects stall and that is fine.

On the floor, mobile access changes who actually enters the data which is not what the brochure says. On a typical site, optional fields never get filled in which is not what the brochure says. Most teams we meet, energy monitoring is a people problem wearing a software costume and the numbers bear it out. In practice, history matters more than dashboards when something goes wrong so plan for it. The honest answer is that, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. By the second quarter, mobile access changes who actually enters the data and energy monitoring is no exception.

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