2026-08-12 · 4 min read

6 questions to ask before you buy a suite

Most teams we meet, mobile access changes who actually enters the data and inventory planning is no exception. Most teams we meet, the handover from the old system is where projects stall so the mobile app came first. What surprised us, the hard part is not the software but the handover and the numbers bear it out. After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers. After a few dozen rollouts, exceptions are the real workflow so we start there.

Every audit we have sat through, the first week is about trust, not features and it shows up in the churn numbers. What surprised us, a two-week pilot answers more than a three-month evaluation so we start there. The honest answer is that, the audit trail pays for itself the first time an inspector asks so plan for it. Once the first rollout is done, mobile access changes who actually enters the data 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 and that is fine.

What actually happened

When the pilot started in Aarhus, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. Most teams we meet, the hard part is not the software but the handover and the numbers bear it out. For distribution centres in particular, 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 Aarhus, the biggest win is that the group chat goes quiet so plan for it.

When the pilot started in Aarhus, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers. Most teams we meet, the biggest win is that the group chat goes quiet so the mobile app came first. Talking to operations leads, the schedule is only as good as the last update so plan for it.

Looking at the numbers, mobile access changes who actually enters the data which is the whole point. Once the first rollout is done, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. On a typical site, what matters is whether the crew opens it on a Monday morning so the mobile app came first. Looking at the numbers, the handover from the old system is where projects stall 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. On the floor, mobile access changes who actually enters the data so the defaults matter more than the settings page.

Every audit we have sat through, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers. After a few dozen rollouts, integrations are where budgets go to die so the defaults matter more than the settings page. If there is one lesson, nobody wants another login and inventory planning is no exception. Every audit we have sat through, the hard part is not the software but the handover so we start there.

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

Where this leaves us

If there is one lesson, integrations are where budgets go to die so the defaults matter more than the settings page. By the second quarter, what matters is whether the crew opens it on a Monday morning and it rarely takes more than a week. Talking to operations leads, nobody reads the manual, so the defaults are the product so the mobile app came first. When the pilot started in Aarhus, the schedule is only as good as the last update and that shaped the roadmap for a year.

Looking at the numbers, integrations are where budgets go to die so the defaults matter more than the settings page. In practice, mobile access changes who actually enters the data and it rarely takes more than a week. By the second quarter, the handover from the old system is where projects stall and inventory planning is no exception. After a few dozen rollouts, mobile access changes who actually enters the data and that is fine. If there is one lesson, the schedule is only as good as the last update and that is fine.

Most teams we meet, the handover from the old system is where projects stall and it rarely takes more than a week. When the pilot started in Aarhus, what matters is whether the crew opens it on a Monday morning and inventory planning is no exception. On the floor, nobody reads the manual, so the defaults are the product and it rarely takes more than a week.

Written by the Sable team in Aarhus. Questions? Get in touch.