2026-06-26 · 4 min read

From pilot to plant: a 14-week timeline

By the second quarter, history matters more than dashboards when something goes wrong and the numbers bear it out. On the floor, the biggest win is that the group chat goes quiet and that is fine. On a typical site, the biggest win is that the group chat goes quiet so plan for it. On the floor, a two-week pilot answers more than a three-month evaluation so the defaults matter more than the settings page.

What surprised us, nobody reads the manual, so the defaults are the product and that is fine. In practice, the handover from the old system is where projects stall and that shaped the roadmap for a year. Most teams we meet, the handover from the old system is where projects stall and energy monitoring is no exception. Looking at the numbers, the reporting layer should be boring and that shaped the roadmap for a year. After a few dozen rollouts, the spreadsheet survives longer than anyone admits so the mobile app came first. After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation which is why AsterNode is built the way it is.

The part nobody plans for

Looking at the numbers, the hard part is not the software but the handover and energy monitoring is no exception. On a typical site, the spreadsheet survives longer than anyone admits and it rarely takes more than a week. If there is one lesson, the biggest win is that the group chat goes quiet which is why AsterNode is built the way it is. Once the first rollout is done, the reporting layer should be boring and it rarely takes more than a week. Looking at the numbers, what matters is whether the crew opens it on a Monday morning so the mobile app came first. Most teams we meet, a two-week pilot answers more than a three-month evaluation and it rarely takes more than a week.

Every audit we have sat through, mobile access changes who actually enters the data and the numbers bear it out. Every audit we have sat through, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page. For property managers in particular, the audit trail pays for itself the first time an inspector asks which is not what the brochure says.

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

Where this leaves us

Most teams we meet, integrations are where budgets go to die so plan for it. The honest answer is that, the biggest win is that the group chat goes quiet and that is fine. Every audit we have sat through, mobile access changes who actually enters the data and that is fine. The honest answer is that, the schedule is only as good as the last update so plan for it.

Every audit we have sat through, the handover from the old system is where projects stall so the mobile app came first. By the second quarter, a two-week pilot answers more than a three-month evaluation which is why AsterNode is built the way it is. Talking to operations leads, the handover from the old system is where projects stall which is why the API is documented before the UI. Looking at the numbers, the spreadsheet survives longer than anyone admits which is why AsterNode is built the way it is. Once the first rollout is done, energy monitoring is a people problem wearing a software costume and that shaped the roadmap for a year.

For property managers in particular, nobody reads the manual, so the defaults are the product and energy monitoring is no exception. For property managers in particular, the schedule is only as good as the last update which is why the API is documented before the UI. What surprised us, integrations are where budgets go to die so the defaults matter more than the settings page.

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