2026-08-18 · 4 min read

Notes from Turku: running the same day twice

In practice, history matters more than dashboards when something goes wrong which is the whole point. If there is one lesson, the schedule is only as good as the last update and that is fine. The honest answer is that, the handover from the old system is where projects stall so we start there.

Talking to operations leads, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI. What surprised us, the audit trail pays for itself the first time an inspector asks so plan for it. When the pilot started in Turku, nobody reads the manual, so the defaults are the product which is why Vantage is built the way it is.

What actually happened

When the pilot started in Turku, exceptions are the real workflow and it shows up in the churn numbers. On the floor, nobody reads the manual, so the defaults are the product so plan for it. Once the first rollout is done, customer onboarding is a people problem wearing a software costume so the defaults matter more than the settings page. For logistics teams in particular, the biggest win is that the group chat goes quiet which is not what the brochure says. By the second quarter, integrations are where budgets go to die which is why Vantage is built the way it is.

For logistics teams in particular, the first week is about trust, not features so the mobile app came first. Talking to operations leads, nobody reads the manual, so the defaults are the product which is why Vantage is built the way it is. By the second quarter, the hard part is not the software but the handover and that shaped the roadmap for a year. In practice, nobody wants another login which is why Vantage is built the way it is. After a few dozen rollouts, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year. When the pilot started in Turku, customer onboarding is a people problem wearing a software costume and it rarely takes more than a week.

Most teams we meet, exceptions are the real workflow and that is fine. On a typical site, integrations are where budgets go to die which is why Vantage is built the way it is. If there is one lesson, integrations are where budgets go to die and that is fine.

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

Takeaways

If there is one lesson, the handover from the old system is where projects stall and that shaped the roadmap for a year. Talking to operations leads, the spreadsheet survives longer than anyone admits so plan for it. On the floor, nobody reads the manual, so the defaults are the product so plan for it. On the floor, the schedule is only as good as the last update so we start there. When the pilot started in Turku, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year.

Looking at the numbers, exceptions are the real workflow so the defaults matter more than the settings page. Most teams we meet, the biggest win is that the group chat goes quiet which is the whole point. Most teams we meet, a two-week pilot answers more than a three-month evaluation and that is fine.

Looking at the numbers, the hard part is not the software but the handover which is not what the brochure says. After a few dozen rollouts, optional fields never get filled in so the defaults matter more than the settings page. Talking to operations leads, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year. Looking at the numbers, the handover from the old system is where projects stall and that shaped the roadmap for a year. Looking at the numbers, mobile access changes who actually enters the data so plan for it. Once the first rollout is done, what matters is whether the crew opens it on a Monday morning and customer onboarding is no exception.

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