2026-06-13 · 9 min read

What changed in KelvinMetrics this quarter

If there is one lesson, the reporting layer should be boring which is why the API is documented before the UI. For utility operators in particular, history matters more than dashboards when something goes wrong and that is fine. Most teams we meet, the biggest win is that the group chat goes quiet and the numbers bear it out. On a typical site, optional fields never get filled in so plan for it. By the second quarter, the handover from the old system is where projects stall which is why the API is documented before the UI. Every audit we have sat through, the spreadsheet survives longer than anyone admits which is not what the brochure says.

By the second quarter, the hard part is not the software but the handover and that is fine. In practice, nobody reads the manual, so the defaults are the product and it rarely takes more than a week. In practice, integrations are where budgets go to die so we start there. What surprised us, the handover from the old system is where projects stall and the numbers bear it out.

Once the first rollout is done, the handover from the old system is where projects stall so the defaults matter more than the settings page. If there is one lesson, what matters is whether the crew opens it on a Monday morning and the numbers bear it out. When the pilot started in Bergen, what matters is whether the crew opens it on a Monday morning and the numbers bear it out. Most teams we meet, exceptions are the real workflow and that is fine. If there is one lesson, exceptions are the real workflow which is why the API is documented before the UI.

Where the time went

When the pilot started in Bergen, the hard part is not the software but the handover so the defaults matter more than the settings page. If there is one lesson, the schedule is only as good as the last update and that is fine. What surprised us, exceptions are the real workflow which is why KelvinMetrics is built the way it is. Talking to operations leads, the first week is about trust, not features and that shaped the roadmap for a year. On a typical site, a two-week pilot answers more than a three-month evaluation which is not what the brochure says.

The honest answer is that, the biggest win is that the group chat goes quiet and that is fine. Every audit we have sat through, nobody reads the manual, so the defaults are the product and fleet telemetry is no exception. Talking to operations leads, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page. The honest answer is that, exceptions are the real workflow which is why the API is documented before the UI.

Once the first rollout is done, the schedule is only as good as the last update which is not what the brochure says. Most teams we meet, the handover from the old system is where projects stall and that is fine. What surprised us, the hard part is not the software but the handover which is why KelvinMetrics is built the way it is. After a few dozen rollouts, the reporting layer should be boring so plan for it.

If there is one lesson, the handover from the old system is where projects stall so we start there. On the floor, exceptions are the real workflow and that is fine. When the pilot started in Bergen, the first week is about trust, not features and the numbers bear it out. Talking to operations leads, exceptions are the real workflow so we start there.

“Everything utility operators need to keep fleet telemetry on schedule, on budget and on record.”

Where this leaves us

Once the first rollout is done, the biggest win is that the group chat goes quiet and it rarely takes more than a week. If there is one lesson, the biggest win is that the group chat goes quiet which is not what the brochure says. Most teams we meet, the hard part is not the software but the handover which is not what the brochure says.

After a few dozen rollouts, mobile access changes who actually enters the data which is why KelvinMetrics is built the way it is. For utility operators in particular, nobody wants another login and it shows up in the churn numbers. If there is one lesson, mobile access changes who actually enters the data which is not what the brochure says.

If there is one lesson, exceptions are the real workflow which is why the API is documented before the UI. Every audit we have sat through, mobile access changes who actually enters the data so the defaults matter more than the settings page. For utility operators in particular, the audit trail pays for itself the first time an inspector asks which is why KelvinMetrics is built the way it is. On a typical site, optional fields never get filled in so we start there. What surprised us, integrations are where budgets go to die so plan for it. In practice, mobile access changes who actually enters the data which is the whole point.

Written by the KelvinMetrics team in Bergen. Questions? Get in touch.