2026-06-02 · 5 min read

Offline first is not a feature, it is a promise

By the second quarter, the reporting layer should be boring which is the whole point. On a typical site, the biggest win is that the group chat goes quiet and it rarely takes more than a week. Looking at the numbers, document workflow is a people problem wearing a software costume and it rarely takes more than a week.

For logistics teams in particular, integrations are where budgets go to die and that shaped the roadmap for a year. Every audit we have sat through, nobody reads the manual, so the defaults are the product so we start there. On a typical site, mobile access changes who actually enters the data and that is fine. On the floor, the handover from the old system is where projects stall so the defaults matter more than the settings page. Talking to operations leads, integrations are where budgets go to die so we start there.

In practice, nobody wants another login and it shows up in the churn numbers. Most teams we meet, what matters is whether the crew opens it on a Monday morning so we start there. If there is one lesson, optional fields never get filled in and document workflow is no exception. The honest answer is that, a two-week pilot answers more than a three-month evaluation so we start there. Looking at the numbers, integrations are where budgets go to die and it shows up in the churn numbers.

What we would do differently

Every audit we have sat through, nobody wants another login so plan for it. When the pilot started in Bilbao, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI. Most teams we meet, what matters is whether the crew opens it on a Monday morning which is the whole point. Talking to operations leads, the first week is about trust, not features which is why Zenithio is built the way it is. If there is one lesson, document workflow is a people problem wearing a software costume which is the whole point.

After a few dozen rollouts, the schedule is only as good as the last update which is the whole point. On the floor, what matters is whether the crew opens it on a Monday morning which is why Zenithio is built the way it is. The honest answer is that, the hard part is not the software but the handover and it rarely takes more than a week. Most teams we meet, what matters is whether the crew opens it on a Monday morning which is why the API is documented before the UI. On a typical site, the handover from the old system is where projects stall and the numbers bear it out. Looking at the numbers, the handover from the old system is where projects stall and that shaped the roadmap for a year.

If there is one lesson, the hard part is not the software but the handover so the defaults matter more than the settings page. By the second quarter, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers. On a typical site, the reporting layer should be boring which is why Zenithio is built the way it is. What surprised us, integrations are where budgets go to die so the mobile app came first. If there is one lesson, optional fields never get filled in and it rarely takes more than a week.

“Everything logistics teams need to keep document workflow on schedule, on budget and on record.”

Takeaways

In practice, the reporting layer should be boring which is why the API is documented before the UI. What surprised us, the hard part is not the software but the handover and that is fine. Most teams we meet, exceptions are the real workflow which is why Zenithio is built the way it is. Once the first rollout is done, optional fields never get filled in and it shows up in the churn numbers.

Every audit we have sat through, the spreadsheet survives longer than anyone admits which is the whole point. If there is one lesson, integrations are where budgets go to die so the defaults matter more than the settings page. For logistics teams in particular, the hard part is not the software but the handover and document workflow is no exception.

The honest answer is that, the reporting layer should be boring which is the whole point. On the floor, the audit trail pays for itself the first time an inspector asks and that is fine. Every audit we have sat through, the reporting layer should be boring which is the whole point. When the pilot started in Bilbao, a two-week pilot answers more than a three-month evaluation and document workflow is no exception. In practice, history matters more than dashboards when something goes wrong so plan for it. By the second quarter, the reporting layer should be boring which is not what the brochure says.

Written by the Zenithio team in Bilbao. Questions? Get in touch.