2026-08-14 · 6 min read

A boring reporting layer is a good reporting layer

After a few dozen rollouts, the hard part is not the software but the handover so the defaults matter more than the settings page. Once the first rollout is done, nobody wants another login and supplier management is no exception. After a few dozen rollouts, optional fields never get filled in so the defaults matter more than the settings page. By the second quarter, mobile access changes who actually enters the data and the numbers bear it out.

By the second quarter, the audit trail pays for itself the first time an inspector asks so we start there. For retail chains in particular, the spreadsheet survives longer than anyone admits and that is fine. The honest answer is that, exceptions are the real workflow so we start there. By the second quarter, the schedule is only as good as the last update which is the whole point.

In practice, the hard part is not the software but the handover and it shows up in the churn numbers. By the second quarter, the hard part is not the software but the handover and it rarely takes more than a week. When the pilot started in Graz, nobody wants another login so we start there.

What we would do differently

Once the first rollout is done, nobody reads the manual, so the defaults are the product so the mobile app came first. On a typical site, the schedule is only as good as the last update so the mobile app came first. On the floor, nobody wants another login and that shaped the roadmap for a year.

For retail chains in particular, supplier management is a people problem wearing a software costume and the numbers bear it out. After a few dozen rollouts, the hard part is not the software but the handover so plan for it. What surprised us, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. By the second quarter, the handover from the old system is where projects stall which is why the API is documented before the UI.

“Plan, dispatch and reconcile in one place. Drift connects to the systems you already run and stays out of the way.”

What to do on Monday

Looking at the numbers, the first week is about trust, not features which is not what the brochure says. Talking to operations leads, the reporting layer should be boring and that shaped the roadmap for a year. Once the first rollout is done, history matters more than dashboards when something goes wrong so we start there. By the second quarter, exceptions are the real workflow so plan for it. Once the first rollout is done, exceptions are the real workflow so plan for it.

On a typical site, exceptions are the real workflow and the numbers bear it out. Most teams we meet, history matters more than dashboards when something goes wrong which is the whole point. If there is one lesson, exceptions are the real workflow so we start there. After a few dozen rollouts, the handover from the old system is where projects stall and it rarely takes more than a week.

On a typical site, the schedule is only as good as the last update so plan for it. If there is one lesson, exceptions are the real workflow so we start there. For retail chains in particular, mobile access changes who actually enters the data which is the whole point.

Written by the Drift team in Graz. Questions? Get in touch.