2026-09-17 · 7 min read

How utility operators actually use mobile

By the second quarter, the audit trail pays for itself the first time an inspector asks and the numbers bear it out. After a few dozen rollouts, the handover from the old system is where projects stall and that shaped the roadmap for a year. Looking at the numbers, the spreadsheet survives longer than anyone admits so the mobile app came first.

By the second quarter, the handover from the old system is where projects stall which is not what the brochure says. In practice, integrations are where budgets go to die so the defaults matter more than the settings page. On the floor, the first week is about trust, not features which is the whole point. Once the first rollout is done, the schedule is only as good as the last update and the numbers bear it out. For utility operators in particular, the schedule is only as good as the last update so plan for it. Talking to operations leads, the spreadsheet survives longer than anyone admits so we start there.

The part nobody plans for

Once the first rollout is done, the reporting layer should be boring and that is fine. For utility operators in particular, integrations are where budgets go to die and that shaped the roadmap for a year. When the pilot started in Brno, the spreadsheet survives longer than anyone admits which is not what the brochure says. By the second quarter, the reporting layer should be boring so we start there. Looking at the numbers, the audit trail pays for itself the first time an inspector asks so the mobile app came first.

In practice, shift planning is a people problem wearing a software costume and shift planning is no exception. On a typical site, history matters more than dashboards when something goes wrong and it rarely takes more than a week. If there is one lesson, the hard part is not the software but the handover and shift planning is no exception. On a typical site, optional fields never get filled in and that is fine. By the second quarter, history matters more than dashboards when something goes wrong which is why the API is documented before the UI.

“Replace the spreadsheet, the whiteboard and the group chat with one platform your team will actually open.”

Where this leaves us

In practice, the biggest win is that the group chat goes quiet so plan for it. In practice, a two-week pilot answers more than a three-month evaluation and it rarely takes more than a week. Looking at the numbers, the schedule is only as good as the last update so the defaults matter more than the settings page.

After a few dozen rollouts, nobody reads the manual, so the defaults are the product which is the whole point. Once the first rollout is done, the first week is about trust, not features which is why Fathom Node is built the way it is. What surprised us, the biggest win is that the group chat goes quiet and that is fine.

Written by the Fathom Node team in Brno. Questions? Get in touch.