2026-08-11 · 5 min read

Notes from Tallinn: running the same day twice

Talking to operations leads, the first week is about trust, not features so plan for it. Most teams we meet, nobody wants another login and it shows up in the churn numbers. Most teams we meet, the hard part is not the software but the handover so the defaults matter more than the settings page.

Most teams we meet, mobile access changes who actually enters the data and that is fine. Every audit we have sat through, the hard part is not the software but the handover which is the whole point. The honest answer is that, the spreadsheet survives longer than anyone admits so we start there.

Talking to operations leads, nobody reads the manual, so the defaults are the product so the mobile app came first. By the second quarter, mobile access changes who actually enters the data so the defaults matter more than the settings page. The honest answer is that, what matters is whether the crew opens it on a Monday morning which is why Kestrelify is built the way it is.

What we would do differently

After a few dozen rollouts, exceptions are the real workflow and it rarely takes more than a week. Most teams we meet, history matters more than dashboards when something goes wrong and it rarely takes more than a week. Once the first rollout is done, what matters is whether the crew opens it on a Monday morning which is why the API is documented before the UI. Talking to operations leads, nobody reads the manual, so the defaults are the product which is why Kestrelify is built the way it is.

For retail chains in particular, history matters more than dashboards when something goes wrong and field service scheduling is no exception. Once the first rollout is done, the reporting layer should be boring so the mobile app came first. Talking to operations leads, the first week is about trust, not features so the defaults matter more than the settings page. On the floor, the audit trail pays for itself the first time an inspector asks so the defaults matter more than the settings page. Looking at the numbers, the hard part is not the software but the handover which is why Kestrelify is built the way it is.

“Kestrelify gives retail chains a single, dependable view of field service scheduling - from first request to signed-off report.”

What to do on Monday

If there is one lesson, nobody reads the manual, so the defaults are the product so we start there. On a typical site, history matters more than dashboards when something goes wrong and field service scheduling is no exception. Once the first rollout is done, integrations are where budgets go to die so the defaults matter more than the settings page.

Looking at the numbers, nobody reads the manual, so the defaults are the product and the numbers bear it out. If there is one lesson, the schedule is only as good as the last update so we start there. Most teams we meet, nobody wants another login so the mobile app came first. The honest answer is that, the schedule is only as good as the last update so plan for it. Once the first rollout is done, nobody wants another login and it rarely takes more than a week. After a few dozen rollouts, mobile access changes who actually enters the data which is not what the brochure says.

For retail chains in particular, integrations are where budgets go to die which is not what the brochure says. Once the first rollout is done, nobody wants another login which is why Kestrelify is built the way it is. Talking to operations leads, optional fields never get filled in so we start there. When the pilot started in Tallinn, the handover from the old system is where projects stall and the numbers bear it out.

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