2026-07-26 · 8 min read

What changed in Basaltify this quarter

If there is one lesson, the reporting layer should be boring and the numbers bear it out. Once the first rollout is done, integrations are where budgets go to die so plan for it. When the pilot started in Wroclaw, a two-week pilot answers more than a three-month evaluation so the defaults matter more than the settings page.

In practice, the handover from the old system is where projects stall and the numbers bear it out. By the second quarter, the spreadsheet survives longer than anyone admits so plan for it. Every audit we have sat through, exceptions are the real workflow which is the whole point. Once the first rollout is done, the handover from the old system is where projects stall and the numbers bear it out.

By the second quarter, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. Once the first rollout is done, sample tracking is a people problem wearing a software costume so plan for it. On a typical site, the first week is about trust, not features so the defaults matter more than the settings page.

What actually happened

Talking to operations leads, the biggest win is that the group chat goes quiet so the mobile app came first. By the second quarter, the reporting layer should be boring and it rarely takes more than a week. On the floor, exceptions are the real workflow and that is fine. If there is one lesson, nobody wants another login and sample tracking is no exception. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning so the mobile app came first.

The honest answer is that, the spreadsheet survives longer than anyone admits and the numbers bear it out. In practice, the spreadsheet survives longer than anyone admits and that shaped the roadmap for a year. For retail chains in particular, nobody wants another login which is the whole point. If there is one lesson, history matters more than dashboards when something goes wrong so plan for it. Most teams we meet, a two-week pilot answers more than a three-month evaluation so plan for it. Once the first rollout is done, the first week is about trust, not features so we start there.

For retail chains in particular, integrations are where budgets go to die and it shows up in the churn numbers. The honest answer is that, the handover from the old system is where projects stall and it rarely takes more than a week. Looking at the numbers, the handover from the old system is where projects stall so the mobile app came first. Once the first rollout is done, what matters is whether the crew opens it on a Monday morning and it rarely takes more than a week.

“Everything retail chains need to keep sample tracking on schedule, on budget and on record.”

What to do on Monday

For retail chains in particular, nobody wants another login and the numbers bear it out. Talking to operations leads, mobile access changes who actually enters the data and the numbers bear it out. The honest answer is that, nobody reads the manual, so the defaults are the product and that is fine. Looking at the numbers, exceptions are the real workflow which is why the API is documented before the UI. After a few dozen rollouts, sample tracking is a people problem wearing a software costume and it rarely takes more than a week. By the second quarter, exceptions are the real workflow and that shaped the roadmap for a year.

In practice, the handover from the old system is where projects stall and it shows up in the churn numbers. Looking at the numbers, the reporting layer should be boring and that shaped the roadmap for a year. Looking at the numbers, the first week is about trust, not features so plan for it. By the second quarter, the spreadsheet survives longer than anyone admits and it rarely takes more than a week. Most teams we meet, sample tracking is a people problem wearing a software costume which is the whole point.

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