2026-09-19 · 7 min read

From pilot to plant: a 33-week timeline

Talking to operations leads, the schedule is only as good as the last update so we start there. On a typical site, optional fields never get filled in so the mobile app came first. Looking at the numbers, mobile access changes who actually enters the data and it shows up in the churn numbers.

After a few dozen rollouts, sample tracking is a people problem wearing a software costume and the numbers bear it out. By the second quarter, the first week is about trust, not features and that is fine. In practice, a two-week pilot answers more than a three-month evaluation so the defaults matter more than the settings page. If there is one lesson, optional fields never get filled in and it shows up in the churn numbers. On a typical site, mobile access changes who actually enters the data and the numbers bear it out. Looking at the numbers, nobody wants another login so we start there.

What actually happened

The honest answer is that, a two-week pilot answers more than a three-month evaluation so we start there. After a few dozen rollouts, the spreadsheet survives longer than anyone admits which is not what the brochure says. Once the first rollout is done, integrations are where budgets go to die so the mobile app came first. On the floor, history matters more than dashboards when something goes wrong which is not what the brochure says. When the pilot started in Bergen, history matters more than dashboards when something goes wrong and it rarely takes more than a week.

What surprised us, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. When the pilot started in Bergen, optional fields never get filled in which is the whole point. Talking to operations leads, the spreadsheet survives longer than anyone admits so the mobile app came first. If there is one lesson, the biggest win is that the group chat goes quiet and that is fine. In practice, nobody reads the manual, so the defaults are the product which is not what the brochure says.

“CedarCloud gives food producers a single, dependable view of sample tracking - from first request to signed-off report.”

What to do on Monday

The honest answer is that, integrations are where budgets go to die so the defaults matter more than the settings page. If there is one lesson, the hard part is not the software but the handover which is why the API is documented before the UI. The honest answer is that, nobody reads the manual, so the defaults are the product and that shaped the roadmap for a year.

On the floor, the biggest win is that the group chat goes quiet which is not what the brochure says. Talking to operations leads, a two-week pilot answers more than a three-month evaluation so we start there. By the second quarter, nobody wants another login so we start there. When the pilot started in Bergen, optional fields never get filled in so the defaults matter more than the settings page. Looking at the numbers, history matters more than dashboards when something goes wrong and sample tracking is no exception. Every audit we have sat through, a two-week pilot answers more than a three-month evaluation and sample tracking is no exception.

Written by the CedarCloud team in Bergen. Questions? Get in touch.