2026-08-11 · 8 min read

How property managers actually use mobile

Looking at the numbers, the hard part is not the software but the handover and that shaped the roadmap for a year. What surprised us, a two-week pilot answers more than a three-month evaluation which is not what the brochure says. Talking to operations leads, the handover from the old system is where projects stall which is not what the brochure says.

Once the first rollout is done, integrations are where budgets go to die which is the whole point. Looking at the numbers, the first week is about trust, not features and it rarely takes more than a week. Once the first rollout is done, optional fields never get filled in and that shaped the roadmap for a year.

What actually happened

For property managers in particular, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week. For property managers in particular, the audit trail pays for itself the first time an inspector asks which is why the API is documented before the UI. On the floor, the audit trail pays for itself the first time an inspector asks and that is fine. The honest answer is that, the first week is about trust, not features which is why Solace Loop is built the way it is. Looking at the numbers, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. In practice, nobody reads the manual, so the defaults are the product so the mobile app came first.

When the pilot started in Bologna, nobody wants another login and it shows up in the churn numbers. Looking at the numbers, history matters more than dashboards when something goes wrong so plan for it. Every audit we have sat through, the audit trail pays for itself the first time an inspector asks which is not what the brochure says.

Talking to operations leads, the hard part is not the software but the handover which is the whole point. In practice, nobody wants another login which is not what the brochure says. On a typical site, history matters more than dashboards when something goes wrong and the numbers bear it out.

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

What to do on Monday

Looking at the numbers, nobody reads the manual, so the defaults are the product which is why Solace Loop is built the way it is. Once the first rollout is done, the handover from the old system is where projects stall so the defaults matter more than the settings page. Every audit we have sat through, the reporting layer should be boring which is why Solace Loop is built the way it is. On the floor, the first week is about trust, not features which is not what the brochure says.

If there is one lesson, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week. After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks which is the whole point. In practice, optional fields never get filled in and energy monitoring is no exception. Talking to operations leads, mobile access changes who actually enters the data so we start there. When the pilot started in Bologna, exceptions are the real workflow and it rarely takes more than a week.

In practice, history matters more than dashboards when something goes wrong which is why the API is documented before the UI. What surprised us, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page. Every audit we have sat through, energy monitoring is a people problem wearing a software costume so plan for it. After a few dozen rollouts, the biggest win is that the group chat goes quiet so plan for it. For property managers in particular, optional fields never get filled in which is the whole point.

Written by the Solace Loop team in Bologna. Questions? Get in touch.