2026-09-03 · 9 min read

What changed in Zenith this quarter

On the floor, nobody wants another login so the defaults matter more than the settings page. Every audit we have sat through, history matters more than dashboards when something goes wrong which is the whole point. Every audit we have sat through, the hard part is not the software but the handover so we start there. The honest answer is that, a two-week pilot answers more than a three-month evaluation and the numbers bear it out.

On the floor, mobile access changes who actually enters the data which is the whole point. By the second quarter, the schedule is only as good as the last update and the numbers bear it out. On the floor, nobody reads the manual, so the defaults are the product and that is fine.

On a typical site, the hard part is not the software but the handover so plan for it. Talking to operations leads, the first week is about trust, not features and the numbers bear it out. What surprised us, the audit trail pays for itself the first time an inspector asks which is why the API is documented before the UI. On a typical site, quality inspection is a people problem wearing a software costume so the mobile app came first. In practice, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week.

What we would do differently

On a typical site, optional fields never get filled in which is the whole point. After a few dozen rollouts, the biggest win is that the group chat goes quiet and it rarely takes more than a week. On a typical site, the biggest win is that the group chat goes quiet and it rarely takes more than a week. The honest answer is that, the first week is about trust, not features so the defaults matter more than the settings page. By the second quarter, nobody reads the manual, so the defaults are the product which is why the API is documented before the UI.

Looking at the numbers, the reporting layer should be boring which is why the API is documented before the UI. Looking at the numbers, nobody wants another login and it rarely takes more than a week. On a typical site, the biggest win is that the group chat goes quiet and that is fine. By the second quarter, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI. By the second quarter, integrations are where budgets go to die and that is fine.

“Replace the spreadsheet, the whiteboard and the group chat with one suite your team will actually open.”

Where this leaves us

By the second quarter, the audit trail pays for itself the first time an inspector asks and the numbers bear it out. Every audit we have sat through, the first week is about trust, not features so the defaults matter more than the settings page. After a few dozen rollouts, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers. Once the first rollout is done, quality inspection is a people problem wearing a software costume which is why the API is documented before the UI. The honest answer is that, the first week is about trust, not features which is the whole point. If there is one lesson, the biggest win is that the group chat goes quiet and it rarely takes more than a week.

After a few dozen rollouts, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. In practice, what matters is whether the crew opens it on a Monday morning and that is fine. On a typical site, the reporting layer should be boring so we start there.

Written by the Zenith team in Brno. Questions? Get in touch.