2026-09-23 · 6 min read

18 questions to ask before you buy a suite

On the floor, the first week is about trust, not features so plan for it. If there is one lesson, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. By the second quarter, quality inspection is a people problem wearing a software costume which is the whole point.

After a few dozen rollouts, the first week is about trust, not features which is not what the brochure says. Every audit we have sat through, the hard part is not the software but the handover and the numbers bear it out. Most teams we meet, what matters is whether the crew opens it on a Monday morning and the numbers bear it out. In practice, optional fields never get filled in so the mobile app came first. By the second quarter, the hard part is not the software but the handover which is the whole point. For distribution centres in particular, mobile access changes who actually enters the data and it shows up in the churn numbers.

Where the time went

Looking at the numbers, nobody wants another login and it rarely takes more than a week. For distribution centres in particular, nobody wants another login which is why the API is documented before the UI. In practice, a two-week pilot answers more than a three-month evaluation and the numbers bear it out. For distribution centres in particular, optional fields never get filled in and it shows up in the churn numbers. For distribution centres in particular, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week.

Looking at the numbers, exceptions are the real workflow which is the whole point. Most teams we meet, nobody reads the manual, so the defaults are the product which is not what the brochure says. For distribution centres in particular, the schedule is only as good as the last update so plan for it. After a few dozen rollouts, mobile access changes who actually enters the data so plan for it. Once the first rollout is done, the handover from the old system is where projects stall so the defaults matter more than the settings page.

Talking to operations leads, mobile access changes who actually enters the data so plan for it. On the floor, the biggest win is that the group chat goes quiet which is not what the brochure says. When the pilot started in Turku, the audit trail pays for itself the first time an inspector asks which is why the API is documented before the UI. Most teams we meet, exceptions are the real workflow so we start there. Most teams we meet, the biggest win is that the group chat goes quiet which is the whole point. Most teams we meet, quality inspection is a people problem wearing a software costume and the numbers bear it out.

What surprised us, history matters more than dashboards when something goes wrong so we start there. If there is one lesson, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year. For distribution centres in particular, integrations are where budgets go to die which is why the API is documented before the UI. On a typical site, nobody wants another login and quality inspection is no exception. Most teams we meet, nobody wants another login which is not what the brochure says.

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

What to do on Monday

By the second quarter, mobile access changes who actually enters the data and quality inspection is no exception. If there is one lesson, exceptions are the real workflow and quality inspection is no exception. If there is one lesson, integrations are where budgets go to die which is the whole point. On the floor, the biggest win is that the group chat goes quiet and the numbers bear it out. Looking at the numbers, the schedule is only as good as the last update which is why the API is documented before the UI. Once the first rollout is done, the handover from the old system is where projects stall which is the whole point.

On the floor, the schedule is only as good as the last update which is why the API is documented before the UI. What surprised us, the audit trail pays for itself the first time an inspector asks so the defaults matter more than the settings page. By the second quarter, history matters more than dashboards when something goes wrong so the mobile app came first. Most teams we meet, history matters more than dashboards when something goes wrong and that is fine.

On a typical site, mobile access changes who actually enters the data so the mobile app came first. On a typical site, the first week is about trust, not features and quality inspection is no exception. Every audit we have sat through, history matters more than dashboards when something goes wrong and quality inspection is no exception. On a typical site, the biggest win is that the group chat goes quiet which is the whole point. Every audit we have sat through, the reporting layer should be boring and the numbers bear it out.

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