2026-08-25 · 5 min read

What changed in Fathom Node this quarter

In practice, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page. Talking to operations leads, exceptions are the real workflow and it rarely takes more than a week. In practice, integrations are where budgets go to die and shift planning is no exception.

After a few dozen rollouts, shift planning is a people problem wearing a software costume and shift planning is no exception. By the second quarter, exceptions are the real workflow so the defaults matter more than the settings page. If there is one lesson, shift planning is a people problem wearing a software costume and it shows up in the churn numbers.

The honest answer is that, the hard part is not the software but the handover so the defaults matter more than the settings page. Looking at the numbers, integrations are where budgets go to die so the mobile app came first. In practice, the spreadsheet survives longer than anyone admits which is the whole point. Every audit we have sat through, the hard part is not the software but the handover so the defaults matter more than the settings page. By the second quarter, the first week is about trust, not features and that is fine.

What we would do differently

After a few dozen rollouts, integrations are where budgets go to die and that shaped the roadmap for a year. Every audit we have sat through, nobody wants another login so the mobile app came first. When the pilot started in Brno, the first week is about trust, not features so the defaults matter more than the settings page. Once the first rollout is done, the reporting layer should be boring which is why Fathom Node is built the way it is. Every audit we have sat through, integrations are where budgets go to die and it rarely takes more than a week.

Talking to operations leads, mobile access changes who actually enters the data so the mobile app came first. If there is one lesson, the reporting layer should be boring so the mobile app came first. On the floor, the reporting layer should be boring and that is fine. In practice, the first week is about trust, not features and shift planning is no exception. For utility operators in particular, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. On a typical site, integrations are where budgets go to die and shift planning is no exception.

“Fathom Node gives utility operators a single, dependable view of shift planning - from first request to signed-off report.”

Where this leaves us

Every audit we have sat through, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. The honest answer is that, the schedule is only as good as the last update and it rarely takes more than a week. The honest answer is that, nobody wants another login so the mobile app came first. For utility operators in particular, mobile access changes who actually enters the data and that is fine. The honest answer is that, the spreadsheet survives longer than anyone admits and the numbers bear it out. On a typical site, exceptions are the real workflow so plan for it.

Most teams we meet, shift planning is a people problem wearing a software costume and that shaped the roadmap for a year. Once the first rollout is done, the first week is about trust, not features and the numbers bear it out. Looking at the numbers, shift planning is a people problem wearing a software costume so we start there.

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