2026-06-25 · 9 min read

A boring reporting layer is a good reporting layer

Talking to operations leads, the spreadsheet survives longer than anyone admits which is why Kestrelify is built the way it is. Once the first rollout is done, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI. Most teams we meet, a two-week pilot answers more than a three-month evaluation and the numbers bear it out.

Looking at the numbers, nobody reads the manual, so the defaults are the product and that is fine. Once the first rollout is done, the audit trail pays for itself the first time an inspector asks which is the whole point. By the second quarter, field service scheduling is a people problem wearing a software costume so we start there.

Most teams we meet, the handover from the old system is where projects stall so we start there. What surprised us, the hard part is not the software but the handover and that shaped the roadmap for a year. If there is one lesson, mobile access changes who actually enters the data and the numbers bear it out. Talking to operations leads, mobile access changes who actually enters the data which is not what the brochure says. When the pilot started in Tallinn, mobile access changes who actually enters the data so plan for it.

What actually happened

On the floor, the hard part is not the software but the handover which is the whole point. When the pilot started in Tallinn, the first week is about trust, not features and that is fine. By the second quarter, the audit trail pays for itself the first time an inspector asks and the numbers bear it out.

By the second quarter, integrations are where budgets go to die which is why the API is documented before the UI. On the floor, mobile access changes who actually enters the data which is not what the brochure says. If there is one lesson, a two-week pilot answers more than a three-month evaluation so the defaults matter more than the settings page. If there is one lesson, history matters more than dashboards when something goes wrong and it rarely takes more than a week. Most teams we meet, the handover from the old system is where projects stall and it shows up in the churn numbers.

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

What to do on Monday

If there is one lesson, the schedule is only as good as the last update and it shows up in the churn numbers. If there is one lesson, the schedule is only as good as the last update and field service scheduling is no exception. By the second quarter, the hard part is not the software but the handover which is why the API is documented before the UI. What surprised us, the handover from the old system is where projects stall which is not what the brochure says.

For retail chains in particular, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. After a few dozen rollouts, the handover from the old system is where projects stall so the defaults matter more than the settings page. If there is one lesson, the schedule is only as good as the last update which is why Kestrelify is built the way it is. In practice, nobody wants another login and the numbers bear it out. On the floor, field service scheduling is a people problem wearing a software costume and it rarely takes more than a week.

Written by the Kestrelify team in Tallinn. Questions? Get in touch.