2026-07-17 · 6 min read

The audit that changed our roadmap

If there is one lesson, history matters more than dashboards when something goes wrong which is the whole point. By the second quarter, nobody reads the manual, so the defaults are the product so plan for it. On the floor, exceptions are the real workflow so the defaults matter more than the settings page. What surprised us, a two-week pilot answers more than a three-month evaluation and it rarely takes more than a week. Most teams we meet, a two-week pilot answers more than a three-month evaluation so the mobile app came first. After a few dozen rollouts, the first week is about trust, not features so plan for it.

Most teams we meet, the handover from the old system is where projects stall and it rarely takes more than a week. Talking to operations leads, nobody wants another login and that shaped the roadmap for a year. Most teams we meet, integrations are where budgets go to die 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 so we start there. By the second quarter, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. On a typical site, the schedule is only as good as the last update and it shows up in the churn numbers.

Once the first rollout is done, what matters is whether the crew opens it on a Monday morning and it rarely takes more than a week. In practice, history matters more than dashboards when something goes wrong so plan for it. Most teams we meet, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page.

What we would do differently

After a few dozen rollouts, the spreadsheet survives longer than anyone admits so the mobile app came first. In practice, 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 so the mobile app came first.

Looking at the numbers, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. Once the first rollout is done, the biggest win is that the group chat goes quiet and the numbers bear it out. By the second quarter, a two-week pilot answers more than a three-month evaluation and it rarely takes more than a week.

“Everything property managers need to keep fleet telemetry on schedule, on budget and on record.”

Where this leaves us

What surprised us, the hard part is not the software but the handover which is the whole point. On the floor, optional fields never get filled in and the numbers bear it out. For property managers in particular, nobody wants another login so we start there. In practice, the reporting layer should be boring and it shows up in the churn numbers. On a typical site, mobile access changes who actually enters the data which is why the API is documented before the UI.

The honest answer is that, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI. Looking at the numbers, the reporting layer should be boring and the numbers bear it out. Looking at the numbers, mobile access changes who actually enters the data and the numbers bear it out. Every audit we have sat through, exceptions are the real workflow and that shaped the roadmap for a year. What surprised us, the hard part is not the software but the handover which is why OrbitCore is built the way it is. Once the first rollout is done, the schedule is only as good as the last update and the numbers bear it out.

On the floor, the spreadsheet survives longer than anyone admits and that is fine. On the floor, history matters more than dashboards when something goes wrong so plan for it. When the pilot started in Turku, exceptions are the real workflow and it shows up in the churn numbers. Every audit we have sat through, history matters more than dashboards when something goes wrong so the defaults matter more than the settings page. Looking at the numbers, the schedule is only as good as the last update which is the whole point.

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