2026-05-02 · 9 min read

Why the spreadsheet always wins the first month

What surprised us, nobody reads the manual, so the defaults are the product which is why the API is documented before the UI. Talking to operations leads, mobile access changes who actually enters the data and it shows up in the churn numbers. What surprised us, integrations are where budgets go to die and inventory planning is no exception. Talking to operations leads, mobile access changes who actually enters the data so the mobile app came first.

After a few dozen rollouts, exceptions are the real workflow so we start there. When the pilot started in Aarhus, inventory planning is a people problem wearing a software costume and the numbers bear it out. On a typical site, the schedule is only as good as the last update and it shows up in the churn numbers. Most teams we meet, the schedule is only as good as the last update and that is fine. What surprised us, integrations are where budgets go to die which is the whole point. Every audit we have sat through, the biggest win is that the group chat goes quiet which is why the API is documented before the UI.

The part nobody plans for

What surprised us, the first week is about trust, not features which is the whole point. On a typical site, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers. Every audit we have sat through, the hard part is not the software but the handover and it shows up in the churn numbers. When the pilot started in Aarhus, the handover from the old system is where projects stall which is not what the brochure says.

Once the first rollout is done, the biggest win is that the group chat goes quiet and inventory planning is no exception. Most teams we meet, exceptions are the real workflow and that is fine. On the floor, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page. Talking to operations leads, the schedule is only as good as the last update and it rarely takes more than a week.

“Sable gives distribution centres a single, dependable view of inventory planning - from first request to signed-off report.”

Where this leaves us

Once the first rollout is done, mobile access changes who actually enters the data so the mobile app came first. Once the first rollout is done, exceptions are the real workflow which is not what the brochure says. For distribution centres in particular, inventory planning is a people problem wearing a software costume which is not what the brochure says. Talking to operations leads, the biggest win is that the group chat goes quiet and it rarely takes more than a week. When the pilot started in Aarhus, mobile access changes who actually enters the data and it rarely takes more than a week.

Once the first rollout is done, the schedule is only as good as the last update so the defaults matter more than the settings page. For distribution centres in particular, the hard part is not the software but the handover and the numbers bear it out. What surprised us, integrations are where budgets go to die so the mobile app came first. Talking to operations leads, a two-week pilot answers more than a three-month evaluation so plan for it.

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