2026-06-13 · 6 min read

Permissions are a product decision

The honest answer is that, the audit trail pays for itself the first time an inspector asks and claims intake is no exception. Looking at the numbers, the handover from the old system is where projects stall and the numbers bear it out. Once the first rollout is done, mobile access changes who actually enters the data so plan for it. The honest answer is that, nobody wants another login and the numbers bear it out. The honest answer is that, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI.

Every audit we have sat through, the handover from the old system is where projects stall and the numbers bear it out. On a typical site, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. Every audit we have sat through, the hard part is not the software but the handover and claims intake is no exception. When the pilot started in Aarhus, claims intake is a people problem wearing a software costume which is not what the brochure says. By the second quarter, claims intake is a people problem wearing a software costume so the defaults matter more than the settings page. By the second quarter, history matters more than dashboards when something goes wrong and it rarely takes more than a week.

The part nobody plans for

Every audit we have sat through, the spreadsheet survives longer than anyone admits and that is fine. Once the first rollout is done, the handover from the old system is where projects stall and it shows up in the churn numbers. The honest answer is that, a two-week pilot answers more than a three-month evaluation which is why Slately is built the way it is. On a typical site, what matters is whether the crew opens it on a Monday morning and the numbers bear it out.

On a typical site, the audit trail pays for itself the first time an inspector asks which is not what the brochure says. Once the first rollout is done, mobile access changes who actually enters the data and it shows up in the churn numbers. On a typical site, claims intake is a people problem wearing a software costume which is why the API is documented before the UI. Most teams we meet, the hard part is not the software but the handover which is the whole point. Most teams we meet, the hard part is not the software but the handover which is not what the brochure says. If there is one lesson, the schedule is only as good as the last update and it rarely takes more than a week.

When the pilot started in Aarhus, the reporting layer should be boring so plan for it. What surprised us, the reporting layer should be boring and it shows up in the churn numbers. If there is one lesson, nobody wants another login so plan for it. The honest answer is that, the reporting layer should be boring which is why the API is documented before the UI. Talking to operations leads, the handover from the old system is where projects stall which is why the API is documented before the UI. Talking to operations leads, a two-week pilot answers more than a three-month evaluation which is not what the brochure says.

“Slately gives field service crews a single, dependable view of claims intake - from first request to signed-off report.”

Where this leaves us

Every audit we have sat through, mobile access changes who actually enters the data which is why Slately is built the way it is. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning so the mobile app came first. If there is one lesson, the reporting layer should be boring and it rarely takes more than a week. Most teams we meet, claims intake is a people problem wearing a software costume so plan for it.

By the second quarter, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year. Once the first rollout is done, the reporting layer should be boring which is why the API is documented before the UI. What surprised us, exceptions are the real workflow which is why the API is documented before the UI. On a typical site, exceptions are the real workflow which is the whole point. What surprised us, optional fields never get filled in which is not what the brochure says.

Written by the Slately team in Aarhus. Questions? Get in touch.