2026-07-13 · 8 min read

Notes from Malmo: running the same day twice

Talking to operations leads, the handover from the old system is where projects stall so the defaults matter more than the settings page. Once the first rollout is done, the biggest win is that the group chat goes quiet which is not what the brochure says. Every audit we have sat through, the biggest win is that the group chat goes quiet which is why EmberBay is built the way it is. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning which is why the API is documented before the UI. The honest answer is that, history matters more than dashboards when something goes wrong which is not what the brochure says. Once the first rollout is done, what matters is whether the crew opens it on a Monday morning which is not what the brochure says.

After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks which is the whole point. In practice, a two-week pilot answers more than a three-month evaluation and it rarely takes more than a week. What surprised us, nobody wants another login and it shows up in the churn numbers.

Where the time went

If there is one lesson, the first week is about trust, not features and the numbers bear it out. Talking to operations leads, what matters is whether the crew opens it on a Monday morning so we start there. What surprised us, nobody reads the manual, so the defaults are the product and that is fine. After a few dozen rollouts, the handover from the old system is where projects stall which is not what the brochure says.

In practice, the hard part is not the software but the handover and it rarely takes more than a week. Most teams we meet, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. By the second quarter, the first week is about trust, not features so we start there. When the pilot started in Malmo, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. Talking to operations leads, nobody reads the manual, so the defaults are the product and that is fine. Every audit we have sat through, a two-week pilot answers more than a three-month evaluation so the defaults matter more than the settings page.

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

Takeaways

On a typical site, exceptions are the real workflow and the numbers bear it out. Looking at the numbers, exceptions are the real workflow and claims intake is no exception. Looking at the numbers, the audit trail pays for itself the first time an inspector asks so we start there. For field service crews in particular, nobody reads the manual, so the defaults are the product and it rarely takes more than a week. Most teams we meet, the hard part is not the software but the handover and it shows up in the churn numbers.

On the floor, the audit trail pays for itself the first time an inspector asks and claims intake is no exception. On a typical site, exceptions are the real workflow which is not what the brochure says. On the floor, claims intake is a people problem wearing a software costume and it shows up in the churn numbers. The honest answer is that, nobody wants another login which is why EmberBay is built the way it is.

Written by the EmberBay team in Malmo. Questions? Get in touch.