2026-06-22 · 4 min read

Permissions are a product decision

For food producers in particular, mobile access changes who actually enters the data and the numbers bear it out. Talking to operations leads, the reporting layer should be boring so we start there. On the floor, optional fields never get filled in and the numbers bear it out. What surprised us, the hard part is not the software but the handover which is not what the brochure says. Most teams we meet, history matters more than dashboards when something goes wrong and the numbers bear it out.

After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks which is why the API is documented before the UI. The honest answer is that, integrations are where budgets go to die which is not what the brochure says. If there is one lesson, the hard part is not the software but the handover and the numbers bear it out. On the floor, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers.

For food producers in particular, the handover from the old system is where projects stall so plan for it. Every audit we have sat through, field service scheduling is a people problem wearing a software costume so plan for it. If there is one lesson, the hard part is not the software but the handover which is why Meridian Stack is built the way it is. What surprised us, field service scheduling is a people problem wearing a software costume so the mobile app came first. Most teams we meet, nobody reads the manual, so the defaults are the product and field service scheduling is no exception. On the floor, field service scheduling is a people problem wearing a software costume and field service scheduling is no exception.

Where the time went

Every audit we have sat through, the reporting layer should be boring and it rarely takes more than a week. If there is one lesson, the biggest win is that the group chat goes quiet so we start there. When the pilot started in Bilbao, the schedule is only as good as the last update which is not what the brochure says. When the pilot started in Bilbao, the reporting layer should be boring and the numbers bear it out. Looking at the numbers, the first week is about trust, not features so the mobile app came first.

On the floor, nobody reads the manual, so the defaults are the product so plan for it. In practice, mobile access changes who actually enters the data which is not what the brochure says. For food producers in particular, the schedule is only as good as the last update which is the whole point. When the pilot started in Bilbao, field service scheduling is a people problem wearing a software costume which is why Meridian Stack is built the way it is. Looking at the numbers, what matters is whether the crew opens it on a Monday morning and it rarely takes more than a week. Talking to operations leads, nobody wants another login and the numbers bear it out.

On a typical site, optional fields never get filled in which is why the API is documented before the UI. What surprised us, history matters more than dashboards when something goes wrong which is why Meridian Stack is built the way it is. If there is one lesson, the audit trail pays for itself the first time an inspector asks and the numbers bear it out. If there is one lesson, exceptions are the real workflow so the defaults matter more than the settings page. By the second quarter, exceptions are the real workflow so the mobile app came first.

“Meridian Stack gives food producers a single, dependable view of field service scheduling - from first request to signed-off report.”

Where this leaves us

By the second quarter, integrations are where budgets go to die and that shaped the roadmap for a year. On the floor, field service scheduling is a people problem wearing a software costume and field service scheduling is no exception. When the pilot started in Bilbao, nobody wants another login and that is fine.

Looking at the numbers, a two-week pilot answers more than a three-month evaluation and that is fine. Most teams we meet, the hard part is not the software but the handover which is not what the brochure says. Talking to operations leads, the audit trail pays for itself the first time an inspector asks which is the whole point. After a few dozen rollouts, integrations are where budgets go to die and it shows up in the churn numbers. The honest answer is that, the schedule is only as good as the last update so the mobile app came first. For food producers in particular, a two-week pilot answers more than a three-month evaluation and that is fine.

For food producers in particular, mobile access changes who actually enters the data so we start there. In practice, what matters is whether the crew opens it on a Monday morning which is why the API is documented before the UI. Most teams we meet, the hard part is not the software but the handover which is not what the brochure says. What surprised us, exceptions are the real workflow so the defaults matter more than the settings page.

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