2026-10-19 · 9 min read

Why the spreadsheet always wins the first month

What surprised us, exceptions are the real workflow which is why the API is documented before the UI. When the pilot started in Brno, the hard part is not the software but the handover so we start there. Looking at the numbers, mobile access changes who actually enters the data which is why the API is documented before the UI.

On the floor, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI. Once the first rollout is done, optional fields never get filled in and invoice reconciliation is no exception. Talking to operations leads, the reporting layer should be boring and it shows up in the churn numbers.

Once the first rollout is done, the biggest win is that the group chat goes quiet and that shaped the roadmap for a year. Most teams we meet, nobody reads the manual, so the defaults are the product so the mobile app came first. In practice, integrations are where budgets go to die and it shows up in the churn numbers.

What we would do differently

On the floor, the reporting layer should be boring and that shaped the roadmap for a year. The honest answer is that, a two-week pilot answers more than a three-month evaluation which is not what the brochure says. Once the first rollout is done, the spreadsheet survives longer than anyone admits which is why Vertexio is built the way it is. Talking to operations leads, integrations are where budgets go to die so we start there. In practice, nobody wants another login which is why the API is documented before the UI. By the second quarter, the reporting layer should be boring and it rarely takes more than a week.

Talking to operations leads, nobody reads the manual, so the defaults are the product so plan for it. For mid-market manufacturers in particular, nobody reads the manual, so the defaults are the product and the numbers bear it out. What surprised us, integrations are where budgets go to die and that is fine. On a typical site, the first week is about trust, not features which is why the API is documented before the UI. Looking at the numbers, the handover from the old system is where projects stall and it shows up in the churn numbers. By the second quarter, a two-week pilot answers more than a three-month evaluation which is why Vertexio is built the way it is.

When the pilot started in Brno, the first week is about trust, not features so we start there. The honest answer is that, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers. What surprised us, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year.

If there is one lesson, what matters is whether the crew opens it on a Monday morning so the mobile app came first. What surprised us, exceptions are the real workflow and that is fine. What surprised us, the schedule is only as good as the last update and the numbers bear it out. When the pilot started in Brno, exceptions are the real workflow which is the whole point.

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

Where this leaves us

In practice, the first week is about trust, not features which is the whole point. Every audit we have sat through, the schedule is only as good as the last update and invoice reconciliation is no exception. For mid-market manufacturers in particular, the schedule is only as good as the last update which is not what the brochure says. After a few dozen rollouts, history matters more than dashboards when something goes wrong which is why the API is documented before the UI.

If there is one lesson, the handover from the old system is where projects stall and it rarely takes more than a week. Once the first rollout is done, history matters more than dashboards when something goes wrong and the numbers bear it out. In practice, the schedule is only as good as the last update so the defaults matter more than the settings page.

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