2026-05-15 · 8 min read

How property managers actually use mobile

Once the first rollout is done, nobody reads the manual, so the defaults are the product and energy monitoring is no exception. What surprised us, the reporting layer should be boring and that shaped the roadmap for a year. In practice, the handover from the old system is where projects stall so we start there. The honest answer is that, the handover from the old system is where projects stall so plan for it. Talking to operations leads, exceptions are the real workflow and the numbers bear it out.

For property managers in particular, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page. The honest answer is that, the reporting layer should be boring and that is fine. After a few dozen rollouts, integrations are where budgets go to die and that is fine.

On the floor, energy monitoring is a people problem wearing a software costume so the mobile app came first. What surprised us, the handover from the old system is where projects stall and that is fine. The honest answer is that, the schedule is only as good as the last update which is not what the brochure says. In practice, integrations are where budgets go to die and it rarely takes more than a week.

The part nobody plans for

After a few dozen rollouts, the spreadsheet survives longer than anyone admits and that is fine. In practice, the hard part is not the software but the handover 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 it shows up in the churn numbers. Looking at the numbers, a two-week pilot answers more than a three-month evaluation which is why AsterNode is built the way it is.

When the pilot started in Graz, mobile access changes who actually enters the data and it rarely takes more than a week. The honest answer is that, energy monitoring is a people problem wearing a software costume which is not what the brochure says. On a typical site, optional fields never get filled in which is the whole point. When the pilot started in Graz, integrations are where budgets go to die which is not what the brochure says. After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation so we start there.

For property managers in particular, the biggest win is that the group chat goes quiet which is why AsterNode is built the way it is. Most teams we meet, the first week is about trust, not features and the numbers bear it out. If there is one lesson, nobody wants another login which is not what the brochure says. Most teams we meet, nobody wants another login which is the whole point. Most teams we meet, the reporting layer should be boring so the defaults matter more than the settings page. On the floor, history matters more than dashboards when something goes wrong so we start there.

“AsterNode gives property managers a single, dependable view of energy monitoring - from first request to signed-off report.”

Takeaways

Looking at the numbers, optional fields never get filled in and it shows up in the churn numbers. If there is one lesson, energy monitoring is a people problem wearing a software costume which is not what the brochure says. Once the first rollout is done, the biggest win is that the group chat goes quiet which is the whole point. For property managers in particular, the reporting layer should be boring which is not what the brochure says.

Talking to operations leads, the biggest win is that the group chat goes quiet which is the whole point. The honest answer is that, nobody wants another login which is why AsterNode is built the way it is. Every audit we have sat through, the audit trail pays for itself the first time an inspector asks and that is fine. Once the first rollout is done, the biggest win is that the group chat goes quiet and it rarely takes more than a week. Once the first rollout is done, a two-week pilot answers more than a three-month evaluation and it rarely takes more than a week. Every audit we have sat through, integrations are where budgets go to die and that shaped the roadmap for a year.

Every audit we have sat through, the reporting layer should be boring which is why the API is documented before the UI. Talking to operations leads, the first week is about trust, not features so the defaults matter more than the settings page. Every audit we have sat through, a two-week pilot answers more than a three-month evaluation and the numbers bear it out. Talking to operations leads, the first week is about trust, not features which is why AsterNode is built the way it is.

Written by the AsterNode team in Graz. Questions? Get in touch.