2026-08-30 · 6 min read

What changed in Fathomhq this quarter

For retail chains in particular, history matters more than dashboards when something goes wrong so plan for it. After a few dozen rollouts, nobody wants another login which is why the API is documented before the UI. By the second quarter, optional fields never get filled in and quality inspection is no exception. Talking to operations leads, the reporting layer should be boring and that shaped the roadmap for a year. After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI.

Talking to operations leads, quality inspection is a people problem wearing a software costume so plan for it. In practice, mobile access changes who actually enters the data and it shows up in the churn numbers. For retail chains in particular, the schedule is only as good as the last update and that shaped the roadmap for a year. Looking at the numbers, the first week is about trust, not features and the numbers bear it out. By the second quarter, integrations are where budgets go to die so the mobile app came first. Looking at the numbers, mobile access changes who actually enters the data so plan for it.

Every audit we have sat through, what matters is whether the crew opens it on a Monday morning so the mobile app came first. By the second quarter, optional fields never get filled in which is the whole point. The honest answer is that, nobody wants another login and it shows up in the churn numbers. If there is one lesson, the reporting layer should be boring which is why the API is documented before the UI.

What actually happened

Looking at the numbers, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. On a typical site, what matters is whether the crew opens it on a Monday morning which is why Fathomhq is built the way it is. After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks so the defaults matter more than the settings page.

In practice, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers. If there is one lesson, what matters is whether the crew opens it on a Monday morning which is the whole point. After a few dozen rollouts, history matters more than dashboards when something goes wrong so the mobile app came first. For retail chains in particular, optional fields never get filled in which is not what the brochure says.

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

Takeaways

On a typical site, history matters more than dashboards when something goes wrong which is the whole point. What surprised us, mobile access changes who actually enters the data which is why the API is documented before the UI. On the floor, the schedule is only as good as the last update and it rarely takes more than a week.

What surprised us, exceptions are the real workflow and the numbers bear it out. In practice, the reporting layer should be boring which is why the API is documented before the UI. In practice, the schedule is only as good as the last update so plan for it. By the second quarter, exceptions are the real workflow so the defaults matter more than the settings page.

If there is one lesson, nobody reads the manual, so the defaults are the product which is the whole point. When the pilot started in Tallinn, the audit trail pays for itself the first time an inspector asks which is why Fathomhq is built the way it is. In practice, the first week is about trust, not features and quality inspection is no exception. Most teams we meet, mobile access changes who actually enters the data so plan for it.

Written by the Fathomhq team in Tallinn. Questions? Get in touch.