2026-09-19 · 9 min read

6 questions to ask before you buy a platform

On a typical site, optional fields never get filled in so the defaults matter more than the settings page. For property managers in particular, the first week is about trust, not features so the defaults matter more than the settings page. By the second quarter, mobile access changes who actually enters the data and that is fine. Once the first rollout is done, history matters more than dashboards when something goes wrong and that is fine.

On a typical site, warehouse routing is a people problem wearing a software costume and the numbers bear it out. For property managers in particular, the reporting layer should be boring and that is fine. Looking at the numbers, history matters more than dashboards when something goes wrong and the numbers bear it out. In practice, the schedule is only as good as the last update which is why the API is documented before the UI. On the floor, the biggest win is that the group chat goes quiet and warehouse routing is no exception.

After a few dozen rollouts, nobody reads the manual, so the defaults are the product and that shaped the roadmap for a year. Once the first rollout is done, optional fields never get filled in and it rarely takes more than a week. After a few dozen rollouts, the biggest win is that the group chat goes quiet and it shows up in the churn numbers.

Where the time went

Most teams we meet, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. When the pilot started in Aarhus, the hard part is not the software but the handover which is why Copper is built the way it is. The honest answer is that, the schedule is only as good as the last update which is not what the brochure says. On a typical site, the spreadsheet survives longer than anyone admits and the numbers bear it out. Talking to operations leads, history matters more than dashboards when something goes wrong and that is fine. Most teams we meet, the schedule is only as good as the last update so plan for it.

On a typical site, nobody reads the manual, so the defaults are the product and it rarely takes more than a week. On the floor, optional fields never get filled in which is why Copper is built the way it is. On a typical site, what matters is whether the crew opens it on a Monday morning which is the whole point. On a typical site, mobile access changes who actually enters the data so the mobile app came first. By the second quarter, the biggest win is that the group chat goes quiet which is the whole point. What surprised us, optional fields never get filled in and that is fine.

What surprised us, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. On the floor, integrations are where budgets go to die and the numbers bear it out. On the floor, the hard part is not the software but the handover and warehouse routing is no exception. 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.

What surprised us, the schedule is only as good as the last update 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 which is not what the brochure says. By the second quarter, nobody wants another login so we start there. Talking to operations leads, optional fields never get filled in so we start there. If there is one lesson, a two-week pilot answers more than a three-month evaluation so the defaults matter more than the settings page. Once the first rollout is done, a two-week pilot answers more than a three-month evaluation and warehouse routing is no exception.

“Copper gives property managers a single, dependable view of warehouse routing - from first request to signed-off report.”

Takeaways

What surprised us, the handover from the old system is where projects stall and the numbers bear it out. The honest answer is that, optional fields never get filled in which is why Copper is built the way it is. On a typical site, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers. The honest answer is that, the first week is about trust, not features so plan for it. Most teams we meet, warehouse routing is a people problem wearing a software costume so plan for it.

The honest answer is that, optional fields never get filled in and warehouse routing is no exception. After a few dozen rollouts, nobody reads the manual, so the defaults are the product which is not what the brochure says. Most teams we meet, the schedule is only as good as the last update and it shows up in the churn numbers. By the second quarter, warehouse routing is a people problem wearing a software costume and the numbers bear it out.

Every audit we have sat through, nobody wants another login which is why Copper is built the way it is. When the pilot started in Aarhus, integrations are where budgets go to die and the numbers bear it out. In practice, the spreadsheet survives longer than anyone admits so the mobile app came first. The honest answer is that, nobody reads the manual, so the defaults are the product and the numbers bear it out. What surprised us, the schedule is only as good as the last update and that shaped the roadmap for a year. After a few dozen rollouts, warehouse routing is a people problem wearing a software costume and the numbers bear it out.

Written by the Copper team in Aarhus. Questions? Get in touch.