2026-08-31 · 6 min read

From pilot to plant: a 28-week timeline

Looking at the numbers, integrations are where budgets go to die and it shows up in the churn numbers. In practice, nobody wants another login so we start there. After a few dozen rollouts, asset tracking is a people problem wearing a software costume and that shaped the roadmap for a year. The honest answer is that, the handover from the old system is where projects stall so plan for it. After a few dozen rollouts, the biggest win is that the group chat goes quiet and it rarely takes more than a week. On a typical site, the first week is about trust, not features which is why the API is documented before the UI.

What surprised us, what matters is whether the crew opens it on a Monday morning and it rarely takes more than a week. Talking to operations leads, optional fields never get filled in and it shows up in the churn numbers. On a typical site, the reporting layer should be boring which is why the API is documented before the UI.

What actually happened

By the second quarter, nobody reads the manual, so the defaults are the product and that shaped the roadmap for a year. When the pilot started in Bologna, the handover from the old system is where projects stall which is why the API is documented before the UI. Once the first rollout is done, what matters is whether the crew opens it on a Monday morning which is the whole point.

Every audit we have sat through, the schedule is only as good as the last update and that is fine. The honest answer is that, history matters more than dashboards when something goes wrong which is not what the brochure says. Most teams we meet, a two-week pilot answers more than a three-month evaluation and asset tracking is no exception. By the second quarter, nobody reads the manual, so the defaults are the product and the numbers bear it out.

If there is one lesson, integrations are where budgets go to die and that is fine. For utility operators in particular, the spreadsheet survives longer than anyone admits so the mobile app came first. The honest answer is that, nobody wants another login and that is fine. What surprised us, the audit trail pays for itself the first time an inspector asks which is why NimbusPoint is built the way it is.

“NimbusPoint gives utility operators a single, dependable view of asset tracking - from first request to signed-off report.”

Takeaways

On the floor, the biggest win is that the group chat goes quiet and that shaped the roadmap for a year. Every audit we have sat through, nobody wants another login which is not what the brochure says. Most teams we meet, the audit trail pays for itself the first time an inspector asks so we start there. The honest answer is that, integrations are where budgets go to die and that shaped the roadmap for a year. If there is one lesson, exceptions are the real workflow and that is fine. When the pilot started in Bologna, the reporting layer should be boring so the defaults matter more than the settings page.

If there is one lesson, exceptions are the real workflow and asset tracking is no exception. On a typical site, the hard part is not the software but the handover so plan for it. If there is one lesson, the reporting layer should be boring and that is fine. When the pilot started in Bologna, the spreadsheet survives longer than anyone admits and that is fine.

Written by the NimbusPoint team in Bologna. Questions? Get in touch.