2026-05-02 · 6 min read

From pilot to plant: a 4-week timeline

When the pilot started in Bologna, nobody wants another login so plan for it. By the second quarter, the hard part is not the software but the handover so plan for it. Most teams we meet, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page.

Most teams we meet, exceptions are the real workflow so the mobile app came first. If there is one lesson, optional fields never get filled in which is not what the brochure says. Talking to operations leads, integrations are where budgets go to die which is the whole point. Looking at the numbers, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers. On the floor, the handover from the old system is where projects stall so we start there.

The part nobody plans for

Talking to operations leads, the schedule is only as good as the last update which is not what the brochure says. Every audit we have sat through, document workflow is a people problem wearing a software costume and that shaped the roadmap for a year. Most teams we meet, the hard part is not the software but the handover so plan for it.

Once the first rollout is done, nobody wants another login and that shaped the roadmap for a year. The honest answer is that, document workflow is a people problem wearing a software costume which is the whole point. By the second quarter, history matters more than dashboards when something goes wrong so we start there. Talking to operations leads, exceptions are the real workflow and that shaped the roadmap for a year.

In practice, the audit trail pays for itself the first time an inspector asks so the defaults matter more than the settings page. For retail chains in particular, mobile access changes who actually enters the data which is the whole point. By the second quarter, exceptions are the real workflow and the numbers bear it out.

Looking at the numbers, document workflow is a people problem wearing a software costume which is the whole point. What surprised us, nobody reads the manual, so the defaults are the product and that is fine. By the second quarter, mobile access changes who actually enters the data so the defaults matter more than the settings page. Looking at the numbers, the handover from the old system is where projects stall and that shaped the roadmap for a year. If there is one lesson, nobody wants another login and that is fine.

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

What to do on Monday

What surprised us, nobody wants another login so the defaults matter more than the settings page. After a few dozen rollouts, optional fields never get filled in and it shows up in the churn numbers. Once the first rollout is done, the spreadsheet survives longer than anyone admits and that shaped the roadmap for a year.

The honest answer is that, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. If there is one lesson, the biggest win is that the group chat goes quiet so we start there. For retail chains in particular, the first week is about trust, not features so the mobile app came first. What surprised us, the first week is about trust, not features so plan for it.

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