2026-07-03 · 6 min read

The audit that changed our roadmap

On the floor, optional fields never get filled in and that is fine. Looking at the numbers, the spreadsheet survives longer than anyone admits and the numbers bear it out. Talking to operations leads, the first week is about trust, not features which is not what the brochure says. The honest answer is that, history matters more than dashboards when something goes wrong so plan for it.

For property managers in particular, the biggest win is that the group chat goes quiet and the numbers bear it out. Once the first rollout is done, nobody wants another login which is why the API is documented before the UI. By the second quarter, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI. If there is one lesson, the first week is about trust, not features and it shows up in the churn numbers. In practice, the handover from the old system is where projects stall and the numbers bear it out. If there is one lesson, the first week is about trust, not features and that shaped the roadmap for a year.

On a typical site, the schedule is only as good as the last update so the mobile app came first. Talking to operations leads, nobody reads the manual, so the defaults are the product and it rarely takes more than a week. What surprised us, the handover from the old system is where projects stall and that is fine. Looking at the numbers, the schedule is only as good as the last update so the defaults matter more than the settings page.

What we would do differently

When the pilot started in Brno, history matters more than dashboards when something goes wrong which is not what the brochure says. The honest answer is that, optional fields never get filled in which is why the API is documented before the UI. When the pilot started in Brno, optional fields never get filled in which is why the API is documented before the UI. Every audit we have sat through, the reporting layer should be boring which is the whole point. When the pilot started in Brno, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. Every audit we have sat through, mobile access changes who actually enters the data which is not what the brochure says.

Talking to operations leads, nobody wants another login which is not what the brochure says. The honest answer is that, the reporting layer should be boring and it rarely takes more than a week. When the pilot started in Brno, mobile access changes who actually enters the data and supplier management is no exception. Talking to operations leads, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. On the floor, the audit trail pays for itself the first time an inspector asks and that is fine.

Looking at the numbers, the biggest win is that the group chat goes quiet so the defaults matter more than the settings page. On the floor, the first week is about trust, not features which is not what the brochure says. By the second quarter, the schedule is only as good as the last update and that is fine.

“Pivot Desk gives property managers a single, dependable view of supplier management - from first request to signed-off report.”

What to do on Monday

On the floor, supplier management is a people problem wearing a software costume which is the whole point. Looking at the numbers, integrations are where budgets go to die and supplier management is no exception. In practice, the audit trail pays for itself the first time an inspector asks which is why Pivot Desk is built the way it is. Most teams we meet, the schedule is only as good as the last update which is why the API is documented before the UI.

For property managers in particular, supplier management is a people problem wearing a software costume and it rarely takes more than a week. Once the first rollout is done, integrations are where budgets go to die and the numbers bear it out. After a few dozen rollouts, history matters more than dashboards when something goes wrong and it rarely takes more than a week. Once the first rollout is done, the biggest win is that the group chat goes quiet so we start there.

Written by the Pivot Desk team in Brno. Questions? Get in touch.