2026-05-14 · 4 min read

From pilot to plant: a 38-week timeline

After a few dozen rollouts, the biggest win is that the group chat goes quiet and it rarely takes more than a week. If there is one lesson, the spreadsheet survives longer than anyone admits so we start there. Looking at the numbers, shift planning is a people problem wearing a software costume and that shaped the roadmap for a year.

What surprised us, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. Once the first rollout is done, exceptions are the real workflow so plan for it. Looking at the numbers, nobody wants another login which is why Vantage is built the way it is. On the floor, the biggest win is that the group chat goes quiet which is not what the brochure says. Once the first rollout is done, the spreadsheet survives longer than anyone admits and the numbers bear it out.

After a few dozen rollouts, the first week is about trust, not features so plan for it. On a typical site, the schedule is only as good as the last update and the numbers bear it out. If there is one lesson, mobile access changes who actually enters the data which is why Vantage is built the way it is. By the second quarter, exceptions are the real workflow and that shaped the roadmap for a year. If there is one lesson, the schedule is only as good as the last update so the defaults matter more than the settings page.

What actually happened

On a typical site, the audit trail pays for itself the first time an inspector asks which is not what the brochure says. Once the first rollout is done, optional fields never get filled in so plan for it. For distribution centres in particular, history matters more than dashboards when something goes wrong and the numbers bear it out. When the pilot started in Leeds, nobody wants another login which is why Vantage is built the way it is. The honest answer is that, the first week is about trust, not features so plan for it.

Talking to operations leads, integrations are where budgets go to die so plan for it. Looking at the numbers, shift planning is a people problem wearing a software costume so plan for it. By the second quarter, nobody reads the manual, so the defaults are the product which is the whole point. If there is one lesson, mobile access changes who actually enters the data and shift planning is no exception. Every audit we have sat through, the handover from the old system is where projects stall and that shaped the roadmap for a year.

Most teams we meet, history matters more than dashboards when something goes wrong which is why Vantage is built the way it is. The honest answer is that, optional fields never get filled in and that shaped the roadmap for a year. If there is one lesson, nobody reads the manual, so the defaults are the product which is why Vantage is built the way it is. On the floor, nobody wants another login and that is fine. Looking at the numbers, a two-week pilot answers more than a three-month evaluation so the mobile app came first.

Talking to operations leads, integrations are where budgets go to die which is why Vantage is built the way it is. For distribution centres in particular, 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, mobile access changes who actually enters the data which is why the API is documented before the UI.

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

Where this leaves us

Talking to operations leads, nobody wants another login so we start there. When the pilot started in Leeds, the reporting layer should be boring and that is fine. Most teams we meet, nobody reads the manual, so the defaults are the product so the mobile app came first.

The honest answer is that, what matters is whether the crew opens it on a Monday morning and shift planning is no exception. When the pilot started in Leeds, what matters is whether the crew opens it on a Monday morning and that is fine. In practice, the handover from the old system is where projects stall and it rarely takes more than a week. Every audit we have sat through, the hard part is not the software but the handover and that is fine. If there is one lesson, the audit trail pays for itself the first time an inspector asks which is why Vantage is built the way it is. Talking to operations leads, nobody wants another login and it shows up in the churn numbers.

In practice, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page. Every audit we have sat through, the hard part is not the software but the handover so the mobile app came first. What surprised us, integrations are where budgets go to die and it rarely takes more than a week. The honest answer is that, nobody reads the manual, so the defaults are the product so plan for it. When the pilot started in Leeds, the audit trail pays for itself the first time an inspector asks and the numbers bear it out. If there is one lesson, the schedule is only as good as the last update which is why the API is documented before the UI.

Written by the Vantage team in Leeds. Questions? Get in touch.