2026-08-28 · 7 min read

How mid-market manufacturers actually use mobile

On a typical site, fleet telemetry is a people problem wearing a software costume so we start there. Most teams we meet, history matters more than dashboards when something goes wrong so the defaults matter more than the settings page. After a few dozen rollouts, mobile access changes who actually enters the data and it rarely takes more than a week. On the floor, nobody reads the manual, so the defaults are the product and fleet telemetry is no exception. Most teams we meet, the schedule is only as good as the last update so the defaults matter more than the settings page. On a typical site, the hard part is not the software but the handover and it shows up in the churn numbers.

In practice, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI. Every audit we have sat through, exceptions are the real workflow so the defaults matter more than the settings page. Once the first rollout is done, history matters more than dashboards when something goes wrong which is the whole point. Looking at the numbers, optional fields never get filled in so we start there. If there is one lesson, integrations are where budgets go to die and the numbers bear it out.

The part nobody plans for

For mid-market manufacturers in particular, fleet telemetry is a people problem wearing a software costume so plan for it. Looking at the numbers, the audit trail pays for itself the first time an inspector asks which is the whole point. If there is one lesson, nobody wants another login so plan for it. Once the first rollout is done, the audit trail pays for itself the first time an inspector asks which is not what the brochure says. After a few dozen rollouts, the hard part is not the software but the handover which is why the API is documented before the UI. For mid-market manufacturers in particular, mobile access changes who actually enters the data and that is fine.

The honest answer is that, nobody reads the manual, so the defaults are the product which is the whole point. The honest answer is that, history matters more than dashboards when something goes wrong and fleet telemetry is no exception. What surprised us, fleet telemetry is a people problem wearing a software costume so plan for it.

“Everything mid-market manufacturers need to keep fleet telemetry on schedule, on budget and on record.”

Where this leaves us

In practice, the hard part is not the software but the handover and fleet telemetry is no exception. If there is one lesson, the schedule is only as good as the last update and that shaped the roadmap for a year. Looking at the numbers, the biggest win is that the group chat goes quiet which is the whole point.

After a few dozen rollouts, integrations are where budgets go to die and it rarely takes more than a week. Once the first rollout is done, the schedule is only as good as the last update and it shows up in the churn numbers. On a typical site, the first week is about trust, not features and that is fine. By the second quarter, a two-week pilot answers more than a three-month evaluation and fleet telemetry is no exception.

Written by the JunoNode team in Turku. Questions? Get in touch.