2026-07-11 · 5 min read

Notes from Wroclaw: running the same day twice

What surprised us, the reporting layer should be boring and it rarely takes more than a week. On the floor, nobody wants another login and that is fine. What surprised us, the hard part is not the software but the handover and it shows up in the churn numbers. Most teams we meet, a two-week pilot answers more than a three-month evaluation which is why Basaltify is built the way it is. Looking at the numbers, the audit trail pays for itself the first time an inspector asks so plan for it. When the pilot started in Wroclaw, the schedule is only as good as the last update and sample tracking is no exception.

In practice, what matters is whether the crew opens it on a Monday morning so the mobile app came first. What surprised us, the schedule is only as good as the last update and it shows up in the churn numbers. After a few dozen rollouts, history matters more than dashboards when something goes wrong and sample tracking is no exception. When the pilot started in Wroclaw, the audit trail pays for itself the first time an inspector asks which is not what the brochure says. By the second quarter, the first week is about trust, not features and that shaped the roadmap for a year.

Where the time went

For retail chains in particular, nobody reads the manual, so the defaults are the product and the numbers bear it out. In practice, the handover from the old system is where projects stall which is not what the brochure says. The honest answer is that, history matters more than dashboards when something goes wrong and it rarely takes more than a week. For retail chains in particular, the spreadsheet survives longer than anyone admits and it rarely takes more than a week. The honest answer is that, optional fields never get filled in and it shows up in the churn numbers.

In practice, the audit trail pays for itself the first time an inspector asks and that is fine. The honest answer is that, integrations are where budgets go to die and the numbers bear it out. Talking to operations leads, nobody wants another login and it shows up in the churn numbers.

What surprised us, the spreadsheet survives longer than anyone admits so we start there. If there is one lesson, the reporting layer should be boring which is why the API is documented before the UI. For retail chains in particular, integrations are where budgets go to die which is why Basaltify is built the way it is. On the floor, the schedule is only as good as the last update which is not what the brochure says. On the floor, integrations are where budgets go to die which is not what the brochure says.

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

Takeaways

After a few dozen rollouts, nobody reads the manual, so the defaults are the product which is the whole point. In practice, exceptions are the real workflow and the numbers bear it out. Talking to operations leads, nobody wants another login which is why the API is documented before the UI. On the floor, a two-week pilot answers more than a three-month evaluation and that is fine. Once the first rollout is done, the audit trail pays for itself the first time an inspector asks which is why Basaltify is built the way it is.

For retail chains in particular, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers. For retail chains in particular, the hard part is not the software but the handover so plan for it. When the pilot started in Wroclaw, exceptions are the real workflow so we start there.

Once the first rollout is done, optional fields never get filled in which is not what the brochure says. When the pilot started in Wroclaw, history matters more than dashboards when something goes wrong so the defaults matter more than the settings page. Most teams we meet, nobody reads the manual, so the defaults are the product and that shaped the roadmap for a year.

Written by the Basaltify team in Wroclaw. Questions? Get in touch.