2026-07-22 · 7 min read

How field service crews actually use mobile

Every audit we have sat through, the hard part is not the software but the handover which is not what the brochure says. Looking at the numbers, nobody wants another login and it shows up in the churn numbers. Looking at the numbers, the biggest win is that the group chat goes quiet so the mobile app came first. In practice, mobile access changes who actually enters the data and it rarely takes more than a week. For field service crews in particular, mobile access changes who actually enters the data which is not what the brochure says. In practice, exceptions are the real workflow so plan for it.

On the floor, nobody reads the manual, so the defaults are the product and that shaped the roadmap for a year. What surprised us, nobody wants another login so the defaults matter more than the settings page. What surprised us, integrations are where budgets go to die so we start there. In practice, optional fields never get filled in which is not what the brochure says.

Looking at the numbers, what matters is whether the crew opens it on a Monday morning so we start there. When the pilot started in Malmo, a two-week pilot answers more than a three-month evaluation and sample tracking is no exception. Most teams we meet, mobile access changes who actually enters the data and it rarely takes more than a week. Looking at the numbers, nobody reads the manual, so the defaults are the product and that shaped the roadmap for a year. When the pilot started in Malmo, nobody wants another login so the mobile app came first.

Where the time went

Most teams we meet, the hard part is not the software but the handover which is not what the brochure says. For field service crews in particular, nobody wants another login and it rarely takes more than a week. The honest answer is that, sample tracking is a people problem wearing a software costume which is why Nimbus Stack is built the way it is.

The honest answer is that, nobody reads the manual, so the defaults are the product and the numbers bear it out. Most teams we meet, nobody wants another login which is the whole point. On the floor, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. Looking at the numbers, exceptions are the real workflow and the numbers bear it out. By the second quarter, exceptions are the real workflow and that is fine.

On the floor, nobody wants another login so the defaults matter more than the settings page. Once the first rollout is done, the schedule is only as good as the last update which is why Nimbus Stack is built the way it is. Talking to operations leads, exceptions are the real workflow so the mobile app came first. By the second quarter, exceptions are the real workflow so plan for it.

“Replace the spreadsheet, the whiteboard and the group chat with one suite your team will actually open.”

Takeaways

In practice, integrations are where budgets go to die which is not what the brochure says. By the second quarter, the first week is about trust, not features which is why the API is documented before the UI. When the pilot started in Malmo, the reporting layer should be boring and that is fine. Most teams we meet, optional fields never get filled in and the numbers bear it out.

The honest answer is that, the handover from the old system is where projects stall which is the whole point. Talking to operations leads, the reporting layer should be boring so we start there. On the floor, nobody reads the manual, so the defaults are the product and sample tracking is no exception. On the floor, the hard part is not the software but the handover so plan for it.

Written by the Nimbus Stack team in Malmo. Questions? Get in touch.