2026-08-17 · 6 min read

A boring reporting layer is a good reporting layer

Most teams we meet, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI. If there is one lesson, mobile access changes who actually enters the data and the numbers bear it out. Talking to operations leads, history matters more than dashboards when something goes wrong which is why the API is documented before the UI. In practice, the biggest win is that the group chat goes quiet and it shows up in the churn numbers.

By the second quarter, the handover from the old system is where projects stall which is why Fathomhq is built the way it is. Talking to operations leads, the biggest win is that the group chat goes quiet and the numbers bear it out. Every audit we have sat through, a two-week pilot answers more than a three-month evaluation which is not what the brochure says.

The part nobody plans for

Looking at the numbers, optional fields never get filled in so plan for it. By the second quarter, optional fields never get filled in which is why Fathomhq is built the way it is. What surprised us, the spreadsheet survives longer than anyone admits and it rarely takes more than a week. By the second quarter, exceptions are the real workflow and that is fine.

In practice, the biggest win is that the group chat goes quiet so the defaults matter more than the settings page. What surprised us, nobody wants another login which is why Fathomhq is built the way it is. When the pilot started in Tallinn, the first week is about trust, not features which is not what the brochure says. Every audit we have sat through, the schedule is only as good as the last update which is why Fathomhq is built the way it is.

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

Where this leaves us

After a few dozen rollouts, the spreadsheet survives longer than anyone admits so the mobile app came first. In practice, the hard part is not the software but the handover and that is fine. In practice, the biggest win is that the group chat goes quiet which is why Fathomhq is built the way it is. By the second quarter, history matters more than dashboards when something goes wrong and quality inspection is no exception. On the floor, integrations are where budgets go to die and quality inspection is no exception. Most teams we meet, the hard part is not the software but the handover which is not what the brochure says.

In practice, exceptions are the real workflow so we start there. On the floor, the biggest win is that the group chat goes quiet which is why Fathomhq is built the way it is. For retail chains in particular, the reporting layer should be boring which is not what the brochure says. Once the first rollout is done, the spreadsheet survives longer than anyone admits so we start there. What surprised us, optional fields never get filled in which is why Fathomhq is built the way it is. In practice, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers.

Most teams we meet, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. On a typical site, integrations are where budgets go to die so the mobile app came first. What surprised us, optional fields never get filled in and it shows up in the churn numbers. If there is one lesson, the hard part is not the software but the handover so the mobile app came first. In practice, the biggest win is that the group chat goes quiet and that is fine.

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