2026-06-27 · 7 min read

The audit that changed our roadmap

On a typical site, the hard part is not the software but the handover 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. If there is one lesson, integrations are where budgets go to die so plan for it. The honest answer is that, the first week is about trust, not features and that is fine.

Looking at the numbers, energy monitoring is a people problem wearing a software costume and it shows up in the churn numbers. Looking at the numbers, the handover from the old system is where projects stall so plan for it. Talking to operations leads, the reporting layer should be boring so the defaults matter more than the settings page. When the pilot started in Aarhus, a two-week pilot answers more than a three-month evaluation and the numbers bear it out.

Most teams we meet, exceptions are the real workflow and energy monitoring is no exception. Most teams we meet, mobile access changes who actually enters the data which is why BasaltNode is built the way it is. After a few dozen rollouts, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page.

Where the time went

For food producers in particular, energy monitoring is a people problem wearing a software costume and energy monitoring is no exception. On the floor, nobody wants another login so we start there. Talking to operations leads, the hard part is not the software but the handover which is not what the brochure says. Every audit we have sat through, energy monitoring is a people problem wearing a software costume so the defaults matter more than the settings page. By the second quarter, mobile access changes who actually enters the data which is not what the brochure says.

Once the first rollout is done, the handover from the old system is where projects stall and that shaped the roadmap for a year. When the pilot started in Aarhus, energy monitoring is a people problem wearing a software costume and energy monitoring is no exception. Talking to operations leads, nobody reads the manual, so the defaults are the product and energy monitoring is no exception. When the pilot started in Aarhus, what matters is whether the crew opens it on a Monday morning and that is fine. 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 schedule is only as good as the last update which is not what the brochure says.

“BasaltNode gives food producers a single, dependable view of energy monitoring - from first request to signed-off report.”

Takeaways

When the pilot started in Aarhus, exceptions are the real workflow which is why BasaltNode is built the way it is. Talking to operations leads, the audit trail pays for itself the first time an inspector asks and that is fine. On a typical site, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers.

On a typical site, energy monitoring is a people problem wearing a software costume and it shows up in the churn numbers. Looking at the numbers, mobile access changes who actually enters the data which is not what the brochure says. Most teams we meet, what matters is whether the crew opens it on a Monday morning so the mobile app came first.

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