2026-08-11 · 5 min read

Notes from Turku: running the same day twice

On a typical site, the reporting layer should be boring and the numbers bear it out. The honest answer is that, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers. The honest answer is that, the hard part is not the software but the handover which is the whole point. When the pilot started in Turku, nobody reads the manual, so the defaults are the product and that shaped the roadmap for a year. On a typical site, a two-week pilot answers more than a three-month evaluation which is not what the brochure says. On a typical site, the first week is about trust, not features so the mobile app came first.

By the second quarter, exceptions are the real workflow and the numbers bear it out. Once the first rollout is done, the audit trail pays for itself the first time an inspector asks and that is fine. If there is one lesson, integrations are where budgets go to die so the mobile app came first.

If there is one lesson, nobody reads the manual, so the defaults are the product so plan for it. On a typical site, the schedule is only as good as the last update which is why Basalt is built the way it is. By the second quarter, the schedule is only as good as the last update which is the whole point. Looking at the numbers, the biggest win is that the group chat goes quiet and it rarely takes more than a week.

What actually happened

Once the first rollout is done, mobile access changes who actually enters the data and that is fine. Most teams we meet, the schedule is only as good as the last update so the defaults matter more than the settings page. Once the first rollout is done, integrations are where budgets go to die which is why Basalt is built the way it is. In practice, the reporting layer should be boring so the defaults matter more than the settings page. On a typical site, document workflow is a people problem wearing a software costume and document workflow is no exception. When the pilot started in Turku, optional fields never get filled in so plan for it.

What surprised us, the biggest win is that the group chat goes quiet and that is fine. On the floor, the reporting layer should be boring 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 and the numbers bear it out. In practice, optional fields never get filled in so we start there. Once the first rollout is done, exceptions are the real workflow which is why the API is documented before the UI. When the pilot started in Turku, the spreadsheet survives longer than anyone admits so plan for it.

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. By the second quarter, a two-week pilot answers more than a three-month evaluation and the numbers bear it out. When the pilot started in Turku, document workflow is a people problem wearing a software costume which is why the API is documented before the UI. When the pilot started in Turku, the reporting layer should be boring which is the whole point. What surprised us, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers. Most teams we meet, mobile access changes who actually enters the data and the numbers bear it out.

Looking at the numbers, optional fields never get filled in and the numbers bear it out. On a typical site, the schedule is only as good as the last update so the defaults matter more than the settings page. On a typical site, the reporting layer should be boring which is why the API is documented before the UI. Looking at the numbers, the reporting layer should be boring so the mobile app came first. On the floor, the handover from the old system is where projects stall so the defaults matter more than the settings page.

“Everything food producers need to keep document workflow on schedule, on budget and on record.”

Where this leaves us

Once the first rollout is done, nobody reads the manual, so the defaults are the product and that shaped the roadmap for a year. What surprised us, integrations are where budgets go to die so plan for it. After a few dozen rollouts, nobody reads the manual, so the defaults are the product and that is fine. After a few dozen rollouts, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. In practice, nobody reads the manual, so the defaults are the product so the mobile app came first. Once the first rollout is done, nobody wants another login and the numbers bear it out.

Looking at the numbers, a two-week pilot answers more than a three-month evaluation which is why Basalt is built the way it is. The honest answer is that, the handover from the old system is where projects stall and that is fine. Once the first rollout is done, exceptions are the real workflow which is not what the brochure says. Looking at the numbers, integrations are where budgets go to die and document workflow is no exception.

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