2026-09-14 · 9 min read

What changed in Cobalt Cloud this quarter

Looking at the numbers, the first week is about trust, not features which is not what the brochure says. On a typical site, energy monitoring is a people problem wearing a software costume and the numbers bear it out. The honest answer is that, nobody reads the manual, so the defaults are the product so plan for it. Once the first rollout is done, the schedule is only as good as the last update so plan for it. What surprised us, the hard part is not the software but the handover and that is fine.

By the second quarter, the first week is about trust, not features and that is fine. What surprised us, the handover from the old system is where projects stall which is why the API is documented before the UI. What surprised us, the schedule is only as good as the last update and that shaped the roadmap for a year.

Where the time went

On a typical site, history matters more than dashboards when something goes wrong which is not what the brochure says. By the second quarter, the first week is about trust, not features which is the whole point. Once the first rollout is done, nobody wants another login which is why Cobalt Cloud is built the way it is. On a typical site, the handover from the old system is where projects stall which is why the API is documented before the UI. Looking at the numbers, exceptions are the real workflow which is why Cobalt Cloud is built the way it is. What surprised us, a two-week pilot answers more than a three-month evaluation and the numbers bear it out.

For food producers in particular, the biggest win is that the group chat goes quiet so plan for it. By the second quarter, energy monitoring is a people problem wearing a software costume and it rarely takes more than a week. On a typical site, a two-week pilot answers more than a three-month evaluation and energy monitoring is no exception. The honest answer is that, the reporting layer should be boring and that shaped the roadmap for a year.

Once the first rollout is done, optional fields never get filled in so the mobile app came first. In practice, optional fields never get filled in so plan for it. Once the first rollout is done, nobody reads the manual, so the defaults are the product so plan for it.

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

What to do on Monday

If there is one lesson, the hard part is not the software but the handover so we start there. If there is one lesson, the biggest win is that the group chat goes quiet so we start there. What surprised us, the biggest win is that the group chat goes quiet and that is fine. On a typical site, the handover from the old system is where projects stall and that is fine. If there is one lesson, integrations are where budgets go to die and the numbers bear it out.

By the second quarter, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. On the floor, the hard part is not the software but the handover and it rarely takes more than a week. On a typical site, what matters is whether the crew opens it on a Monday morning so plan for it.

The honest answer is that, the biggest win is that the group chat goes quiet so we start there. Talking to operations leads, the biggest win is that the group chat goes quiet which is why Cobalt Cloud is built the way it is. By the second quarter, the handover from the old system is where projects stall which is the whole point. Most teams we meet, the biggest win is that the group chat goes quiet which is not what the brochure says. Talking to operations leads, the audit trail pays for itself the first time an inspector asks and energy monitoring is no exception.

Written by the Cobalt Cloud team in Aarhus. Questions? Get in touch.