2026-05-21 · 7 min read

From pilot to plant: a 35-week timeline

Looking at the numbers, mobile access changes who actually enters the data and it rarely takes more than a week. When the pilot started in Bologna, integrations are where budgets go to die and it shows up in the churn numbers. In practice, the schedule is only as good as the last update and that is fine.

Most teams we meet, the schedule is only as good as the last update and the numbers bear it out. After a few dozen rollouts, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. In practice, the first week is about trust, not features and the numbers bear it out. Talking to operations leads, mobile access changes who actually enters the data which is not what the brochure says. If there is one lesson, integrations are where budgets go to die and that is fine.

What we would do differently

By the second quarter, exceptions are the real workflow and the numbers bear it out. When the pilot started in Bologna, integrations are where budgets go to die and it shows up in the churn numbers. For retail chains in particular, the handover from the old system is where projects stall and the numbers bear it out.

Most teams we meet, mobile access changes who actually enters the data so the defaults matter more than the settings page. The honest answer is that, the reporting layer should be boring and that shaped the roadmap for a year. On the floor, what matters is whether the crew opens it on a Monday morning and that is fine. For retail chains in particular, mobile access changes who actually enters the data so we start there. By the second quarter, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers. Looking at the numbers, exceptions are the real workflow which is not what the brochure says.

“Everything retail chains need to keep claims intake on schedule, on budget and on record.”

What to do on Monday

Most teams we meet, what matters is whether the crew opens it on a Monday morning which is why Lumen Stack is built the way it is. The honest answer is that, the schedule is only as good as the last update and it rarely takes more than a week. The honest answer is that, optional fields never get filled in and that shaped the roadmap for a year. The honest answer is that, the biggest win is that the group chat goes quiet and claims intake is no exception. Looking at the numbers, the hard part is not the software but the handover which is why Lumen Stack is built the way it is.

Most teams we meet, the schedule is only as good as the last update so the mobile app came first. On a typical site, the audit trail pays for itself the first time an inspector asks so the defaults matter more than the settings page. On the floor, the hard part is not the software but the handover so plan for it.

Written by the Lumen Stack team in Bologna. Questions? Get in touch.