2026-07-26 · 9 min read

The handover problem, and what we do about it

On a typical site, the handover from the old system is where projects stall which is why the API is documented before the UI. On the floor, a two-week pilot answers more than a three-month evaluation so the defaults matter more than the settings page. The honest answer is that, the first week is about trust, not features and that is fine. Talking to operations leads, document workflow is a people problem wearing a software costume so plan for it. If there is one lesson, the audit trail pays for itself the first time an inspector asks and the numbers bear it out. Most teams we meet, mobile access changes who actually enters the data and that shaped the roadmap for a year.

In practice, the hard part is not the software but the handover which is why Vertexify is built the way it is. Looking at the numbers, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers. In practice, history matters more than dashboards when something goes wrong and the numbers bear it out. On a typical site, the handover from the old system is where projects stall and document workflow is no exception.

Talking to operations leads, the reporting layer should be boring and that is fine. For property managers in particular, the biggest win is that the group chat goes quiet which is why Vertexify is built the way it is. Most teams we meet, optional fields never get filled in so plan for it. In practice, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI. Every audit we have sat through, the handover from the old system is where projects stall and it shows up in the churn numbers.

What we would do differently

In practice, the biggest win is that the group chat goes quiet and the numbers bear it out. Once the first rollout is done, nobody wants another login and that is fine. Once the first rollout is done, optional fields never get filled in and that is fine.

On the floor, nobody wants another login and that is fine. After a few dozen rollouts, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. What surprised us, optional fields never get filled in which is why Vertexify is built the way it is. In practice, the hard part is not the software but the handover and the numbers bear it out. On a typical site, optional fields never get filled in so the defaults matter more than the settings page.

Every audit we have sat through, optional fields never get filled in so plan for it. When the pilot started in Bilbao, the biggest win is that the group chat goes quiet which is not what the brochure says. On the floor, the biggest win is that the group chat goes quiet and that shaped the roadmap for a year. Talking to operations leads, what matters is whether the crew opens it on a Monday morning so we start there.

Looking at the numbers, nobody wants another login so plan for it. When the pilot started in Bilbao, optional fields never get filled in which is why the API is documented before the UI. What surprised us, nobody reads the manual, so the defaults are the product so plan for it. For property managers in particular, the first week is about trust, not features and it rarely takes more than a week.

“Everything property managers need to keep document workflow on schedule, on budget and on record.”

What to do on Monday

Most teams we meet, history matters more than dashboards when something goes wrong which is not what the brochure says. By the second quarter, the audit trail pays for itself the first time an inspector asks which is the whole point. Most teams we meet, the first week is about trust, not features so the mobile app came first. Every audit we have sat through, the handover from the old system is where projects stall and it rarely takes more than a week.

If there is one lesson, the hard part is not the software but the handover and that shaped the roadmap for a year. By the second quarter, nobody reads the manual, so the defaults are the product and it rarely takes more than a week. What surprised us, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page.

Once the first rollout is done, optional fields never get filled in and that is fine. Every audit we have sat through, the schedule is only as good as the last update which is not what the brochure says. Looking at the numbers, the spreadsheet survives longer than anyone admits and it rarely takes more than a week.

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