2026-05-11 · 8 min read

Why the spreadsheet always wins the first month

Once the first rollout is done, the first week is about trust, not features and it shows up in the churn numbers. If there is one lesson, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page. Once the first rollout is done, the hard part is not the software but the handover and revenue analytics is no exception. Once the first rollout is done, nobody reads the manual, so the defaults are the product so we start there. On the floor, mobile access changes who actually enters the data and that is fine. Once the first rollout is done, the biggest win is that the group chat goes quiet and that shaped the roadmap for a year.

After a few dozen rollouts, nobody reads the manual, so the defaults are the product and that shaped the roadmap for a year. Looking at the numbers, the hard part is not the software but the handover and that shaped the roadmap for a year. Every audit we have sat through, nobody wants another login and revenue analytics is no exception.

The part nobody plans for

What surprised us, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. By the second quarter, the handover from the old system is where projects stall which is why Kestrel is built the way it is. On the floor, a two-week pilot answers more than a three-month evaluation and the numbers bear it out.

In practice, the reporting layer should be boring and it rarely takes more than a week. Once the first rollout is done, nobody wants another login so the mobile app came first. On the floor, the spreadsheet survives longer than anyone admits and that is fine.

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

Where this leaves us

When the pilot started in Brno, the schedule is only as good as the last update so we start there. For retail chains in particular, history matters more than dashboards when something goes wrong and the numbers bear it out. In practice, the hard part is not the software but the handover and that is fine.

Once the first rollout is done, nobody reads the manual, so the defaults are the product and it rarely takes more than a week. Every audit we have sat through, the handover from the old system is where projects stall which is the whole point. For retail chains in particular, optional fields never get filled in which is why Kestrel is built the way it is. On a typical site, the hard part is not the software but the handover and it rarely takes more than a week.

For retail chains in particular, revenue analytics is a people problem wearing a software costume which is not what the brochure says. Talking to operations leads, mobile access changes who actually enters the data which is why the API is documented before the UI. In practice, the spreadsheet survives longer than anyone admits and the numbers bear it out. Most teams we meet, the hard part is not the software but the handover and it rarely takes more than a week.

Written by the Kestrel team in Brno. Questions? Get in touch.