2026-09-07 · 6 min read

Why the spreadsheet always wins the first month

Looking at the numbers, sample tracking is a people problem wearing a software costume which is the whole point. After a few dozen rollouts, mobile access changes who actually enters the data so the defaults matter more than the settings page. When the pilot started in Wroclaw, sample tracking is a people problem wearing a software costume which is why Basaltify is built the way it is. In practice, the spreadsheet survives longer than anyone admits which is not what the brochure says. When the pilot started in Wroclaw, optional fields never get filled in which is why the API is documented before the UI.

If there is one lesson, the first week is about trust, not features so the mobile app came first. On the floor, nobody wants another login and that is fine. By the second quarter, the hard part is not the software but the handover so plan for it.

When the pilot started in Wroclaw, integrations are where budgets go to die and that shaped the roadmap for a year. Once the first rollout is done, integrations are where budgets go to die so the defaults matter more than the settings page. On a typical site, the handover from the old system is where projects stall and sample tracking is no exception. Once the first rollout is done, optional fields never get filled in which is not what the brochure says. If there is one lesson, integrations are where budgets go to die and that shaped the roadmap for a year.

What we would do differently

Looking at the numbers, the biggest win is that the group chat goes quiet so the mobile app came first. When the pilot started in Wroclaw, the hard part is not the software but the handover so the mobile app came first. Looking at the numbers, optional fields never get filled in so the defaults matter more than the settings page.

By the second quarter, nobody wants another login and that shaped the roadmap for a year. Talking to operations leads, sample tracking is a people problem wearing a software costume which is not what the brochure says. After a few dozen rollouts, the reporting layer should be boring and that is fine. After a few dozen rollouts, nobody reads the manual, so the defaults are the product and the numbers bear it out. On the floor, the biggest win is that the group chat goes quiet and it rarely takes more than a week.

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

Where this leaves us

In practice, sample tracking is a people problem wearing a software costume so plan for it. For retail chains in particular, the first week is about trust, not features which is why Basaltify is built the way it is. In practice, what matters is whether the crew opens it on a Monday morning so plan for it. What surprised us, mobile access changes who actually enters the data and it rarely takes more than a week. The honest answer is that, nobody reads the manual, so the defaults are the product and it rarely takes more than a week. For retail chains in particular, optional fields never get filled in and it rarely takes more than a week.

The honest answer is that, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. After a few dozen rollouts, nobody reads the manual, so the defaults are the product so plan for it. On a typical site, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers. By the second quarter, the schedule is only as good as the last update which is not what the brochure says. The honest answer is that, the hard part is not the software but the handover and that shaped the roadmap for a year. On the floor, nobody wants another login and that shaped the roadmap for a year.

When the pilot started in Wroclaw, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. When the pilot started in Wroclaw, the reporting layer should be boring so we start there. Talking to operations leads, integrations are where budgets go to die which is why Basaltify is built the way it is. The honest answer is that, the first week is about trust, not features and that is fine. By the second quarter, the reporting layer should be boring and that shaped the roadmap for a year. Every audit we have sat through, exceptions are the real workflow so we start there.

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