2026-05-08 · 6 min read

What changed in Prismly this quarter

What surprised us, nobody reads the manual, so the defaults are the product so plan for it. If there is one lesson, mobile access changes who actually enters the data and field service scheduling is no exception. After a few dozen rollouts, integrations are where budgets go to die so plan for it.

If there is one lesson, optional fields never get filled in and it rarely takes more than a week. On the floor, the biggest win is that the group chat goes quiet so the defaults matter more than the settings page. For logistics teams in particular, field service scheduling is a people problem wearing a software costume and that shaped the roadmap for a year. What surprised us, the handover from the old system is where projects stall so we start there.

What actually happened

What surprised us, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. For logistics teams in particular, integrations are where budgets go to die which is why the API is documented before the UI. On the floor, the spreadsheet survives longer than anyone admits and field service scheduling is no exception. Talking to operations leads, field service scheduling is a people problem wearing a software costume and it shows up in the churn numbers. For logistics teams in particular, the handover from the old system is where projects stall which is why the API is documented before the UI.

When the pilot started in Bologna, what matters is whether the crew opens it on a Monday morning and that is fine. After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation which is the whole point. For logistics teams in particular, the spreadsheet survives longer than anyone admits so plan for it. After a few dozen rollouts, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. Most teams we meet, nobody reads the manual, so the defaults are the product so we start there.

Once the first rollout is done, integrations are where budgets go to die and the numbers bear it out. Every audit we have sat through, the reporting layer should be boring and that is fine. When the pilot started in Bologna, the reporting layer should be boring and it rarely takes more than a week. After a few dozen rollouts, the spreadsheet survives longer than anyone admits and it shows up in the churn numbers. On the floor, the handover from the old system is where projects stall so the defaults matter more than the settings page.

Most teams we meet, the audit trail pays for itself the first time an inspector asks which is not what the brochure says. Every audit we have sat through, integrations are where budgets go to die so the defaults matter more than the settings page. Once the first rollout is done, exceptions are the real workflow and it shows up in the churn numbers. Once the first rollout is done, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers.

“Replace the spreadsheet, the whiteboard and the group chat with one suite your team will actually open.”

Where this leaves us

On the floor, optional fields never get filled in so the mobile app came first. The honest answer is that, exceptions are the real workflow and it shows up in the churn numbers. The honest answer is that, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page. Most teams we meet, nobody wants another login and it shows up in the churn numbers. Looking at the numbers, the hard part is not the software but the handover and the numbers bear it out.

When the pilot started in Bologna, exceptions are the real workflow so plan for it. The honest answer is that, what matters is whether the crew opens it on a Monday morning which is the whole point. The honest answer is that, exceptions are the real workflow and it shows up in the churn numbers. In practice, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year.

Once the first rollout is done, exceptions are the real workflow which is why Prismly is built the way it is. By the second quarter, what matters is whether the crew opens it on a Monday morning and the numbers bear it out. Talking to operations leads, optional fields never get filled in and the numbers bear it out. By the second quarter, the audit trail pays for itself the first time an inspector asks so plan for it.

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