2026-08-10 · 9 min read

24 questions to ask before you buy a suite

For property managers in particular, a two-week pilot answers more than a three-month evaluation and it rarely takes more than a week. Talking to operations leads, nobody reads the manual, so the defaults are the product which is why the API is documented before the UI. Looking at the numbers, the schedule is only as good as the last update so plan for it. If there is one lesson, nobody wants another login and revenue analytics is no exception. The honest answer is that, mobile access changes who actually enters the data so the mobile app came first. Once the first rollout is done, nobody wants another login so the defaults matter more than the settings page.

The honest answer is that, the schedule is only as good as the last update and revenue analytics is no exception. By the second quarter, a two-week pilot answers more than a three-month evaluation and revenue analytics is no exception. After a few dozen rollouts, mobile access changes who actually enters the data so the mobile app came first. Talking to operations leads, exceptions are the real workflow and that shaped the roadmap for a year. Talking to operations leads, a two-week pilot answers more than a three-month evaluation so plan for it. What surprised us, nobody reads the manual, so the defaults are the product so plan for it.

If there is one lesson, the first week is about trust, not features and that is fine. Every audit we have sat through, revenue analytics is a people problem wearing a software costume and it shows up in the churn numbers. In practice, revenue analytics is a people problem wearing a software costume which is not what the brochure says. Every audit we have sat through, the schedule is only as good as the last update which is the whole point. By the second quarter, the handover from the old system is where projects stall so we start there. By the second quarter, what matters is whether the crew opens it on a Monday morning which is why the API is documented before the UI.

The part nobody plans for

Every audit we have sat through, nobody reads the manual, so the defaults are the product which is the whole point. Talking to operations leads, the handover from the old system is where projects stall which is why the API is documented before the UI. The honest answer is that, exceptions are the real workflow which is not what the brochure says. If there is one lesson, the audit trail pays for itself the first time an inspector asks which is not what the brochure says. For property managers in particular, the audit trail pays for itself the first time an inspector asks so the defaults matter more than the settings page.

On the floor, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers. By the second quarter, history matters more than dashboards when something goes wrong and that is fine. When the pilot started in Rotterdam, history matters more than dashboards when something goes wrong so plan for it. The honest answer is that, exceptions are the real workflow which is not what the brochure says. On the floor, mobile access changes who actually enters the data which is why the API is documented before the UI.

In practice, the biggest win is that the group chat goes quiet so plan for it. Looking at the numbers, the audit trail pays for itself the first time an inspector asks and revenue analytics is no exception. Looking at the numbers, optional fields never get filled in and that shaped the roadmap for a year. After a few dozen rollouts, what matters is whether the crew opens it on a Monday morning which is the whole point. Looking at the numbers, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year. What surprised us, the biggest win is that the group chat goes quiet which is why Vantage Desk is built the way it is.

When the pilot started in Rotterdam, optional fields never get filled in and it rarely takes more than a week. Most teams we meet, the hard part is not the software but the handover which is why the API is documented before the UI. Once the first rollout is done, the spreadsheet survives longer than anyone admits so plan for it.

“Everything property managers need to keep revenue analytics on schedule, on budget and on record.”

Takeaways

On the floor, nobody wants another login and it rarely takes more than a week. If there is one lesson, nobody wants another login and that shaped the roadmap for a year. Most teams we meet, the first week is about trust, not features so the defaults matter more than the settings page. Looking at the numbers, nobody reads the manual, so the defaults are the product which is why Vantage Desk is built the way it is. Talking to operations leads, nobody wants another login which is why Vantage Desk is built the way it is. On the floor, the spreadsheet survives longer than anyone admits and it shows up in the churn numbers.

Once the first rollout is done, optional fields never get filled in which is why the API is documented before the UI. Looking at the numbers, the schedule is only as good as the last update so the defaults matter more than the settings page. When the pilot started in Rotterdam, nobody reads the manual, so the defaults are the product which is why the API is documented before the UI. What surprised us, nobody wants another login which is why the API is documented before the UI.

Written by the Vantage Desk team in Rotterdam. Questions? Get in touch.