2026-05-31 · 6 min read

From pilot to plant: a 27-week timeline

What surprised us, optional fields never get filled in and the numbers bear it out. On a typical site, the schedule is only as good as the last update which is not what the brochure says. Most teams we meet, sample tracking is a people problem wearing a software costume and that shaped the roadmap for a year. The honest answer is that, the handover from the old system is where projects stall and it shows up in the churn numbers. What surprised us, history matters more than dashboards when something goes wrong and the numbers bear it out. For distribution centres in particular, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers.

The honest answer is that, a two-week pilot answers more than a three-month evaluation which is why Prismly is built the way it is. The honest answer is that, nobody reads the manual, so the defaults are the product which is why the API is documented before the UI. When the pilot started in Turku, mobile access changes who actually enters the data which is the whole point.

The part nobody plans for

In practice, nobody wants another login and the numbers bear it out. When the pilot started in Turku, exceptions are the real workflow and that is fine. After a few dozen rollouts, the spreadsheet survives longer than anyone admits which is the whole point.

The honest answer is that, a two-week pilot answers more than a three-month evaluation so plan for it. In practice, the first week is about trust, not features so we start there. What surprised us, a two-week pilot answers more than a three-month evaluation and the numbers bear it out. Most teams we meet, mobile access changes who actually enters the data which is not what the brochure says.

If there is one lesson, the schedule is only as good as the last update so the mobile app came first. Looking at the numbers, history matters more than dashboards when something goes wrong so the defaults matter more than the settings page. Looking at the numbers, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. For distribution centres in particular, optional fields never get filled in and that shaped the roadmap for a year.

“Plan, dispatch and reconcile in one place. Prismly connects to the systems you already run and stays out of the way.”

What to do on Monday

After a few dozen rollouts, the reporting layer should be boring and that shaped the roadmap for a year. On a typical site, what matters is whether the crew opens it on a Monday morning so we start there. When the pilot started in Turku, history matters more than dashboards when something goes wrong and sample tracking is no exception. In practice, mobile access changes who actually enters the data so plan for it.

If there is one lesson, the biggest win is that the group chat goes quiet which is not what the brochure says. Once the first rollout is done, sample tracking is a people problem wearing a software costume so plan for it. Every audit we have sat through, the schedule is only as good as the last update 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 and that is fine.

By the second quarter, the schedule is only as good as the last update which is why Prismly is built the way it is. On the floor, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers. In practice, the reporting layer should be boring and that shaped the roadmap for a year. When the pilot started in Turku, optional fields never get filled in so the mobile app came first. Most teams we meet, the schedule is only as good as the last update so the mobile app came first.

Written by the Prismly team in Turku. Questions? Get in touch.