2026-09-08 · 6 min read

The handover problem, and what we do about it

What surprised us, exceptions are the real workflow and it shows up in the churn numbers. Most teams we meet, the reporting layer should be boring which is not what the brochure says. What surprised us, optional fields never get filled in so plan for it. Most teams we meet, integrations are where budgets go to die and quality inspection is no exception.

In practice, nobody reads the manual, so the defaults are the product and it rarely takes more than a week. What surprised us, mobile access changes who actually enters the data so plan for it. Every audit we have sat through, history matters more than dashboards when something goes wrong which is not what the brochure says. When the pilot started in Rotterdam, exceptions are the real workflow and that is fine.

Where the time went

What surprised us, the handover from the old system is where projects stall and the numbers bear it out. Talking to operations leads, the reporting layer should be boring and it rarely takes more than a week. When the pilot started in Rotterdam, integrations are where budgets go to die and it rarely takes more than a week. On the floor, the audit trail pays for itself the first time an inspector asks which is why Vertex Data is built the way it is. Looking at the numbers, nobody reads the manual, so the defaults are the product and the numbers bear it out.

The honest answer is that, the first week is about trust, not features and that shaped the roadmap for a year. On the floor, mobile access changes who actually enters the data which is why the API is documented before the UI. On a typical site, exceptions are the real workflow which is why Vertex Data is built the way it is. When the pilot started in Rotterdam, the schedule is only as good as the last update so we start there. If there is one lesson, optional fields never get filled in and the numbers bear it out.

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

Takeaways

Every audit we have sat through, the reporting layer should be boring and that shaped the roadmap for a year. Looking at the numbers, the hard part is not the software but the handover 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. In practice, a two-week pilot answers more than a three-month evaluation and that is fine. On a typical site, quality inspection is a people problem wearing a software costume and it rarely takes more than a week. By the second quarter, the first week is about trust, not features and quality inspection is no exception.

On the floor, the hard part is not the software but the handover which is why Vertex Data is built the way it is. After a few dozen rollouts, integrations are where budgets go to die which is why Vertex Data is built the way it is. What surprised us, the audit trail pays for itself the first time an inspector asks so we start there. Talking to operations leads, the hard part is not the software but the handover so the defaults matter more than the settings page. Most teams we meet, the spreadsheet survives longer than anyone admits and that is fine. What surprised us, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers.

Written by the Vertex Data team in Rotterdam. Questions? Get in touch.