2026-08-09 · 7 min read

From pilot to plant: a 13-week timeline

By the second quarter, the hard part is not the software but the handover which is not what the brochure says. On a typical site, integrations are where budgets go to die which is not what the brochure says. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning so we start there. On the floor, mobile access changes who actually enters the data and fleet telemetry is no exception.

What surprised us, integrations are where budgets go to die so plan for it. Looking at the numbers, optional fields never get filled in and it shows up in the churn numbers. By the second quarter, mobile access changes who actually enters the data and the numbers bear it out.

What we would do differently

In practice, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers. What surprised us, the spreadsheet survives longer than anyone admits so plan for it. Most teams we meet, the handover from the old system is where projects stall which is why the API is documented before the UI. Talking to operations leads, what matters is whether the crew opens it on a Monday morning so the mobile app came first.

By the second quarter, nobody wants another login and fleet telemetry is no exception. The honest answer is that, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI. On the floor, the hard part is not the software but the handover and that is fine. For utility operators in particular, fleet telemetry is a people problem wearing a software costume and that is fine. Once the first rollout is done, the schedule is only as good as the last update and that is fine.

The honest answer is that, mobile access changes who actually enters the data and that is fine. Every audit we have sat through, the first week is about trust, not features and that shaped the roadmap for a year. Talking to operations leads, the reporting layer should be boring which is not what the brochure says. Once the first rollout is done, nobody wants another login which is not what the brochure says. If there is one lesson, nobody wants another login which is why the API is documented before the UI.

What surprised us, history matters more than dashboards when something goes wrong which is why the API is documented before the UI. On the floor, exceptions are the real workflow and fleet telemetry is no exception. On a typical site, the schedule is only as good as the last update and that is fine.

“Plan, dispatch and reconcile in one place. Harborhq connects to the systems you already run and stays out of the way.”

What to do on Monday

On the floor, the audit trail pays for itself the first time an inspector asks so the defaults matter more than the settings page. By the second quarter, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. In practice, nobody reads the manual, so the defaults are the product so the mobile app came first. The honest answer is that, exceptions are the real workflow so the defaults matter more than the settings page. What surprised us, integrations are where budgets go to die which is not what the brochure says.

When the pilot started in Turku, the schedule is only as good as the last update which is why the API is documented before the UI. In practice, exceptions are the real workflow which is why the API is documented before the UI. Once the first rollout is done, nobody reads the manual, so the defaults are the product which is why the API is documented before the UI.

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