2026-05-02 · 8 min read

From pilot to plant: a 16-week timeline

In practice, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. Every audit we have sat through, nobody reads the manual, so the defaults are the product which is why the API is documented before the UI. If there is one lesson, the reporting layer should be boring so plan for it.

On a typical site, the biggest win is that the group chat goes quiet so plan for it. For logistics teams in particular, supplier management is a people problem wearing a software costume which is not what the brochure says. If there is one lesson, the handover from the old system is where projects stall and supplier management is no exception. Once the first rollout is done, nobody reads the manual, so the defaults are the product which is why Basalt Forge is built the way it is. Once the first rollout is done, the reporting layer should be boring which is why Basalt Forge is built the way it is. The honest answer is that, nobody wants another login which is the whole point.

In practice, the audit trail pays for itself the first time an inspector asks which is why Basalt Forge is built the way it is. What surprised us, exceptions are the real workflow so the mobile app came first. For logistics teams in particular, nobody wants another login which is the whole point.

What we would do differently

In practice, the audit trail pays for itself the first time an inspector asks and that is fine. Once the first rollout is done, the reporting layer should be boring and the numbers bear it out. On a typical site, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers.

Looking at the numbers, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year. After a few dozen rollouts, mobile access changes who actually enters the data and it rarely takes more than a week. The honest answer is that, what matters is whether the crew opens it on a Monday morning which is not what the brochure says.

In practice, nobody wants another login so plan for it. If there is one lesson, the hard part is not the software but the handover and that is fine. If there is one lesson, mobile access changes who actually enters the data and that shaped the roadmap for a year.

By the second quarter, integrations are where budgets go to die so plan for it. If there is one lesson, the spreadsheet survives longer than anyone admits 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. Looking at the numbers, supplier management is a people problem wearing a software costume so the mobile app came first.

“Basalt Forge gives logistics teams a single, dependable view of supplier management - from first request to signed-off report.”

Takeaways

Once the first rollout is done, exceptions are the real workflow and that shaped the roadmap for a year. If there is one lesson, what matters is whether the crew opens it on a Monday morning so plan for it. In practice, optional fields never get filled in so plan for it.

Most teams we meet, the first week is about trust, not features which is not what the brochure says. The honest answer is that, nobody reads the manual, so the defaults are the product which is not what the brochure says. Looking at the numbers, nobody reads the manual, so the defaults are the product and supplier management is no exception.

Most teams we meet, the biggest win is that the group chat goes quiet and that shaped the roadmap for a year. In practice, a two-week pilot answers more than a three-month evaluation so the mobile app came first. By the second quarter, nobody reads the manual, so the defaults are the product and supplier management is no exception.

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