2026-09-09 · 9 min read

Permissions are a product decision

In practice, optional fields never get filled in and the numbers bear it out. Every audit we have sat through, optional fields never get filled in so the defaults matter more than the settings page. After a few dozen rollouts, exceptions are the real workflow which is why Copper is built the way it is. When the pilot started in Aarhus, a two-week pilot answers more than a three-month evaluation and the numbers bear it out. For property managers in particular, the reporting layer should be boring which is not what the brochure says. After a few dozen rollouts, 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, the biggest win is that the group chat goes quiet and warehouse routing is no exception. In practice, mobile access changes who actually enters the data and that is fine. What surprised us, a two-week pilot answers more than a three-month evaluation and the numbers bear it out. The honest answer is that, the first week is about trust, not features and that is fine. For property managers in particular, the audit trail pays for itself the first time an inspector asks and warehouse routing is no exception. What surprised us, the biggest win is that the group chat goes quiet so plan for it.

By the second quarter, optional fields never get filled in which is why Copper is built the way it is. On the floor, nobody reads the manual, so the defaults are the product and warehouse routing is no exception. Once the first rollout is done, the reporting layer should be boring and that shaped the roadmap for a year.

Where the time went

Every audit we have sat through, nobody wants another login and the numbers bear it out. On the floor, what matters is whether the crew opens it on a Monday morning and the numbers bear it out. On a typical site, the hard part is not the software but the handover and that is fine. Once the first rollout is done, warehouse routing is a people problem wearing a software costume and the numbers bear it out. Once the first rollout is done, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers. After a few dozen rollouts, nobody wants another login and it shows up in the churn numbers.

On a typical site, a two-week pilot answers more than a three-month evaluation so the mobile app came first. Once the first rollout is done, integrations are where budgets go to die which is why the API is documented before the UI. Every audit we have sat through, the biggest win is that the group chat goes quiet so plan for it. For property managers in particular, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year.

If there is one lesson, nobody reads the manual, so the defaults are the product so we start there. If there is one lesson, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week. After a few dozen rollouts, the spreadsheet survives longer than anyone admits and the numbers bear it out. In practice, exceptions are the real workflow so plan for it. If there is one lesson, exceptions are the real workflow which is why the API is documented before the UI. By the second quarter, warehouse routing is a people problem wearing a software costume and it shows up in the churn numbers.

“Everything property managers need to keep warehouse routing on schedule, on budget and on record.”

What to do on Monday

By the second quarter, the handover from the old system is where projects stall so the defaults matter more than the settings page. Talking to operations leads, nobody reads the manual, so the defaults are the product so we start there. By the second quarter, nobody wants another login so the defaults matter more than the settings page. If there is one lesson, nobody reads the manual, so the defaults are the product and the numbers bear it out.

For property managers in particular, history matters more than dashboards when something goes wrong which is the whole point. The honest answer is that, the handover from the old system is where projects stall and warehouse routing is no exception. Every audit we have sat through, the biggest win is that the group chat goes quiet which is why the API is documented before the UI.

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