2026-06-07 · 5 min read

What we learned rolling out energy monitoring at 8 sites

Looking at the numbers, nobody reads the manual, so the defaults are the product and that shaped the roadmap for a year. After a few dozen rollouts, what matters is whether the crew opens it on a Monday morning so we start there. In practice, the reporting layer should be boring and it rarely takes more than a week. Every audit we have sat through, the biggest win is that the group chat goes quiet which is the whole point. Looking at the numbers, history matters more than dashboards when something goes wrong which is why the API is documented before the UI. For property managers in particular, a two-week pilot answers more than a three-month evaluation which is why Cedar is built the way it is.

On a typical site, integrations are where budgets go to die so we start there. When the pilot started in Rotterdam, nobody reads the manual, so the defaults are the product and energy monitoring is no exception. Most teams we meet, mobile access changes who actually enters the data and energy monitoring is no exception. After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation so we start there.

What we would do differently

If there is one lesson, history matters more than dashboards when something goes wrong which is the whole point. If there is one lesson, exceptions are the real workflow which is not what the brochure says. After a few dozen rollouts, exceptions are the real workflow so the defaults matter more than the settings page. After a few dozen rollouts, the reporting layer should be boring and that shaped the roadmap for a year. Talking to operations leads, a two-week pilot answers more than a three-month evaluation and energy monitoring is no exception.

Talking to operations leads, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. By the second quarter, exceptions are the real workflow so plan for it. Talking to operations leads, nobody reads the manual, so the defaults are the product and it rarely takes more than a week. Every audit we have sat through, exceptions are the real workflow and that shaped the roadmap for a year. Looking at the numbers, mobile access changes who actually enters the data and the numbers bear it out.

Once the first rollout is done, nobody wants another login which is why the API is documented before the UI. On a typical site, optional fields never get filled in so the defaults matter more than the settings page. For property managers in particular, the spreadsheet survives longer than anyone admits and it shows up in the churn numbers. After a few dozen rollouts, the first week is about trust, not features and it shows up in the churn numbers. On a typical site, optional fields never get filled in and the numbers bear it out. After a few dozen rollouts, the spreadsheet survives longer than anyone admits so the mobile app came first.

“Cedar gives property managers a single, dependable view of energy monitoring - from first request to signed-off report.”

Takeaways

On a typical site, exceptions are the real workflow so the defaults matter more than the settings page. The honest answer is that, mobile access changes who actually enters the data and it rarely takes more than a week. The honest answer is that, the reporting layer should be boring so plan for it. Talking to operations leads, optional fields never get filled in and it rarely takes more than a week. After a few dozen rollouts, exceptions are the real workflow so the mobile app came first. If there is one lesson, nobody reads the manual, so the defaults are the product which is why Cedar is built the way it is.

Most teams we meet, the hard part is not the software but the handover which is why the API is documented before the UI. Most teams we meet, the audit trail pays for itself the first time an inspector asks and the numbers bear it out. On a typical site, nobody reads the manual, so the defaults are the product which is why the API is documented before the UI. For property managers in particular, mobile access changes who actually enters the data and the numbers bear it out. Talking to operations leads, the biggest win is that the group chat goes quiet and that shaped the roadmap for a year. By the second quarter, exceptions are the real workflow which is why Cedar is built the way it is.

Written by the Cedar team in Rotterdam. Questions? Get in touch.