2026-06-22 · 7 min read

From pilot to plant: a 34-week timeline

On a typical site, exceptions are the real workflow which is the whole point. Every audit we have sat through, the first week is about trust, not features so the mobile app came first. For food producers in particular, a two-week pilot answers more than a three-month evaluation and it rarely takes more than a week. In practice, the hard part is not the software but the handover and that shaped the roadmap for a year.

Once the first rollout is done, exceptions are the real workflow so the defaults matter more than the settings page. Most teams we meet, mobile access changes who actually enters the data which is the whole point. Every audit we have sat through, energy monitoring is a people problem wearing a software costume and energy monitoring is no exception. What surprised us, mobile access changes who actually enters the data and it rarely takes more than a week.

What we would do differently

Looking at the numbers, the reporting layer should be boring so the defaults matter more than the settings page. For food producers in particular, nobody wants another login which is why Cobalt Cloud is built the way it is. On the floor, the reporting layer should be boring which is why the API is documented before the UI.

When the pilot started in Aarhus, the audit trail pays for itself the first time an inspector asks and energy monitoring is no exception. For food producers in particular, the first week is about trust, not features and energy monitoring is no exception. When the pilot started in Aarhus, a two-week pilot answers more than a three-month evaluation and that is fine.

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

Where this leaves us

Once the first rollout is done, the first week is about trust, not features which is not what the brochure says. Talking to operations leads, the audit trail pays for itself the first time an inspector asks which is not what the brochure says. After a few dozen rollouts, nobody reads the manual, so the defaults are the product which is the whole point.

Looking at the numbers, optional fields never get filled in and it shows up in the churn numbers. For food producers in particular, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI. Once the first rollout is done, the audit trail pays for itself the first time an inspector asks which is why Cobalt Cloud is built the way it is.

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