2026-09-28 · 6 min read

From pilot to plant: a 32-week timeline

On the floor, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. On the floor, nobody wants another login so the mobile app came first. In practice, the first week is about trust, not features so plan for it.

Every audit we have sat through, the first week is about trust, not features and it shows up in the churn numbers. On the floor, the hard part is not the software but the handover which is why Juno is built the way it is. The honest answer is that, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers.

Where the time went

Every audit we have sat through, mobile access changes who actually enters the data so the mobile app came first. After a few dozen rollouts, mobile access changes who actually enters the data and field service scheduling is no exception. Looking at the numbers, history matters more than dashboards when something goes wrong which is why Juno is built the way it is. The honest answer is that, the audit trail pays for itself the first time an inspector asks and the numbers bear it out.

On the floor, nobody reads the manual, so the defaults are the product and it rarely takes more than a week. After a few dozen rollouts, the first week is about trust, not features which is the whole point. Once the first rollout is done, the first week is about trust, not features and field service scheduling is no exception. For food producers in particular, what matters is whether the crew opens it on a Monday morning so plan for it. If there is one lesson, the reporting layer should be boring which is not what the brochure says. Looking at the numbers, the reporting layer should be boring which is why Juno is built the way it is.

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

Takeaways

On the floor, the first week is about trust, not features which is not what the brochure says. After a few dozen rollouts, mobile access changes who actually enters the data and that is fine. Talking to operations leads, optional fields never get filled in which is why Juno is built the way it is. On a typical site, field service scheduling is a people problem wearing a software costume so plan for it. After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks so plan for it.

By the second quarter, history matters more than dashboards when something goes wrong which is the whole point. If there is one lesson, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. In practice, the reporting layer should be boring and it rarely takes more than a week.

Written by the Juno team in Rotterdam. Questions? Get in touch.