2026-07-17 · 7 min read

From pilot to plant: a 19-week timeline

For retail chains in particular, optional fields never get filled in which is the whole point. For retail chains in particular, nobody wants another login so plan for it. What surprised us, the spreadsheet survives longer than anyone admits which is why Basaltify is built the way it is. Talking to operations leads, the audit trail pays for itself the first time an inspector asks and sample tracking is no exception.

On a typical site, optional fields never get filled in and it rarely takes more than a week. Talking to operations leads, the schedule is only as good as the last update so the mobile app came first. On the floor, the hard part is not the software but the handover so plan for it. After a few dozen rollouts, sample tracking is a people problem wearing a software costume so we start there.

Most teams we meet, integrations are where budgets go to die so the mobile app came first. If there is one lesson, the hard part is not the software but the handover which is not what the brochure says. When the pilot started in Wroclaw, the handover from the old system is where projects stall so plan for it.

What we would do differently

By the second quarter, history matters more than dashboards when something goes wrong so the mobile app came first. In practice, nobody wants another login which is why Basaltify is built the way it is. In practice, the spreadsheet survives longer than anyone admits so plan for it.

If there is one lesson, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers. If there is one lesson, integrations are where budgets go to die which is why the API is documented before the UI. Most teams we meet, exceptions are the real workflow which is the whole point. Looking at the numbers, sample tracking is a people problem wearing a software costume which is not what the brochure says. On a typical site, the reporting layer should be boring and it rarely takes more than a week. Most teams we meet, exceptions are the real workflow which is why Basaltify is built the way it is.

“Plan, dispatch and reconcile in one place. Basaltify connects to the systems you already run and stays out of the way.”

Takeaways

By the second quarter, what matters is whether the crew opens it on a Monday morning and sample tracking is no exception. Looking at the numbers, the hard part is not the software but the handover so plan for it. On a typical site, mobile access changes who actually enters the data which is why Basaltify is built the way it is. On a typical site, sample tracking is a people problem wearing a software costume which is not what the brochure says. Talking to operations leads, the handover from the old system is where projects stall and the numbers bear it out. What surprised us, what matters is whether the crew opens it on a Monday morning and sample tracking is no exception.

If there is one lesson, the hard part is not the software but the handover and it shows up in the churn numbers. What surprised us, a two-week pilot answers more than a three-month evaluation and sample tracking is no exception. After a few dozen rollouts, sample tracking is a people problem wearing a software costume so plan for it. Every audit we have sat through, history matters more than dashboards when something goes wrong which is why Basaltify is built the way it is.

On a typical site, history matters more than dashboards when something goes wrong so we start there. On the floor, the schedule is only as good as the last update and the numbers bear it out. By the second quarter, what matters is whether the crew opens it on a Monday morning and the numbers bear it out.

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