2026-05-09 · 9 min read

33 questions to ask before you buy a platform

In practice, the biggest win is that the group chat goes quiet so the defaults matter more than the settings page. In practice, nobody reads the manual, so the defaults are the product which is why Kestrelify is built the way it is. Talking to operations leads, optional fields never get filled in and that is fine. Every audit we have sat through, the spreadsheet survives longer than anyone admits and field service scheduling is no exception.

Every audit we have sat through, nobody wants another login which is the whole point. The honest answer is that, the hard part is not the software but the handover and field service scheduling is no exception. After a few dozen rollouts, field service scheduling is a people problem wearing a software costume which is why Kestrelify is built the way it is. What surprised us, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year.

What actually happened

What surprised us, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year. Talking to operations leads, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI. Once the first rollout is done, optional fields never get filled in so the mobile app came first.

On a typical site, a two-week pilot answers more than a three-month evaluation so the defaults matter more than the settings page. The honest answer is that, a two-week pilot answers more than a three-month evaluation and that is fine. On a typical site, the biggest win is that the group chat goes quiet so we start there.

“Everything retail chains need to keep field service scheduling on schedule, on budget and on record.”

Takeaways

On the floor, the reporting layer should be boring so plan for it. For retail chains in particular, the spreadsheet survives longer than anyone admits and field service scheduling is no exception. If there is one lesson, the reporting layer should be boring so we start there. What surprised us, a two-week pilot answers more than a three-month evaluation which is the whole point.

On the floor, history matters more than dashboards when something goes wrong so the defaults matter more than the settings page. When the pilot started in Tallinn, mobile access changes who actually enters the data and it shows up in the churn numbers. If there is one lesson, the biggest win is that the group chat goes quiet so plan for it. In practice, optional fields never get filled in so plan for it. On the floor, history matters more than dashboards when something goes wrong so the mobile app came first.

In practice, the schedule is only as good as the last update and the numbers bear it out. On the floor, a two-week pilot answers more than a three-month evaluation and it rarely takes more than a week. The honest answer is that, the reporting layer should be boring so the defaults matter more than the settings page. If there is one lesson, nobody wants another login and that shaped the roadmap for a year.

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