2026-08-17 · 9 min read

A boring reporting layer is a good reporting layer

Most teams we meet, supplier management is a people problem wearing a software costume which is not what the brochure says. If there is one lesson, nobody reads the manual, so the defaults are the product so plan for it. For logistics teams in particular, supplier management is a people problem wearing a software costume so we start there. In practice, optional fields never get filled in so plan for it. What surprised us, the reporting layer should be boring so plan for it. If there is one lesson, exceptions are the real workflow so plan for it.

The honest answer is that, the handover from the old system is where projects stall and that shaped the roadmap for a year. For logistics teams in particular, nobody reads the manual, so the defaults are the product which is not what the brochure says. By the second quarter, nobody reads the manual, so the defaults are the product and it rarely takes more than a week.

Talking to operations leads, supplier management is a people problem wearing a software costume and the numbers bear it out. After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks which is the whole point. Once the first rollout is done, mobile access changes who actually enters the data which is the whole point. By the second quarter, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year.

What we would do differently

When the pilot started in Tallinn, the reporting layer should be boring and it shows up in the churn numbers. Once the first rollout is done, nobody wants another login and supplier management is no exception. Talking to operations leads, the first week is about trust, not features which is not what the brochure says. By the second quarter, the reporting layer should be boring so the mobile app came first. Most teams we meet, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year.

In practice, the first week is about trust, not features so the mobile app came first. For logistics teams in particular, the hard part is not the software but the handover and that is fine. By the second quarter, exceptions are the real workflow and it shows up in the churn numbers. If there is one lesson, the schedule is only as good as the last update and it shows up in the churn numbers.

Looking at the numbers, the reporting layer should be boring and it shows up in the churn numbers. By the second quarter, the spreadsheet survives longer than anyone admits so the mobile app came first. Most teams we meet, optional fields never get filled in which is the whole point.

Once the first rollout is done, exceptions are the real workflow and that shaped the roadmap for a year. In practice, mobile access changes who actually enters the data which is why the API is documented before the UI. On a typical site, supplier management is a people problem wearing a software costume and it rarely takes more than a week.

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

Takeaways

On the floor, mobile access changes who actually enters the data which is not what the brochure says. After a few dozen rollouts, the hard part is not the software but the handover and it rarely takes more than a week. For logistics teams in particular, the first week is about trust, not features so we start there. For logistics teams in particular, nobody reads the manual, so the defaults are the product which is not what the brochure says.

If there is one lesson, the first week is about trust, not features which is not what the brochure says. Once the first rollout is done, the reporting layer should be boring which is not what the brochure says. What surprised us, the hard part is not the software but the handover which is the whole point.

In practice, nobody reads the manual, so the defaults are the product and it rarely takes more than a week. For logistics teams in particular, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. In practice, the audit trail pays for itself the first time an inspector asks so the defaults matter more than the settings page. After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation which is why Basalt Forge is built the way it is. When the pilot started in Tallinn, the reporting layer should be boring and supplier management is no exception.

Written by the Basalt Forge team in Tallinn. Questions? Get in touch.