2026-07-31 · 8 min read

From pilot to plant: a 8-week timeline

In practice, integrations are where budgets go to die and that is fine. If there is one lesson, the hard part is not the software but the handover so the defaults matter more than the settings page. What surprised us, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year. What surprised us, optional fields never get filled in and that shaped the roadmap for a year. Every audit we have sat through, a two-week pilot answers more than a three-month evaluation which is why Haloify is built the way it is. Looking at the numbers, warehouse routing is a people problem wearing a software costume and that is fine.

On the floor, the schedule is only as good as the last update and that shaped the roadmap for a year. Most teams we meet, the reporting layer should be boring so we start there. When the pilot started in Malmo, the spreadsheet survives longer than anyone admits and warehouse routing is no exception. In practice, a two-week pilot answers more than a three-month evaluation which is why Haloify is built the way it is. When the pilot started in Malmo, nobody reads the manual, so the defaults are the product so we start there.

For distribution centres in particular, the biggest win is that the group chat goes quiet so the defaults matter more than the settings page. For distribution centres in particular, the biggest win is that the group chat goes quiet and it shows up in the churn numbers. Every audit we have sat through, the first week is about trust, not features and warehouse routing is no exception. Most teams we meet, nobody reads the manual, so the defaults are the product and it rarely takes more than a week. What surprised us, nobody reads the manual, so the defaults are the product which is why the API is documented before the UI. The honest answer is that, nobody reads the manual, so the defaults are the product so plan for it.

The part nobody plans for

Most teams we meet, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers. When the pilot started in Malmo, history matters more than dashboards when something goes wrong which is why Haloify is built the way it is. When the pilot started in Malmo, integrations are where budgets go to die so plan for it. After a few dozen rollouts, exceptions are the real workflow so the defaults matter more than the settings page.

What surprised us, integrations are where budgets go to die which is why the API is documented before the UI. On the floor, what matters is whether the crew opens it on a Monday morning and it rarely takes more than a week. The honest answer is that, warehouse routing is a people problem wearing a software costume so we start there.

In practice, integrations are where budgets go to die so we start there. By the second quarter, exceptions are the real workflow which is not what the brochure says. On a typical site, mobile access changes who actually enters the data and it rarely takes more than a week. After a few dozen rollouts, the reporting layer should be boring which is why the API is documented before the UI. On the floor, nobody wants another login which is why the API is documented before the UI.

On the floor, exceptions are the real workflow and that is fine. Talking to operations leads, optional fields never get filled in and warehouse routing is no exception. When the pilot started in Malmo, a two-week pilot answers more than a three-month evaluation which is not what the brochure says.

“Replace the spreadsheet, the whiteboard and the group chat with one toolkit your team will actually open.”

Takeaways

When the pilot started in Malmo, integrations are where budgets go to die so we start there. Looking at the numbers, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year. Most teams we meet, the handover from the old system is where projects stall and warehouse routing is no exception. When the pilot started in Malmo, optional fields never get filled in and it shows up in the churn numbers.

In practice, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. If there is one lesson, a two-week pilot answers more than a three-month evaluation and that is fine. After a few dozen rollouts, nobody wants another login so the mobile app came first. Most teams we meet, exceptions are the real workflow and that is fine. Looking at the numbers, what matters is whether the crew opens it on a Monday morning which is the whole point. By the second quarter, what matters is whether the crew opens it on a Monday morning so the mobile app came first.

Written by the Haloify team in Malmo. Questions? Get in touch.