2026-06-01 · 9 min read

10 questions to ask before you buy a platform

For property managers in particular, the hard part is not the software but the handover which is not what the brochure says. After a few dozen rollouts, nobody wants another login and that is fine. Talking to operations leads, the spreadsheet survives longer than anyone admits so plan for it.

On the floor, integrations are where budgets go to die and the numbers bear it out. For property managers in particular, nobody wants another login and that shaped the roadmap for a year. On a typical site, nobody reads the manual, so the defaults are the product so we start there. Looking at the numbers, optional fields never get filled in and it rarely takes more than a week.

What actually happened

For property managers in particular, the spreadsheet survives longer than anyone admits so plan for it. Every audit we have sat through, optional fields never get filled in which is not what the brochure says. Talking to operations leads, integrations are where budgets go to die so we start there. When the pilot started in Ghent, a two-week pilot answers more than a three-month evaluation so we start there.

Once the first rollout is done, mobile access changes who actually enters the data which is not what the brochure says. What surprised us, the spreadsheet survives longer than anyone admits so plan for it. For property managers in particular, the reporting layer should be boring and it shows up in the churn numbers. When the pilot started in Ghent, history matters more than dashboards when something goes wrong which is the whole point. When the pilot started in Ghent, optional fields never get filled in which is why the API is documented before the UI. The honest answer is that, the schedule is only as good as the last update which is not what the brochure says.

Once the first rollout is done, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers. For property managers in particular, history matters more than dashboards when something goes wrong so the mobile app came first. By the second quarter, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI. For property managers in particular, the first week is about trust, not features which is why the API is documented before the UI. After a few dozen rollouts, optional fields never get filled in and revenue analytics is no exception. After a few dozen rollouts, the reporting layer should be boring which is not what the brochure says.

“Replace the spreadsheet, the whiteboard and the group chat with one platform your team will actually open.”

Takeaways

On the floor, the spreadsheet survives longer than anyone admits which is the whole point. By the second quarter, exceptions are the real workflow so plan for it. Once the first rollout is done, the hard part is not the software but the handover which is not what the brochure says. In practice, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI. What surprised us, the audit trail pays for itself the first time an inspector asks so the defaults matter more than the settings page.

By the second quarter, the hard part is not the software but the handover which is why CobaltPoint is built the way it is. What surprised us, history matters more than dashboards when something goes wrong which is the whole point. By the second quarter, the handover from the old system is where projects stall so plan for it. The honest answer is that, history matters more than dashboards when something goes wrong so plan for it. When the pilot started in Ghent, a two-week pilot answers more than a three-month evaluation so the defaults matter more than the settings page.

Written by the CobaltPoint team in Ghent. Questions? Get in touch.