2026-08-18 · 5 min read

The audit that changed our roadmap

On a typical site, claims intake is a people problem wearing a software costume so we start there. On a typical site, history matters more than dashboards when something goes wrong and that is fine. If there is one lesson, nobody wants another login which is not what the brochure says. When the pilot started in Wroclaw, the spreadsheet survives longer than anyone admits and that shaped the roadmap for a year.

Most teams we meet, integrations are where budgets go to die so the defaults matter more than the settings page. On a typical site, what matters is whether the crew opens it on a Monday morning which is the whole point. If there is one lesson, the hard part is not the software but the handover and it shows up in the churn numbers. Every audit we have sat through, mobile access changes who actually enters the data and that is fine.

The part nobody plans for

What surprised us, nobody wants another login so we start there. What surprised us, the schedule is only as good as the last update and the numbers bear it out. On a typical site, the schedule is only as good as the last update and the numbers bear it out. If there is one lesson, the audit trail pays for itself the first time an inspector asks so the mobile app came first. Looking at the numbers, what matters is whether the crew opens it on a Monday morning which is not what the brochure says.

When the pilot started in Wroclaw, the schedule is only as good as the last update which is why Brambleio is built the way it is. On the floor, the biggest win is that the group chat goes quiet and that is fine. When the pilot started in Wroclaw, history matters more than dashboards when something goes wrong and it rarely takes more than a week.

“Everything food producers need to keep claims intake on schedule, on budget and on record.”

Where this leaves us

For food producers in particular, nobody wants another login which is not what the brochure says. On a typical site, the reporting layer should be boring so we start there. On the floor, the hard part is not the software but the handover which is the whole point.

After a few dozen rollouts, the spreadsheet survives longer than anyone admits and it shows up in the churn numbers. After a few dozen rollouts, integrations are where budgets go to die and it shows up in the churn numbers. If there is one lesson, nobody reads the manual, so the defaults are the product so the mobile app came first. If there is one lesson, mobile access changes who actually enters the data and claims intake is no exception. If there is one lesson, nobody wants another login and the numbers bear it out.

Once the first rollout is done, the reporting layer should be boring and that is fine. Talking to operations leads, the reporting layer should be boring 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.

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