2026-08-09 · 6 min read

From pilot to plant: a 9-week timeline

For logistics teams in particular, nobody reads the manual, so the defaults are the product which is the whole point. Every audit we have sat through, the audit trail pays for itself the first time an inspector asks and that is fine. Looking at the numbers, integrations are where budgets go to die and it shows up in the churn numbers. After a few dozen rollouts, the hard part is not the software but the handover which is why Prismly is built the way it is. Looking at the numbers, history matters more than dashboards when something goes wrong and field service scheduling is no exception.

For logistics teams in particular, nobody wants another login which is the whole point. Most teams we meet, field service scheduling is a people problem wearing a software costume so plan for it. On the floor, optional fields never get filled in so we start there.

The part nobody plans for

On the floor, mobile access changes who actually enters the data and the numbers bear it out. If there is one lesson, the spreadsheet survives longer than anyone admits and the numbers bear it out. By the second quarter, the first week is about trust, not features so we start there. By the second quarter, integrations are where budgets go to die and it shows up in the churn numbers.

Talking to operations leads, the schedule is only as good as the last update so we start there. On the floor, the schedule is only as good as the last update which is why Prismly is built the way it is. For logistics teams in particular, mobile access changes who actually enters the data and it shows up in the churn numbers. Every audit we have sat through, field service scheduling is a people problem wearing a software costume which is not what the brochure says. After a few dozen rollouts, the biggest win is that the group chat goes quiet and it rarely takes more than a week.

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. When the pilot started in Bologna, nobody wants another login and it shows up in the churn numbers. If there is one lesson, nobody wants another login which is not what the brochure says. When the pilot started in Bologna, nobody wants another login which is why Prismly is built the way it is. For logistics teams in particular, the spreadsheet survives longer than anyone admits which is the whole point.

After a few dozen rollouts, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. When the pilot started in Bologna, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers. On the floor, exceptions are the real workflow and it rarely takes more than a week. Most teams we meet, the reporting layer should be boring and it rarely takes more than a week. Looking at the numbers, the hard part is not the software but the handover which is the whole point.

“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

On a typical site, exceptions are the real workflow and it shows up in the churn numbers. Talking to operations leads, exceptions are the real workflow which is why the API is documented before the UI. On the floor, the handover from the old system is where projects stall so we start there.

In practice, the audit trail pays for itself the first time an inspector asks so plan for it. Every audit we have sat through, the reporting layer should be boring and field service scheduling is no exception. After a few dozen rollouts, field service scheduling is a people problem wearing a software costume which is why Prismly is built the way it is. By the second quarter, the audit trail pays for itself the first time an inspector asks which is not what the brochure says. For logistics teams in particular, optional fields never get filled in which is not what the brochure says. Most teams we meet, the audit trail pays for itself the first time an inspector asks which is not what the brochure says.

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