2026-09-05 · 5 min read

What changed in JunoNode this quarter

Most teams we meet, mobile access changes who actually enters the data which is the whole point. On a typical site, the audit trail pays for itself the first time an inspector asks and the numbers bear it out. When the pilot started in Turku, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week. The honest answer is that, the spreadsheet survives longer than anyone admits which is the whole point.

When the pilot started in Turku, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. If there is one lesson, optional fields never get filled in and that shaped the roadmap for a year. Every audit we have sat through, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page. For mid-market manufacturers in particular, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI. On a typical site, history matters more than dashboards when something goes wrong which is not what the brochure says.

Where the time went

Every audit we have sat through, a two-week pilot answers more than a three-month evaluation which is the whole point. Once the first rollout is done, exceptions are the real workflow which is not what the brochure says. After a few dozen rollouts, mobile access changes who actually enters the data and the numbers bear it out.

When the pilot started in Turku, nobody reads the manual, so the defaults are the product so the mobile app came first. After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks so we start there. Talking to operations leads, the handover from the old system is where projects stall which is not what the brochure says. Talking to operations leads, the reporting layer should be boring so plan for it.

For mid-market manufacturers in particular, the hard part is not the software but the handover so we start there. When the pilot started in Turku, the handover from the old system is where projects stall which is why JunoNode is built the way it is. What surprised us, the spreadsheet survives longer than anyone admits and that is fine. Once the first rollout is done, the biggest win is that the group chat goes quiet and that shaped the roadmap for a year.

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

What to do on Monday

Talking to operations leads, nobody reads the manual, so the defaults are the product and fleet telemetry is no exception. By the second quarter, fleet telemetry is a people problem wearing a software costume which is not what the brochure says. If there is one lesson, history matters more than dashboards when something goes wrong and it rarely takes more than a week.

Looking at the numbers, the hard part is not the software but the handover so the defaults matter more than the settings page. On the floor, nobody reads the manual, so the defaults are the product so the mobile app came first. Looking at the numbers, nobody reads the manual, so the defaults are the product which is the whole point. Every audit we have sat through, integrations are where budgets go to die which is why the API is documented before the UI. The honest answer is that, fleet telemetry is a people problem wearing a software costume and that shaped the roadmap for a year. On the floor, fleet telemetry is a people problem wearing a software costume which is why JunoNode is built the way it is.

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