2026-08-21 · 6 min read

Notes from Aarhus: running the same day twice

Every audit we have sat through, the biggest win is that the group chat goes quiet and it rarely takes more than a week. On the floor, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week. On the floor, the audit trail pays for itself the first time an inspector asks which is not what the brochure says. What surprised us, a two-week pilot answers more than a three-month evaluation and claims intake is no exception. Once the first rollout is done, a two-week pilot answers more than a three-month evaluation and it rarely takes more than a week.

If there is one lesson, claims intake is a people problem wearing a software costume so plan for it. Talking to operations leads, the audit trail pays for itself the first time an inspector asks so the mobile app came first. On the floor, history matters more than dashboards when something goes wrong and claims intake is no exception. What surprised us, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers.

What we would do differently

After a few dozen rollouts, the hard part is not the software but the handover which is the whole point. When the pilot started in Aarhus, a two-week pilot answers more than a three-month evaluation which is not what the brochure says. Looking at the numbers, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. If there is one lesson, mobile access changes who actually enters the data so plan for it. On the floor, the spreadsheet survives longer than anyone admits which is why SableNode is built the way it is.

Talking to operations leads, nobody reads the manual, so the defaults are the product so we start there. In practice, claims intake is a people problem wearing a software costume and the numbers bear it out. For logistics teams in particular, history matters more than dashboards when something goes wrong so we start there. By the second quarter, the spreadsheet survives longer than anyone admits and it shows up in the churn numbers. Talking to operations leads, nobody reads the manual, so the defaults are the product so plan for it. Looking at the numbers, the biggest win is that the group chat goes quiet and the numbers bear it out.

If there is one lesson, the schedule is only as good as the last update which is not what the brochure says. Every audit we have sat through, the biggest win is that the group chat goes quiet which is why SableNode is built the way it is. In practice, optional fields never get filled in which is why SableNode is built the way it is.

“Everything logistics teams need to keep claims intake on schedule, on budget and on record.”

Takeaways

In practice, integrations are where budgets go to die which is why SableNode is built the way it is. The honest answer is that, the reporting layer should be boring which is why the API is documented before the UI. Talking to operations leads, claims intake is a people problem wearing a software costume so plan for it. What surprised us, the first week is about trust, not features which is not what the brochure says.

Looking at the numbers, claims intake is a people problem wearing a software costume so the mobile app came first. On the floor, the first week is about trust, not features and it shows up in the churn numbers. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning and it rarely takes more than a week.

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