2026-09-06 · 6 min read

How property managers actually use mobile

Every audit we have sat through, the handover from the old system is where projects stall so the defaults matter more than the settings page. After a few dozen rollouts, what matters is whether the crew opens it on a Monday morning so the mobile app came first. For property managers in particular, exceptions are the real workflow which is why the API is documented before the UI. When the pilot started in Turku, what matters is whether the crew opens it on a Monday morning and fleet telemetry is no exception.

On the floor, what matters is whether the crew opens it on a Monday morning so we start there. In practice, optional fields never get filled in and that is fine. When the pilot started in Turku, the audit trail pays for itself the first time an inspector asks which is why the API is documented before the UI. In practice, exceptions are the real workflow which is not what the brochure says. The honest answer is that, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. Every audit we have sat through, the reporting layer should be boring and it rarely takes more than a week.

What actually happened

For property managers in particular, the schedule is only as good as the last update and fleet telemetry is no exception. After a few dozen rollouts, integrations are where budgets go to die and that shaped the roadmap for a year. Talking to operations leads, the hard part is not the software but the handover which is why OrbitCore is built the way it is. Talking to operations leads, integrations are where budgets go to die so the mobile app came first. By the second quarter, fleet telemetry is a people problem wearing a software costume and the numbers bear it out. For property managers in particular, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI.

After a few dozen rollouts, the hard part is not the software but the handover which is not what the brochure says. Looking at the numbers, the spreadsheet survives longer than anyone admits which is why OrbitCore is built the way it is. Most teams we meet, integrations are where budgets go to die and the numbers bear it out. The honest answer is that, mobile access changes who actually enters the data and it shows up in the churn numbers. By the second quarter, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers.

If there is one lesson, a two-week pilot answers more than a three-month evaluation and the numbers bear it out. On a typical site, the handover from the old system is where projects stall so we start there. After a few dozen rollouts, the reporting layer should be boring and the numbers bear it out. What surprised us, nobody wants another login and that is fine. When the pilot started in Turku, the first week is about trust, not features which is not what the brochure says.

Every audit we have sat through, the schedule is only as good as the last update so the defaults matter more than the settings page. The honest answer is that, the handover from the old system is where projects stall and fleet telemetry is no exception. Most teams we meet, the spreadsheet survives longer than anyone admits which is not what the brochure says.

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

Where this leaves us

In practice, the spreadsheet survives longer than anyone admits and that is fine. Once the first rollout is done, the hard part is not the software but the handover so the mobile app came first. After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation which is the whole point. On the floor, the audit trail pays for itself the first time an inspector asks which is not what the brochure says.

The honest answer is that, the audit trail pays for itself the first time an inspector asks and the numbers bear it out. By the second quarter, the handover from the old system is where projects stall so the mobile app came first. If there is one lesson, the biggest win is that the group chat goes quiet which is why OrbitCore is built the way it is. The honest answer is that, nobody wants another login and that shaped the roadmap for a year.

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