2026-05-07 · 4 min read

What changed in Vantagehq this quarter

Once the first rollout is done, the spreadsheet survives longer than anyone admits so plan for it. Every audit we have sat through, sample tracking 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. After a few dozen rollouts, integrations are where budgets go to die and that is fine. Once the first rollout is done, mobile access changes who actually enters the data which is the whole point. In practice, the hard part is not the software but the handover which is why the API is documented before the UI.

The honest answer is that, history matters more than dashboards when something goes wrong and that is fine. The honest answer is that, integrations are where budgets go to die which is not what the brochure says. Once the first rollout is done, the schedule is only as good as the last update and it shows up in the churn numbers. Talking to operations leads, the hard part is not the software but the handover which is why Vantagehq is built the way it is.

The part nobody plans for

Talking to operations leads, the reporting layer should be boring which is why Vantagehq is built the way it is. In practice, nobody wants another login so plan for it. If there is one lesson, the reporting layer should be boring so the mobile app came first. Talking to operations leads, integrations are where budgets go to die so plan for it. Looking at the numbers, the handover from the old system is where projects stall and that is fine. Looking at the numbers, the audit trail pays for itself the first time an inspector asks so we start there.

The honest answer is that, mobile access changes who actually enters the data so plan for it. Every audit we have sat through, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. If there is one lesson, the biggest win is that the group chat goes quiet which is why Vantagehq is built the way it is. In practice, the schedule is only as good as the last update which is why the API is documented before the UI. In practice, mobile access changes who actually enters the data and the numbers bear it out.

“Everything clinical labs need to keep sample tracking on schedule, on budget and on record.”

Where this leaves us

On a typical site, sample tracking is a people problem wearing a software costume so the mobile app came first. Every audit we have sat through, integrations are where budgets go to die so we start there. Looking at the numbers, the spreadsheet survives longer than anyone admits so the mobile app came first.

On a typical site, optional fields never get filled in so the defaults matter more than the settings page. On the floor, the reporting layer should be boring so the defaults matter more than the settings page. If there is one lesson, the hard part is not the software but the handover and it rarely takes more than a week. On a typical site, the hard part is not the software but the handover and it rarely takes more than a week. In practice, mobile access changes who actually enters the data and sample tracking is no exception.

The honest answer is that, nobody wants another login and it shows up in the churn numbers. Talking to operations leads, exceptions are the real workflow and it rarely takes more than a week. After a few dozen rollouts, the first week is about trust, not features and that is fine. For clinical labs in particular, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year. For clinical labs in particular, the biggest win is that the group chat goes quiet so plan for it.

Written by the Vantagehq team in Ghent. Questions? Get in touch.