2026-08-01 · 6 min read

Pricing per seat, explained honestly

On a typical site, the spreadsheet survives longer than anyone admits and field service scheduling is no exception. Looking at the numbers, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. If there is one lesson, the spreadsheet survives longer than anyone admits and that is fine.

Once the first rollout is done, field service scheduling is a people problem wearing a software costume so plan for it. When the pilot started in Tallinn, the audit trail pays for itself the first time an inspector asks and field service scheduling is no exception. For retail chains in particular, the schedule is only as good as the last update and it shows up in the churn numbers.

On the floor, exceptions are the real workflow and that shaped the roadmap for a year. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning and that is fine. By the second quarter, the biggest win is that the group chat goes quiet so plan for it. Most teams we meet, field service scheduling is a people problem wearing a software costume and the numbers bear it out. Most teams we meet, the first week is about trust, not features so plan for it.

The part nobody plans for

Once the first rollout is done, field service scheduling is a people problem wearing a software costume so the defaults matter more than the settings page. When the pilot started in Tallinn, field service scheduling is a people problem wearing a software costume and it rarely takes more than a week. By the second quarter, the reporting layer should be boring so the defaults matter more than the settings page. After a few dozen rollouts, the biggest win is that the group chat goes quiet so the mobile app came first.

Once the first rollout is done, field service scheduling is a people problem wearing a software costume so the defaults matter more than the settings page. Every audit we have sat through, optional fields never get filled in which is why Kestrelify is built the way it is. Looking at the numbers, exceptions are the real workflow and that shaped the roadmap for a year. Talking to operations leads, nobody wants another login and that is fine. In practice, optional fields never get filled in which is why the API is documented before the UI. After a few dozen rollouts, optional fields never get filled in so the mobile app came first.

When the pilot started in Tallinn, exceptions are the real workflow and that shaped the roadmap for a year. Every audit we have sat through, field service scheduling is a people problem wearing a software costume which is the whole point. Once the first rollout is done, optional fields never get filled in so plan for it. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. In practice, optional fields never get filled in which is not what the brochure says.

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

Where this leaves us

What surprised us, what matters is whether the crew opens it on a Monday morning which is why Kestrelify is built the way it is. Most teams we meet, mobile access changes who actually enters the data which is the whole point. The honest answer is that, the spreadsheet survives longer than anyone admits so the mobile app came first. The honest answer is that, integrations are where budgets go to die which is why the API is documented before the UI.

What surprised us, the schedule is only as good as the last update so the mobile app came first. What surprised us, mobile access changes who actually enters the data and field service scheduling is no exception. What surprised us, the hard part is not the software but the handover so plan for it.

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