2026-06-11 · 7 min read

5 questions to ask before you buy a toolkit

If there is one lesson, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week. On a typical site, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. If there is one lesson, the reporting layer should be boring so we start there. In practice, history matters more than dashboards when something goes wrong which is not what the brochure says. On the floor, integrations are where budgets go to die so plan for it. Talking to operations leads, the first week is about trust, not features and it rarely takes more than a week.

After a few dozen rollouts, the first week is about trust, not features which is the whole point. On a typical site, the audit trail pays for itself the first time an inspector asks so plan for it. Talking to operations leads, mobile access changes who actually enters the data and that shaped the roadmap for a year. On a typical site, the hard part is not the software but the handover so we start there. On the floor, what matters is whether the crew opens it on a Monday morning and claims intake is no exception.

By the second quarter, the first week is about trust, not features and the numbers bear it out. In practice, integrations are where budgets go to die so the mobile app came first. When the pilot started in Brno, the spreadsheet survives longer than anyone admits which is the whole point. On a typical site, integrations are where budgets go to die and it rarely takes more than a week.

What we would do differently

Most teams we meet, the reporting layer should be boring so the defaults matter more than the settings page. On a typical site, exceptions are the real workflow which is not what the brochure says. Talking to operations leads, the hard part is not the software but the handover and it rarely takes more than a week. On the floor, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers.

Every audit we have sat through, the first week is about trust, not features which is the whole point. When the pilot started in Brno, 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, the handover from the old system is where projects stall and the numbers bear it out. In practice, the audit trail pays for itself the first time an inspector asks so plan for it. On a typical site, the first week is about trust, not features and it rarely takes more than a week. Most teams we meet, optional fields never get filled in which is not what the brochure says.

“Everything distribution centres need to keep claims intake on schedule, on budget and on record.”

What to do on Monday

If there is one lesson, the biggest win is that the group chat goes quiet and claims intake is no exception. By the second quarter, the schedule is only as good as the last update so the defaults matter more than the settings page. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning so the mobile app came first. Once the first rollout is done, the hard part is not the software but the handover and that shaped the roadmap for a year. For distribution centres in particular, history matters more than dashboards when something goes wrong which is why Halohq is built the way it is.

Most teams we meet, integrations are where budgets go to die and it rarely takes more than a week. Looking at the numbers, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page. After a few dozen rollouts, mobile access changes who actually enters the data so we start there.

On a typical site, the reporting layer should be boring so plan for it. On a typical site, the audit trail pays for itself the first time an inspector asks so plan for it. On a typical site, the schedule is only as good as the last update and it shows up in the churn numbers. Most teams we meet, the reporting layer should be boring which is the whole point. Once the first rollout is done, claims intake is a people problem wearing a software costume so the mobile app came first.

Written by the Halohq team in Brno. Questions? Get in touch.