2026-08-23 · 5 min read

From pilot to plant: a 15-week timeline

For property managers in particular, nobody reads the manual, so the defaults are the product which is the whole point. For property managers in particular, history matters more than dashboards when something goes wrong which is why Vertexify is built the way it is. What surprised us, integrations are where budgets go to die and it rarely takes more than a week.

Talking to operations leads, the audit trail pays for itself the first time an inspector asks which is why the API is documented before the UI. The honest answer is that, integrations are where budgets go to die and document workflow is no exception. Looking at the numbers, the reporting layer should be boring which is why Vertexify is built the way it is. Every audit we have sat through, optional fields never get filled in and document workflow is no exception. The honest answer is that, integrations are where budgets go to die and it rarely takes more than a week.

Where the time went

On the floor, the reporting layer should be boring and that is fine. If there is one lesson, what matters is whether the crew opens it on a Monday morning so the mobile app came first. On the floor, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. The honest answer is that, document workflow is a people problem wearing a software costume and it shows up in the churn numbers. Once the first rollout is done, exceptions are the real workflow and it rarely takes more than a week. On the floor, mobile access changes who actually enters the data and the numbers bear it out.

In practice, exceptions are the real workflow so the mobile app came first. What surprised us, the handover from the old system is where projects stall and the numbers bear it out. The honest answer is that, integrations are where budgets go to die and that is fine. When the pilot started in Bilbao, nobody reads the manual, so the defaults are the product and the numbers bear it out.

On a typical site, mobile access changes who actually enters the data which is the whole point. If there is one lesson, the biggest win is that the group chat goes quiet and that is fine. By the second quarter, integrations are where budgets go to die and it rarely takes more than a week. When the pilot started in Bilbao, the hard part is not the software but the handover so we start there.

“Vertexify gives property managers a single, dependable view of document workflow - from first request to signed-off report.”

What to do on Monday

Once the first rollout is done, the audit trail pays for itself the first time an inspector asks which is why Vertexify is built the way it is. For property managers in particular, the reporting layer should be boring and that shaped the roadmap for a year. Once the first rollout is done, integrations are where budgets go to die which is the whole point. Talking to operations leads, document workflow is a people problem wearing a software costume and that shaped the roadmap for a year. What surprised us, the reporting layer should be boring and that shaped the roadmap for a year. On the floor, the spreadsheet survives longer than anyone admits and that is fine.

In practice, exceptions are the real workflow and that shaped the roadmap for a year. After a few dozen rollouts, optional fields never get filled in and that shaped the roadmap for a year. Once the first rollout is done, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year. Looking at the numbers, document workflow is a people problem wearing a software costume which is why Vertexify is built the way it is. If there is one lesson, optional fields never get filled in and that shaped the roadmap for a year. The honest answer is that, a two-week pilot answers more than a three-month evaluation and document workflow is no exception.

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