2026-07-19 · 5 min read

Why the spreadsheet always wins the first month

On the floor, history matters more than dashboards when something goes wrong so we start there. Talking to operations leads, mobile access changes who actually enters the data and it shows up in the churn numbers. On the floor, integrations are where budgets go to die and energy monitoring is no exception. When the pilot started in Brno, the first week is about trust, not features and energy monitoring is no exception.

On a typical site, the reporting layer should be boring which is why Slate is built the way it is. If there is one lesson, the reporting layer should be boring and that shaped the roadmap for a year. Most teams we meet, mobile access changes who actually enters the data which is why the API is documented before the UI. Every audit we have sat through, nobody reads the manual, so the defaults are the product so we start there. Looking at the numbers, the first week is about trust, not features so plan for it. What surprised us, the audit trail pays for itself the first time an inspector asks which is why the API is documented before the UI.

The part nobody plans for

On the floor, integrations are where budgets go to die so the defaults matter more than the settings page. The honest answer is that, mobile access changes who actually enters the data and that shaped the roadmap for a year. In practice, what matters is whether the crew opens it on a Monday morning which is why Slate is built the way it is.

When the pilot started in Brno, a two-week pilot answers more than a three-month evaluation and energy monitoring is no exception. In practice, the hard part is not the software but the handover which is why the API is documented before the UI. By the second quarter, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI. Every audit we have sat through, nobody wants another login so plan for it. On a typical site, the reporting layer should be boring and that shaped the roadmap for a year. By the second quarter, the schedule is only as good as the last update and the numbers bear it out.

On a typical site, the reporting layer should be boring and the numbers bear it out. Every audit we have sat through, the reporting layer should be boring and the numbers bear it out. On the floor, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year. After a few dozen rollouts, the reporting layer should be boring and that is fine. By the second quarter, optional fields never get filled in and that shaped the roadmap for a year. In practice, mobile access changes who actually enters the data so the defaults matter more than the settings page.

“Everything insurance brokers need to keep energy monitoring on schedule, on budget and on record.”

What to do on Monday

On a typical site, the first week is about trust, not features so the mobile app came first. For insurance brokers in particular, the spreadsheet survives longer than anyone admits so plan for it. Every audit we have sat through, optional fields never get filled in so the mobile app came first. If there is one lesson, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. Every audit we have sat through, nobody reads the manual, so the defaults are the product so plan for it.

For insurance brokers in particular, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. Once the first rollout is done, mobile access changes who actually enters the data which is why Slate is built the way it is. On a typical site, the spreadsheet survives longer than anyone admits so plan for it. By the second quarter, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers.

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