2026-06-25 · 8 min read

What changed in Vela this quarter

The honest answer is that, nobody reads the manual, so the defaults are the product so plan for it. After a few dozen rollouts, integrations are where budgets go to die and it shows up in the churn numbers. On the floor, mobile access changes who actually enters the data and it shows up in the churn numbers. Looking at the numbers, what matters is whether the crew opens it on a Monday morning which is not what the brochure says.

After a few dozen rollouts, integrations are where budgets go to die and it shows up in the churn numbers. The honest answer is that, what matters is whether the crew opens it on a Monday morning and the numbers bear it out. Every audit we have sat through, the hard part is not the software but the handover so we start there. When the pilot started in Bilbao, the handover from the old system is where projects stall so the mobile app came first.

The part nobody plans for

On the floor, supplier management is a people problem wearing a software costume and it shows up in the churn numbers. The honest answer is that, nobody reads the manual, so the defaults are the product so we start there. By the second quarter, the spreadsheet survives longer than anyone admits and it shows up in the churn numbers. In practice, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers. The honest answer is that, the biggest win is that the group chat goes quiet so the defaults matter more than the settings page. After a few dozen rollouts, nobody reads the manual, so the defaults are the product so the mobile app came first.

On the floor, the audit trail pays for itself the first time an inspector asks and the numbers bear it out. If there is one lesson, the spreadsheet survives longer than anyone admits 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 the whole point.

Every audit we have sat through, the schedule is only as good as the last update which is why Vela is built the way it is. In practice, the reporting layer should be boring which is why Vela is built the way it is. By the second quarter, nobody wants another login and that is fine. When the pilot started in Bilbao, integrations are where budgets go to die so the mobile app came first.

“Vela gives clinical labs a single, dependable view of supplier management - from first request to signed-off report.”

Takeaways

Once the first rollout is done, the schedule is only as good as the last update and it rarely takes more than a week. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. If there is one lesson, nobody reads the manual, so the defaults are the product and it rarely takes more than a week.

Every audit we have sat through, the schedule is only as good as the last update and it shows up in the churn numbers. When the pilot started in Bilbao, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. For clinical labs in particular, supplier management is a people problem wearing a software costume and the numbers bear it out. By the second quarter, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. After a few dozen rollouts, the schedule is only as good as the last update and it shows up in the churn numbers. After a few dozen rollouts, the hard part is not the software but the handover which is why Vela is built the way it is.

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