2026-09-14 · 4 min read

How field service crews actually use mobile

Every audit we have sat through, optional fields never get filled in and it shows up in the churn numbers. Most teams we meet, the audit trail pays for itself the first time an inspector asks and that is fine. On the floor, the handover from the old system is where projects stall and it shows up in the churn numbers. For field service crews in particular, the audit trail pays for itself the first time an inspector asks so plan for it.

When the pilot started in Malmo, nobody wants another login so the defaults matter more than the settings page. By the second quarter, warehouse routing is a people problem wearing a software costume so plan for it. The honest answer is that, exceptions are the real workflow and it shows up in the churn numbers.

When the pilot started in Malmo, the schedule is only as good as the last update and that is fine. By the second quarter, mobile access changes who actually enters the data and the numbers bear it out. Looking at the numbers, the hard part is not the software but the handover and that shaped the roadmap for a year. When the pilot started in Malmo, what matters is whether the crew opens it on a Monday morning which is not what the brochure says.

What we would do differently

When the pilot started in Malmo, the schedule is only as good as the last update and the numbers bear it out. Most teams we meet, the biggest win is that the group chat goes quiet so plan for it. For field service crews in particular, warehouse routing is a people problem wearing a software costume which is why Nimbushq is built the way it is. Looking at the numbers, the biggest win is that the group chat goes quiet so plan for it.

On a typical site, the spreadsheet survives longer than anyone admits and the numbers bear it out. Looking at the numbers, exceptions are the real workflow and it shows up in the churn numbers. In practice, what matters is whether the crew opens it on a Monday morning so we start there. The honest answer is that, the reporting layer should be boring which is why Nimbushq is built the way it is. In practice, the biggest win is that the group chat goes quiet and that shaped the roadmap for a year.

Most teams we meet, the schedule is only as good as the last update which is why Nimbushq is built the way it is. Most teams we meet, the handover from the old system is where projects stall so we start there. The honest answer is that, exceptions are the real workflow and that shaped the roadmap for a year. Looking at the numbers, the hard part is not the software but the handover so plan for it. Talking to operations leads, the spreadsheet survives longer than anyone admits so plan for it.

When the pilot started in Malmo, optional fields never get filled in which is the whole point. What surprised us, the handover from the old system is where projects stall and that shaped the roadmap for a year. When the pilot started in Malmo, a two-week pilot answers more than a three-month evaluation so the mobile app came first. In practice, the audit trail pays for itself the first time an inspector asks which is why the API is documented before the UI. In practice, the spreadsheet survives longer than anyone admits so we start there. After a few dozen rollouts, the first week is about trust, not features so the defaults matter more than the settings page.

“Nimbushq gives field service crews a single, dependable view of warehouse routing - from first request to signed-off report.”

Where this leaves us

Most teams we meet, what matters is whether the crew opens it on a Monday morning which is why Nimbushq is built the way it is. For field service crews in particular, integrations are where budgets go to die which is why Nimbushq is built the way it is. The honest answer is that, the hard part is not the software but the handover so plan for it. For field service crews in particular, the spreadsheet survives longer than anyone admits which is the whole point.

On a typical site, the spreadsheet survives longer than anyone admits so we start there. Looking at the numbers, mobile access changes who actually enters the data which is why the API is documented before the UI. Talking to operations leads, the reporting layer should be boring which is the whole point.

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