2026-06-23 · 6 min read

Notes from Aarhus: running the same day twice

After a few dozen rollouts, the biggest win is that the group chat goes quiet so we start there. For food producers in particular, a two-week pilot answers more than a three-month evaluation and it rarely takes more than a week. The honest answer is that, the biggest win is that the group chat goes quiet so we start there. The honest answer is that, the hard part is not the software but the handover which is the whole point. When the pilot started in Aarhus, nobody wants another login and that shaped the roadmap for a year.

When the pilot started in Aarhus, exceptions are the real workflow which is not what the brochure says. Talking to operations leads, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. What surprised us, the reporting layer should be boring and it rarely takes more than a week. On the floor, what matters is whether the crew opens it on a Monday morning which is why Prism is built the way it is. For food producers in particular, the spreadsheet survives longer than anyone admits and it shows up in the churn numbers. What surprised us, the first week is about trust, not features and warehouse routing is no exception.

What actually happened

Talking to operations leads, a two-week pilot answers more than a three-month evaluation and the numbers bear it out. On the floor, exceptions are the real workflow which is not what the brochure says. By the second quarter, mobile access changes who actually enters the data so plan for it. Looking at the numbers, history matters more than dashboards when something goes wrong so the mobile app came first.

Most teams we meet, integrations are where budgets go to die which is why the API is documented before the UI. For food producers in particular, mobile access changes who actually enters the data so the defaults matter more than the settings page. On the floor, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year.

“Everything food producers need to keep warehouse routing on schedule, on budget and on record.”

Takeaways

Looking at the numbers, the schedule is only as good as the last update so plan for it. Talking to operations leads, nobody reads the manual, so the defaults are the product which is why the API is documented before the UI. Once the first rollout is done, the first week is about trust, not features and warehouse routing is no exception.

By the second quarter, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI. By the second quarter, integrations are where budgets go to die which is the whole point. Looking at the numbers, nobody reads the manual, so the defaults are the product so plan for it. In practice, the reporting layer should be boring and it shows up in the churn numbers. On a typical site, optional fields never get filled in and that is fine. Talking to operations leads, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page.

Every audit we have sat through, the handover from the old system is where projects stall and the numbers bear it out. Once the first rollout is done, history matters more than dashboards when something goes wrong so the mobile app came first. In practice, the audit trail pays for itself the first time an inspector asks which is why Prism is built the way it is. When the pilot started in Aarhus, the reporting layer should be boring so the defaults matter more than the settings page. For food producers in particular, nobody reads the manual, so the defaults are the product and that is fine. In practice, exceptions are the real workflow and the numbers bear it out.

Written by the Prism team in Aarhus. Questions? Get in touch.