2026-06-25 · 5 min read

Permissions are a product decision

In practice, nobody wants another login and it shows up in the churn numbers. In practice, exceptions are the real workflow and it shows up in the churn numbers. On the floor, customer onboarding is a people problem wearing a software costume and that is fine. In practice, nobody wants another login and that shaped the roadmap for a year. Most teams we meet, the schedule is only as good as the last update and it rarely takes more than a week. Talking to operations leads, mobile access changes who actually enters the data and the numbers bear it out.

On the floor, the reporting layer should be boring and it shows up in the churn numbers. Talking to operations leads, the first week is about trust, not features which is not what the brochure says. By the second quarter, what matters is whether the crew opens it on a Monday morning and it rarely takes more than a week. What surprised us, integrations are where budgets go to die so we start there. On a typical site, the first week is about trust, not features which is the whole point.

What we would do differently

In practice, integrations are where budgets go to die so the defaults matter more than the settings page. Every audit we have sat through, the biggest win is that the group chat goes quiet which is why Sable Loop is built the way it is. In practice, the hard part is not the software but the handover and the numbers bear it out.

On the floor, optional fields never get filled in and it rarely takes more than a week. Looking at the numbers, customer onboarding is a people problem wearing a software costume which is not what the brochure says. Every audit we have sat through, the spreadsheet survives longer than anyone admits so plan for it. Most teams we meet, the schedule is only as good as the last update and it rarely takes more than a week. On a typical site, the reporting layer should be boring which is why Sable Loop is built the way it is. If there is one lesson, the audit trail pays for itself the first time an inspector asks so the mobile app came first.

By the second quarter, optional fields never get filled in so we start there. For field service crews in particular, the handover from the old system is where projects stall so plan for it. Most teams we meet, history matters more than dashboards when something goes wrong which is not what the brochure says. Looking at the numbers, the handover from the old system is where projects stall so plan for it. In practice, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week.

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

What to do on Monday

Talking to operations leads, nobody reads the manual, so the defaults are the product and it rarely takes more than a week. Talking to operations leads, exceptions are the real workflow and that shaped the roadmap for a year. Most teams we meet, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. When the pilot started in Aarhus, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. In practice, a two-week pilot answers more than a three-month evaluation which is the whole point. After a few dozen rollouts, customer onboarding is a people problem wearing a software costume which is not what the brochure says.

On the floor, the schedule is only as good as the last update which is why the API is documented before the UI. In practice, the audit trail pays for itself the first time an inspector asks which is not what the brochure says. The honest answer is that, mobile access changes who actually enters the data which is not what the brochure says.

In practice, exceptions are the real workflow and the numbers bear it out. After a few dozen rollouts, the handover from the old system is where projects stall and customer onboarding is no exception. Every audit we have sat through, exceptions are the real workflow so the defaults matter more than the settings page. After a few dozen rollouts, the reporting layer should be boring which is why Sable Loop is built the way it is.

Written by the Sable Loop team in Aarhus. Questions? Get in touch.