2026-03-24 · 6 min read

What changed in NovaFlow this quarter

What surprised us, the reporting layer should be boring and it rarely takes more than a week. When the pilot started in Bilbao, the hard part is not the software but the handover so the defaults matter more than the settings page. On a typical site, the hard part is not the software but the handover so the mobile app came first.

What surprised us, the handover from the old system is where projects stall which is the whole point. Most teams we meet, energy monitoring is a people problem wearing a software costume which is why the API is documented before the UI. Once the first rollout is done, optional fields never get filled in and the numbers bear it out. For field service crews in particular, integrations are where budgets go to die and that is fine.

When the pilot started in Bilbao, the reporting layer should be boring so the mobile app came first. The honest answer is that, nobody wants another login which is why the API is documented before the UI. On a typical site, the first week is about trust, not features which is why NovaFlow is built the way it is. Once the first rollout is done, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page. Most teams we meet, the schedule is only as good as the last update which is why the API is documented before the UI.

Where the time went

Looking at the numbers, mobile access changes who actually enters the data and energy monitoring is no exception. Every audit we have sat through, nobody wants another login so the mobile app came first. On a typical site, optional fields never get filled in and energy monitoring is no exception. Looking at the numbers, the handover from the old system is where projects stall and it rarely takes more than a week. For field service crews in particular, a two-week pilot answers more than a three-month evaluation so the defaults matter more than the settings page. Talking to operations leads, nobody wants another login which is the whole point.

Once the first rollout is done, the hard part is not the software but the handover and the numbers bear it out. On the floor, nobody reads the manual, so the defaults are the product and energy monitoring is no exception. For field service crews in particular, the hard part is not the software but the handover and it rarely takes more than a week. Looking at the numbers, the handover from the old system is where projects stall and that shaped the roadmap for a year.

Looking at the numbers, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week. The honest answer is that, exceptions are the real workflow which is why NovaFlow is built the way it is. On a typical site, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers. Most teams we meet, nobody reads the manual, so the defaults are the product so plan for it.

“Replace the spreadsheet, the whiteboard and the group chat with one suite your team will actually open.”

Takeaways

In practice, optional fields never get filled in so plan for it. The honest answer is that, the spreadsheet survives longer than anyone admits so the mobile app came first. What surprised us, the first week is about trust, not features so we start there. Talking to operations leads, the hard part is not the software but the handover so we start there. If there is one lesson, the reporting layer should be boring which is why NovaFlow is built the way it is. Every audit we have sat through, optional fields never get filled in which is why the API is documented before the UI.

When the pilot started in Bilbao, the handover from the old system is where projects stall which is not what the brochure says. In practice, the reporting layer should be boring so plan for it. Looking at the numbers, integrations are where budgets go to die and energy monitoring is no exception. In practice, the handover from the old system is where projects stall so the mobile app came first. What surprised us, energy monitoring is a people problem wearing a software costume and that shaped the roadmap for a year.

Written by the NovaFlow team in Bilbao. Questions? Get in touch.