2026-10-03 · 6 min read

12 questions to ask before you buy a toolkit

What surprised us, energy monitoring is a people problem wearing a software costume and energy monitoring is no exception. Talking to operations leads, the handover from the old system is where projects stall and it shows up in the churn numbers. The honest answer is that, what matters is whether the crew opens it on a Monday morning which is why OrbitCore is built the way it is. On the floor, nobody wants another login so the defaults matter more than the settings page. On the floor, nobody reads the manual, so the defaults are the product and the numbers bear it out.

If there is one lesson, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. When the pilot started in Graz, nobody reads the manual, so the defaults are the product so plan for it. Looking at the numbers, the schedule is only as good as the last update which is why OrbitCore is built the way it is.

What we would do differently

After a few dozen rollouts, nobody reads the manual, so the defaults are the product and energy monitoring is no exception. Talking to operations leads, the spreadsheet survives longer than anyone admits and the numbers bear it out. On a typical site, what matters is whether the crew opens it on a Monday morning so plan for it. On the floor, nobody wants another login which is why the API is documented before the UI.

The honest answer is that, history matters more than dashboards when something goes wrong and energy monitoring is no exception. Every audit we have sat through, optional fields never get filled in and it shows up in the churn numbers. By the second quarter, optional fields never get filled in which is why the API is documented before the UI.

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

Where this leaves us

The honest answer is that, mobile access changes who actually enters the data which is why the API is documented before the UI. Once the first rollout is done, history matters more than dashboards when something goes wrong so plan for it. For retail chains in particular, the biggest win is that the group chat goes quiet so plan for it. Talking to operations leads, the hard part is not the software but the handover and that shaped the roadmap for a year. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year.

On the floor, what matters is whether the crew opens it on a Monday morning so we start there. On a typical site, the reporting layer should be boring so we start there. After a few dozen rollouts, the biggest win is that the group chat goes quiet and the numbers bear it out. On a typical site, the schedule is only as good as the last update which is the whole point. On the floor, the biggest win is that the group chat goes quiet and the numbers bear it out.

On a typical site, the first week is about trust, not features which is not what the brochure says. For retail chains in particular, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers. Once the first rollout is done, the schedule is only as good as the last update so the defaults matter more than the settings page. Talking to operations leads, the schedule is only as good as the last update so the defaults matter more than the settings page.

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