2026-09-14 · 4 min read

23 questions to ask before you buy a workspace

Every audit we have sat through, the spreadsheet survives longer than anyone admits and the numbers bear it out. After a few dozen rollouts, mobile access changes who actually enters the data and that shaped the roadmap for a year. Every audit we have sat through, nobody wants another login so the mobile app came first. Once the first rollout is done, the reporting layer should be boring and that shaped the roadmap for a year.

For logistics teams in particular, the first week is about trust, not features which is not what the brochure says. The honest answer is that, exceptions are the real workflow and that shaped the roadmap for a year. Most teams we meet, the reporting layer should be boring which is why the API is documented before the UI.

The part nobody plans for

Once the first rollout is done, nobody wants another login so the defaults matter more than the settings page. Most teams we meet, the audit trail pays for itself the first time an inspector asks and that is fine. On a typical site, nobody wants another login and the numbers bear it out. Every audit we have sat through, optional fields never get filled in and it shows up in the churn numbers. Once the first rollout is done, the hard part is not the software but the handover and invoice reconciliation is no exception.

Every audit we have sat through, the biggest win is that the group chat goes quiet and that shaped the roadmap for a year. By the second quarter, the first week is about trust, not features so plan for it. Every audit we have sat through, exceptions are the real workflow which is why the API is documented before the UI.

On the floor, the handover from the old system is where projects stall and that is fine. On the floor, the audit trail pays for itself the first time an inspector asks so plan for it. On the floor, the reporting layer should be boring which is not what the brochure says. Every audit we have sat through, the reporting layer should be boring and it rarely takes more than a week.

“Everything logistics teams need to keep invoice reconciliation on schedule, on budget and on record.”

Takeaways

When the pilot started in Malmo, the first week is about trust, not features which is why Fathomly is built the way it is. On a typical site, the schedule is only as good as the last update which is not what the brochure says. Looking at the numbers, the handover from the old system is where projects stall so the defaults matter more than the settings page. The honest answer is that, what matters is whether the crew opens it on a Monday morning so plan for it.

Every audit we have sat through, the hard part is not the software but the handover which is why Fathomly is built the way it is. Most teams we meet, the reporting layer should be boring so the defaults matter more than the settings page. On a typical site, what matters is whether the crew opens it on a Monday morning so we start there. Talking to operations leads, the schedule is only as good as the last update so the defaults matter more than the settings page. Talking to operations leads, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers.

In practice, invoice reconciliation is a people problem wearing a software costume so the defaults matter more than the settings page. By the second quarter, mobile access changes who actually enters the data so the mobile app came first. For logistics teams in particular, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. On the floor, exceptions are the real workflow and it shows up in the churn numbers.

Written by the Fathomly team in Malmo. Questions? Get in touch.