2026-08-25 · 8 min read

The audit that changed our roadmap

When the pilot started in Bilbao, exceptions are the real workflow so we start there. For food producers in particular, the biggest win is that the group chat goes quiet and that shaped the roadmap for a year. What surprised us, the handover from the old system is where projects stall which is why the API is documented before the UI. After a few dozen rollouts, exceptions are the real workflow and the numbers bear it out. Once the first rollout is done, the hard part is not the software but the handover which is why the API is documented before the UI. Looking at the numbers, optional fields never get filled in and that is fine.

Talking to operations leads, exceptions are the real workflow which is not what the brochure says. What surprised us, the hard part is not the software but the handover and that is fine. When the pilot started in Bilbao, the reporting layer should be boring and field service scheduling is no exception. Most teams we meet, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week. If there is one lesson, the handover from the old system is where projects stall and it shows up in the churn numbers.

The honest answer is that, the spreadsheet survives longer than anyone admits and that shaped the roadmap for a year. Every audit we have sat through, the reporting layer should be boring which is not what the brochure says. On a typical site, the first week is about trust, not features which is why Meridian Stack is built the way it is.

What actually happened

When the pilot started in Bilbao, the spreadsheet survives longer than anyone admits which is the whole point. On a typical site, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page. When the pilot started in Bilbao, the first week is about trust, not features which is why the API is documented before the UI. Looking at the numbers, the spreadsheet survives longer than anyone admits so plan for it. After a few dozen rollouts, optional fields never get filled in and it shows up in the churn numbers.

Every audit we have sat through, integrations are where budgets go to die and the numbers bear it out. If there is one lesson, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year. On the floor, the biggest win is that the group chat goes quiet so the defaults matter more than the settings page. Every audit we have sat through, mobile access changes who actually enters the data so the defaults matter more than the settings page.

After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation which is the whole point. On a typical site, the first week is about trust, not features and it shows up in the churn numbers. When the pilot started in Bilbao, mobile access changes who actually enters the data and it shows up in the churn numbers. For food producers in particular, the schedule is only as good as the last update so we start there.

Every audit we have sat through, a two-week pilot answers more than a three-month evaluation which is why Meridian Stack is built the way it is. On a typical site, exceptions are the real workflow and it rarely takes more than a week. Talking to operations leads, field service scheduling is a people problem wearing a software costume and it rarely takes more than a week. Talking to operations leads, exceptions are the real workflow and the numbers bear it out. What surprised us, history matters more than dashboards when something goes wrong which is not what the brochure says. By the second quarter, the schedule is only as good as the last update and it shows up in the churn numbers.

“Everything food producers need to keep field service scheduling on schedule, on budget and on record.”

Where this leaves us

The honest answer is that, integrations are where budgets go to die so the defaults matter more than the settings page. Talking to operations leads, the reporting layer should be boring and it rarely takes more than a week. On the floor, the schedule is only as good as the last update and it shows up in the churn numbers. Talking to operations leads, field service scheduling is a people problem wearing a software costume so we start there.

After a few dozen rollouts, history matters more than dashboards when something goes wrong which is why the API is documented before the UI. When the pilot started in Bilbao, field service scheduling is a people problem wearing a software costume and it shows up in the churn numbers. The honest answer is that, integrations are where budgets go to die which is not what the brochure says. On a typical site, the reporting layer should be boring which is why the API is documented before the UI. The honest answer is that, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page.

Once the first rollout is done, the handover from the old system is where projects stall which is the whole point. When the pilot started in Bilbao, the spreadsheet survives longer than anyone admits which is not what the brochure says. Once the first rollout is done, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year. On a typical site, the audit trail pays for itself the first time an inspector asks which is not what the brochure says.

Written by the Meridian Stack team in Bilbao. Questions? Get in touch.