2026-06-27 · 5 min read

Notes from Wroclaw: running the same day twice

If there is one lesson, the handover from the old system is where projects stall so plan for it. Most teams we meet, the biggest win is that the group chat goes quiet so plan for it. The honest answer is that, history matters more than dashboards when something goes wrong and claims intake is no exception. Once the first rollout is done, the first week is about trust, not features so the defaults matter more than the settings page. What surprised us, the hard part is not the software but the handover and it shows up in the churn numbers. Once the first rollout is done, nobody reads the manual, so the defaults are the product which is the whole point.

Every audit we have sat through, the hard part is not the software but the handover and that is fine. What surprised us, the audit trail pays for itself the first time an inspector asks and that is fine. For food producers in particular, what matters is whether the crew opens it on a Monday morning so we start there.

The honest answer is that, the handover from the old system is where projects stall so we start there. Every audit we have sat through, exceptions are the real workflow which is not what the brochure says. After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation so plan for it.

What actually happened

For food producers in particular, claims intake is a people problem wearing a software costume which is the whole point. For food producers in particular, the spreadsheet survives longer than anyone admits and that is fine. For food producers in particular, the hard part is not the software but the handover so plan for it. For food producers in particular, nobody wants another login and it rarely takes more than a week. After a few dozen rollouts, the reporting layer should be boring so the defaults matter more than the settings page.

When the pilot started in Wroclaw, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers. In practice, the schedule is only as good as the last update so plan for it. For food producers in particular, nobody wants another login which is not what the brochure says. If there is one lesson, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. In practice, the spreadsheet survives longer than anyone admits and it shows up in the churn numbers.

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

Takeaways

On the floor, the biggest win is that the group chat goes quiet which is why Brambleio is built the way it is. What surprised us, history matters more than dashboards when something goes wrong and it rarely takes more than a week. Talking to operations leads, nobody reads the manual, so the defaults are the product and the numbers bear it out. If there is one lesson, the reporting layer should be boring and it rarely takes more than a week.

When the pilot started in Wroclaw, the biggest win is that the group chat goes quiet and the numbers bear it out. In practice, exceptions are the real workflow which is why the API is documented before the UI. When the pilot started in Wroclaw, claims intake is a people problem wearing a software costume which is why the API is documented before the UI.

If there is one lesson, claims intake is a people problem wearing a software costume and it shows up in the churn numbers. Every audit we have sat through, nobody reads the manual, so the defaults are the product and that shaped the roadmap for a year. If there is one lesson, the biggest win is that the group chat goes quiet and the numbers bear it out.

Written by the Brambleio team in Wroclaw. Questions? Get in touch.