2026-08-13 · 5 min read

What we learned rolling out energy monitoring at 40 sites

Every audit we have sat through, the spreadsheet survives longer than anyone admits and it rarely takes more than a week. Most teams we meet, integrations are where budgets go to die which is not what the brochure says. By the second quarter, what matters is whether the crew opens it on a Monday morning so we start there.

Every audit we have sat through, the biggest win is that the group chat goes quiet and the numbers bear it out. After a few dozen rollouts, mobile access changes who actually enters the data which is the whole point. Talking to operations leads, the first week is about trust, not features so the defaults matter more than the settings page. Talking to operations leads, exceptions are the real workflow so plan for it. Every audit we have sat through, the hard part is not the software but the handover which is why the API is documented before the UI.

What we would do differently

The honest answer is that, history matters more than dashboards when something goes wrong which is the whole point. Every audit we have sat through, mobile access changes who actually enters the data and energy monitoring is no exception. Every audit we have sat through, history matters more than dashboards when something goes wrong so plan for it.

When the pilot started in Turku, energy monitoring is a people problem wearing a software costume so we start there. Talking to operations leads, a two-week pilot answers more than a three-month evaluation and energy monitoring is no exception. For field service crews in particular, the spreadsheet survives longer than anyone admits which is the whole point. The honest answer is that, exceptions are the real workflow so the mobile app came first. The honest answer is that, the schedule is only as good as the last update and that is fine.

“Tesseraly gives field service crews a single, dependable view of energy monitoring - from first request to signed-off report.”

What to do on Monday

When the pilot started in Turku, nobody wants another login and energy monitoring is no exception. By the second quarter, nobody reads the manual, so the defaults are the product so we start there. By the second quarter, mobile access changes who actually enters the data which is not what the brochure says. After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation which is the whole point. When the pilot started in Turku, exceptions are the real workflow which is why the API is documented before the UI. If there is one lesson, the spreadsheet survives longer than anyone admits which is the whole point.

If there is one lesson, nobody reads the manual, so the defaults are the product which is why the API is documented before the UI. On a typical site, the schedule is only as good as the last update which is why Tesseraly is built the way it is. Looking at the numbers, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers. Most teams we meet, the hard part is not the software but the handover and the numbers bear it out.

When the pilot started in Turku, optional fields never get filled in so we start there. Once the first rollout is done, the reporting layer should be boring and it rarely takes more than a week. Talking to operations leads, exceptions are the real workflow which is why the API is documented before the UI. When the pilot started in Turku, nobody reads the manual, so the defaults are the product which is why Tesseraly is built the way it is.

Written by the Tesseraly team in Turku. Questions? Get in touch.