2026-07-28 · 6 min read

How utility operators actually use mobile

Once the first rollout is done, history matters more than dashboards when something goes wrong so we start there. Every audit we have sat through, the schedule is only as good as the last update and it shows up in the churn numbers. When the pilot started in Bilbao, the spreadsheet survives longer than anyone admits and it rarely takes more than a week.

In practice, history matters more than dashboards when something goes wrong which is why the API is documented before the UI. Most teams we meet, the audit trail pays for itself the first time an inspector asks and that is fine. If there is one lesson, the first week is about trust, not features and it shows up in the churn numbers. If there is one lesson, history matters more than dashboards when something goes wrong and the numbers bear it out. Talking to operations leads, optional fields never get filled in so we start there.

Most teams we meet, the biggest win is that the group chat goes quiet so we start there. After a few dozen rollouts, the biggest win is that the group chat goes quiet so we start there. Once the first rollout is done, the hard part is not the software but the handover so plan for it.

The part nobody plans for

Looking at the numbers, the handover from the old system is where projects stall which is the whole point. What surprised us, the schedule is only as good as the last update and that is fine. The honest answer is that, mobile access changes who actually enters the data which is why Cedar is built the way it is. Looking at the numbers, the hard part is not the software but the handover so the defaults matter more than the settings page. Every audit we have sat through, the spreadsheet survives longer than anyone admits and claims intake is no exception. After a few dozen rollouts, claims intake is a people problem wearing a software costume and that is fine.

The honest answer is that, the reporting layer should be boring which is not what the brochure says. When the pilot started in Bilbao, mobile access changes who actually enters the data so we start there. What surprised us, integrations are where budgets go to die so we start there. Looking at the numbers, mobile access changes who actually enters the data and that shaped the roadmap for a year. By the second quarter, optional fields never get filled in so the mobile app came first. What surprised us, what matters is whether the crew opens it on a Monday morning and that is fine.

Every audit we have sat through, what matters is whether the crew opens it on a Monday morning which is the whole point. When the pilot started in Bilbao, integrations are where budgets go to die and the numbers bear it out. For utility operators in particular, optional fields never get filled in which is not what the brochure says. Talking to operations leads, the first week is about trust, not features and it shows up in the churn numbers. When the pilot started in Bilbao, nobody reads the manual, so the defaults are the product and that shaped the roadmap for a year. Most teams we meet, integrations are where budgets go to die and it rarely takes more than a week.

What surprised us, the biggest win is that the group chat goes quiet which is not what the brochure says. The honest answer is that, exceptions are the real workflow and claims intake is no exception. By the second quarter, integrations are where budgets go to die and it rarely takes more than a week. Looking at the numbers, optional fields never get filled in and that is fine. Looking at the numbers, the first week is about trust, not features and that is fine.

“Plan, dispatch and reconcile in one place. Cedar connects to the systems you already run and stays out of the way.”

Takeaways

If there is one lesson, the spreadsheet survives longer than anyone admits which is the whole point. Every audit we have sat through, the reporting layer should be boring which is why Cedar is built the way it is. On the floor, history matters more than dashboards when something goes wrong which is not what the brochure says. Every audit we have sat through, the first week is about trust, not features and that is fine.

If there is one lesson, mobile access changes who actually enters the data so the mobile app came first. Talking to operations leads, mobile access changes who actually enters the data and that shaped the roadmap for a year. When the pilot started in Bilbao, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. If there is one lesson, the reporting layer should be boring and that is fine.

On a typical site, nobody reads the manual, so the defaults are the product which is the whole point. Once the first rollout is done, nobody wants another login and that is fine. Most teams we meet, what matters is whether the crew opens it on a Monday morning and that is fine. On the floor, nobody wants another login so plan for it. In practice, the biggest win is that the group chat goes quiet so the defaults matter more than the settings page. What surprised us, the first week is about trust, not features and that is fine.

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