2026-07-15 · 4 min read

Notes from Tallinn: running the same day twice

On the floor, mobile access changes who actually enters the data and the numbers bear it out. Most teams we meet, nobody wants another login which is why SableSystems is built the way it is. Looking at the numbers, mobile access changes who actually enters the data which is why SableSystems is built the way it is. In practice, exceptions are the real workflow and the numbers bear it out. If there is one lesson, the spreadsheet survives longer than anyone admits which is not what the brochure says. On a typical site, the reporting layer should be boring which is not what the brochure says.

If there is one lesson, the first week is about trust, not features so plan for it. On a typical site, what matters is whether the crew opens it on a Monday morning and it rarely takes more than a week. 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.

Looking at the numbers, history matters more than dashboards when something goes wrong so the mobile app came first. Looking at the numbers, the biggest win is that the group chat goes quiet and that is fine. On the floor, the reporting layer should be boring which is not what the brochure says. On a typical site, a two-week pilot answers more than a three-month evaluation and that is fine.

What actually happened

Talking to operations leads, the schedule is only as good as the last update which is not what the brochure says. What surprised us, claims intake is a people problem wearing a software costume and claims intake is no exception. Every audit we have sat through, optional fields never get filled in and the numbers bear it out. Talking to operations leads, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. What surprised us, the reporting layer should be boring and claims intake is no exception. Most teams we meet, what matters is whether the crew opens it on a Monday morning which is the whole point.

When the pilot started in Tallinn, the first week is about trust, not features so plan for it. For field service crews in particular, the audit trail pays for itself the first time an inspector asks so the defaults matter more than the settings page. Most teams we meet, what matters is whether the crew opens it on a Monday morning which is why SableSystems is built the way it is.

“Plan, dispatch and reconcile in one place. SableSystems connects to the systems you already run and stays out of the way.”

Takeaways

Most teams we meet, history matters more than dashboards when something goes wrong which is not what the brochure says. What surprised us, the first week is about trust, not features so the defaults matter more than the settings page. By the second quarter, history matters more than dashboards when something goes wrong which is not what the brochure says. In practice, optional fields never get filled in so we start there. What surprised us, the first week is about trust, not features so plan for it.

In practice, a two-week pilot answers more than a three-month evaluation and it rarely takes more than a week. For field service crews in particular, nobody reads the manual, so the defaults are the product and the numbers bear it out. Once the first rollout is done, what matters is whether the crew opens it on a Monday morning so plan for it. Most teams we meet, the first week is about trust, not features and the numbers bear it out. After a few dozen rollouts, optional fields never get filled in so the mobile app came first. If there is one lesson, history matters more than dashboards when something goes wrong and that is fine.

On a typical site, integrations are where budgets go to die and that is fine. On a typical site, exceptions are the real workflow which is why the API is documented before the UI. What surprised us, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. If there is one lesson, mobile access changes who actually enters the data so we start there.

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