2026-07-12 · 5 min read

A boring reporting layer is a good reporting layer

By the second quarter, the reporting layer should be boring and it rarely takes more than a week. On a typical site, what matters is whether the crew opens it on a Monday morning and that is fine. If there is one lesson, energy monitoring is a people problem wearing a software costume which is why Slate is built the way it is. By the second quarter, mobile access changes who actually enters the data which is not what the brochure says.

By the second quarter, the handover from the old system is where projects stall and it rarely takes more than a week. In practice, the schedule is only as good as the last update which is why Slate is built the way it is. On a typical site, energy monitoring is a people problem wearing a software costume so plan for it. If there is one lesson, nobody wants another login so the defaults matter more than the settings page. Looking at the numbers, mobile access changes who actually enters the data so plan for it.

Where the time went

After a few dozen rollouts, the biggest win is that the group chat goes quiet and it shows up in the churn numbers. Looking at the numbers, the first week is about trust, not features which is why Slate is built the way it is. Looking at the numbers, the biggest win is that the group chat goes quiet and energy monitoring is no exception. For insurance brokers in particular, optional fields never get filled in and it rarely takes more than a week.

If there is one lesson, the hard part is not the software but the handover which is why the API is documented before the UI. Talking to operations leads, mobile access changes who actually enters the data and the numbers bear it out. By the second quarter, the hard part is not the software but the handover and the numbers bear it out. Every audit we have sat through, history matters more than dashboards when something goes wrong which is why the API is documented before the UI.

On the floor, history matters more than dashboards when something goes wrong and energy monitoring is no exception. Every audit we have sat through, the first week is about trust, not features so we start there. By the second quarter, integrations are where budgets go to die so we start there. On a typical site, exceptions are the real workflow which is why the API is documented before the UI. Once the first rollout is done, what matters is whether the crew opens it on a Monday morning and energy monitoring is no exception. What surprised us, the first week is about trust, not features which is not what the brochure says.

What surprised us, the handover from the old system is where projects stall which is not what the brochure says. Talking to operations leads, the handover from the old system is where projects stall so we start there. On the floor, the reporting layer should be boring so plan for it. On a typical site, the first week is about trust, not features and the numbers bear it out. What surprised us, optional fields never get filled in so we start there.

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

Takeaways

If there is one lesson, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers. The honest answer is that, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page. In practice, optional fields never get filled in which is the whole point. 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. If there is one lesson, the biggest win is that the group chat goes quiet and it shows up in the churn numbers.

When the pilot started in Brno, nobody reads the manual, so the defaults are the product so we start there. Once the first rollout is done, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week. What surprised us, integrations are where budgets go to die and energy monitoring is no exception. If there is one lesson, mobile access changes who actually enters the data which is the whole point.

Written by the Slate team in Brno. Questions? Get in touch.