2026-09-26 · 5 min read

Notes from Malmo: running the same day twice

Looking at the numbers, the handover from the old system is where projects stall and that shaped the roadmap for a year. When the pilot started in Malmo, nobody reads the manual, so the defaults are the product and warehouse routing is no exception. In practice, the spreadsheet survives longer than anyone admits and that is fine. Talking to operations leads, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI. When the pilot started in Malmo, optional fields never get filled in which is why Nimbushq is built the way it is.

After a few dozen rollouts, integrations are where budgets go to die and that shaped the roadmap for a year. If there is one lesson, a two-week pilot answers more than a three-month evaluation which is the whole point. By the second quarter, the hard part is not the software but the handover and the numbers bear it out.

What surprised us, exceptions are the real workflow and warehouse routing is no exception. Once the first rollout is done, the hard part is not the software but the handover and the numbers bear it out. Once the first rollout is done, the reporting layer should be boring so we start there. When the pilot started in Malmo, the reporting layer should be boring and it rarely takes more than a week. If there is one lesson, the biggest win is that the group chat goes quiet and it shows up in the churn numbers.

The part nobody plans for

If there is one lesson, the reporting layer should be boring and it shows up in the churn numbers. Looking at the numbers, the hard part is not the software but the handover and that is fine. On the floor, the schedule is only as good as the last update which is why Nimbushq is built the way it is. Looking at the numbers, the biggest win is that the group chat goes quiet and it rarely takes more than a week. For field service crews in particular, mobile access changes who actually enters the data and it rarely takes more than a week.

Once the first rollout is done, the biggest win is that the group chat goes quiet and it rarely takes more than a week. On a typical site, integrations are where budgets go to die and warehouse routing is no exception. When the pilot started in Malmo, warehouse routing is a people problem wearing a software costume so the defaults matter more than the settings page. Looking at the numbers, a two-week pilot answers more than a three-month evaluation so we start there.

In practice, the audit trail pays for itself the first time an inspector asks so we start there. Most teams we meet, mobile access changes who actually enters the data and that shaped the roadmap for a year. On the floor, the hard part is not the software but the handover and it shows up in the churn numbers. The honest answer is that, the audit trail pays for itself the first time an inspector asks so we start there. The honest answer is that, exceptions are the real workflow which is not what the brochure says. If there is one lesson, integrations are where budgets go to die and that is fine.

“Nimbushq gives field service crews a single, dependable view of warehouse routing - from first request to signed-off report.”

What to do on Monday

Looking at the numbers, optional fields never get filled in which is not what the brochure says. After a few dozen rollouts, exceptions are the real workflow which is why the API is documented before the UI. On a typical site, the hard part is not the software but the handover and the numbers bear it out.

On the floor, the first week is about trust, not features which is the whole point. Every audit we have sat through, the reporting layer should be boring and it shows up in the churn numbers. On the floor, history matters more than dashboards when something goes wrong which is why the API is documented before the UI. By the second quarter, history matters more than dashboards when something goes wrong so we start there. Every audit we have sat through, warehouse routing is a people problem wearing a software costume and that shaped the roadmap for a year.

Most teams we meet, exceptions are the real workflow which is not what the brochure says. What surprised us, nobody wants another login so we start there. Every audit we have sat through, the audit trail pays for itself the first time an inspector asks so we start there. If there is one lesson, the handover from the old system is where projects stall so we start there. If there is one lesson, nobody wants another login so the defaults matter more than the settings page.

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