2026-07-20 · 8 min read

19 questions to ask before you buy a toolkit

After a few dozen rollouts, energy monitoring is a people problem wearing a software costume and that shaped the roadmap for a year. If there is one lesson, the biggest win is that the group chat goes quiet and the numbers bear it out. In practice, the spreadsheet survives longer than anyone admits so plan for it. Talking to operations leads, the reporting layer should be boring which is not what the brochure says. Looking at the numbers, the reporting layer should be boring and it shows up in the churn numbers. In practice, the reporting layer should be boring and the numbers bear it out.

In practice, nobody wants another login which is not what the brochure says. What surprised us, history matters more than dashboards when something goes wrong which is why CoralFlow is built the way it is. Looking at the numbers, what matters is whether the crew opens it on a Monday morning so plan for it.

On a typical site, a two-week pilot answers more than a three-month evaluation so the defaults matter more than the settings page. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning so plan for it. When the pilot started in Bilbao, nobody wants another login which is why the API is documented before the UI. Most teams we meet, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. 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. Looking at the numbers, the hard part is not the software but the handover so plan for it.

Where the time went

On the floor, energy monitoring is a people problem wearing a software costume which is why the API is documented before the UI. When the pilot started in Bilbao, the spreadsheet survives longer than anyone admits so plan for it. Once the first rollout is done, energy monitoring is a people problem wearing a software costume which is not what the brochure says. Every audit we have sat through, the hard part is not the software but the handover so the defaults matter more than the settings page. On the floor, integrations are where budgets go to die and it rarely takes more than a week.

Most teams we meet, what matters is whether the crew opens it on a Monday morning which is why the API is documented before the UI. Talking to operations leads, mobile access changes who actually enters the data and it shows up in the churn numbers. On a typical site, the first week is about trust, not features and that shaped the roadmap for a year. If there is one lesson, energy monitoring is a people problem wearing a software costume so the defaults matter more than the settings page. What surprised us, the biggest win is that the group chat goes quiet and it rarely takes more than a week. Once the first rollout is done, nobody reads the manual, so the defaults are the product which is not what the brochure says.

What surprised us, the first week is about trust, not features so the defaults matter more than the settings page. On the floor, the handover from the old system is where projects stall and energy monitoring is no exception. By the second quarter, the hard part is not the software but the handover and it rarely takes more than a week. Talking to operations leads, energy monitoring is a people problem wearing a software costume and energy monitoring is no exception. When the pilot started in Bilbao, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. Most teams we meet, exceptions are the real workflow so we start there.

“CoralFlow gives field service crews a single, dependable view of energy monitoring - from first request to signed-off report.”

Where this leaves us

Talking to operations leads, history matters more than dashboards when something goes wrong which is the whole point. Every audit we have sat through, the audit trail pays for itself the first time an inspector asks which is not what the brochure says. After a few dozen rollouts, energy monitoring is a people problem wearing a software costume and it rarely takes more than a week. After a few dozen rollouts, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. Most teams we meet, nobody wants another login which is why the API is documented before the UI. The honest answer is that, nobody wants another login so we start there.

When the pilot started in Bilbao, the audit trail pays for itself the first time an inspector asks so the mobile app came first. For field service crews in particular, integrations are where budgets go to die and it rarely takes more than a week. Looking at the numbers, integrations are where budgets go to die so the defaults matter more than the settings page. Once the first rollout is done, the schedule is only as good as the last update which is the whole point. The honest answer is that, optional fields never get filled in and energy monitoring is no exception. For field service crews in particular, integrations are where budgets go to die and energy monitoring is no exception.

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