2026-07-19 · 6 min read

Exceptions are the real workflow

On a typical site, a two-week pilot answers more than a three-month evaluation which is the whole point. In practice, the spreadsheet survives longer than anyone admits and the numbers bear it out. In practice, the hard part is not the software but the handover and that shaped the roadmap for a year. If there is one lesson, the first week is about trust, not features which is not what the brochure says.

Talking to operations leads, the handover from the old system is where projects stall which is the whole point. Talking to operations leads, the biggest win is that the group chat goes quiet and energy monitoring is no exception. What surprised us, the reporting layer should be boring so the defaults matter more than the settings page.

Every audit we have sat through, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. When the pilot started in Aarhus, the handover from the old system is where projects stall which is why the API is documented before the UI. In practice, a two-week pilot answers more than a three-month evaluation and the numbers bear it out. For food producers in particular, a two-week pilot answers more than a three-month evaluation which is not what the brochure says.

What actually happened

Most teams we meet, the biggest win is that the group chat goes quiet so plan for it. In practice, optional fields never get filled in so plan for it. The honest answer is that, the handover from the old system is where projects stall which is not what the brochure says. Every audit we have sat through, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year. Talking to operations leads, the handover from the old system is where projects stall and energy monitoring is no exception. Talking to operations leads, nobody wants another login which is the whole point.

After a few dozen rollouts, mobile access changes who actually enters the data and it shows up in the churn numbers. Looking at the numbers, the schedule is only as good as the last update which is why BasaltNode is built the way it is. Once the first rollout is done, nobody wants another login so plan for it. Once the first rollout is done, nobody wants another login so plan for it.

Looking at the numbers, the biggest win is that the group chat goes quiet and that shaped the roadmap for a year. After a few dozen rollouts, the schedule is only as good as the last update so the defaults matter more than the settings page. After a few dozen rollouts, nobody reads the manual, so the defaults are the product and that is fine.

“Everything food producers need to keep energy monitoring on schedule, on budget and on record.”

Where this leaves us

On a typical site, history matters more than dashboards when something goes wrong and it rarely takes more than a week. By the second quarter, integrations are where budgets go to die so the defaults matter more than the settings page. Every audit we have sat through, nobody wants another login and it rarely takes more than a week. Every audit we have sat through, the reporting layer should be boring so plan for it. Once the first rollout is done, the handover from the old system is where projects stall so we start there.

What surprised us, the spreadsheet survives longer than anyone admits and it rarely takes more than a week. Once the first rollout is done, the biggest win is that the group chat goes quiet and it shows up in the churn numbers. After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks so we start there.

After a few dozen rollouts, what matters is whether the crew opens it on a Monday morning which is why BasaltNode is built the way it is. When the pilot started in Aarhus, energy monitoring is a people problem wearing a software costume and energy monitoring is no exception. After a few dozen rollouts, nobody reads the manual, so the defaults are the product so we start there. On the floor, the schedule is only as good as the last update so plan for it.

Written by the BasaltNode team in Aarhus. Questions? Get in touch.