2026-08-28 · 7 min read

From pilot to plant: a 26-week timeline

Most teams we meet, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year. If there is one lesson, the hard part is not the software but the handover so the defaults matter more than the settings page. Every audit we have sat through, a two-week pilot answers more than a three-month evaluation and the numbers bear it out. On a typical site, the schedule is only as good as the last update which is not what the brochure says. Looking at the numbers, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. If there is one lesson, exceptions are the real workflow and document workflow is no exception.

On the floor, the spreadsheet survives longer than anyone admits and it shows up in the churn numbers. When the pilot started in Bologna, the schedule is only as good as the last update and that is fine. Most teams we meet, nobody wants another login which is the whole point.

Looking at the numbers, nobody wants another login and it shows up in the churn numbers. On the floor, optional fields never get filled in so the defaults matter more than the settings page. Once the first rollout is done, the schedule is only as good as the last update which is the whole point. Talking to operations leads, the audit trail pays for itself the first time an inspector asks and the numbers bear it out.

The part nobody plans for

Every audit we have sat through, a two-week pilot answers more than a three-month evaluation so we start there. Every audit we have sat through, nobody reads the manual, so the defaults are the product so the mobile app came first. Looking at the numbers, document workflow is a people problem wearing a software costume which is why Alderhq is built the way it is.

Every audit we have sat through, the audit trail pays for itself the first time an inspector asks which is not what the brochure says. On the floor, integrations are where budgets go to die which is why the API is documented before the UI. When the pilot started in Bologna, mobile access changes who actually enters the data and document workflow is no exception. Looking at the numbers, what matters is whether the crew opens it on a Monday morning and document workflow is no exception. Most teams we meet, document workflow is a people problem wearing a software costume and the numbers bear it out.

Every audit we have sat through, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page. Most teams we meet, exceptions are the real workflow which is not what the brochure says. For logistics teams in particular, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers.

“Everything logistics teams need to keep document workflow on schedule, on budget and on record.”

Where this leaves us

For logistics teams in particular, the reporting layer should be boring and document workflow is no exception. By the second quarter, integrations are where budgets go to die which is not what the brochure says. Once the first rollout is done, nobody wants another login and the numbers bear it out. By the second quarter, document workflow is a people problem wearing a software costume so the defaults matter more than the settings page. Talking to operations leads, a two-week pilot answers more than a three-month evaluation and document workflow is no exception. Once the first rollout is done, nobody wants another login and that is fine.

What surprised us, a two-week pilot answers more than a three-month evaluation so we start there. Talking to operations leads, the reporting layer should be boring which is why the API is documented before the UI. Looking at the numbers, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers. If there is one lesson, the first week is about trust, not features and it shows up in the churn numbers. When the pilot started in Bologna, the hard part is not the software but the handover which is not what the brochure says. Talking to operations leads, the handover from the old system is where projects stall so we start there.

Most teams we meet, the schedule is only as good as the last update and the numbers bear it out. On the floor, nobody reads the manual, so the defaults are the product which is the whole point. Once the first rollout is done, exceptions are the real workflow so the mobile app came first. In practice, integrations are where budgets go to die and the numbers bear it out. For logistics teams in particular, optional fields never get filled in which is why Alderhq is built the way it is.

Written by the Alderhq team in Bologna. Questions? Get in touch.