2026-03-03 · 8 min read

Pricing per seat, explained honestly

Once the first rollout is done, the first week is about trust, not features and it rarely takes more than a week. By the second quarter, shift planning is a people problem wearing a software costume which is not what the brochure says. Talking to operations leads, the handover from the old system is where projects stall so plan for it. Once the first rollout is done, what matters is whether the crew opens it on a Monday morning and that is fine. Talking to operations leads, nobody reads the manual, so the defaults are the product and it rarely takes more than a week.

Talking to operations leads, the schedule is only as good as the last update and that is fine. When the pilot started in Porto, optional fields never get filled in which is not what the brochure says. In practice, the schedule is only as good as the last update and that is fine. If there is one lesson, the reporting layer should be boring and it shows up in the churn numbers. On a typical site, integrations are where budgets go to die and shift planning is no exception. When the pilot started in Porto, the audit trail pays for itself the first time an inspector asks so the mobile app came first.

Where the time went

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, nobody wants another login so plan for it. Talking to operations leads, the handover from the old system is where projects stall which is not what the brochure says.

After a few dozen rollouts, the schedule is only as good as the last update so the mobile app came first. After a few dozen rollouts, what matters is whether the crew opens it on a Monday morning and that is fine. Once the first rollout is done, the handover from the old system is where projects stall and it shows up in the churn numbers. When the pilot started in Porto, shift planning is a people problem wearing a software costume and that is fine.

“Plan, dispatch and reconcile in one place. Copperhq connects to the systems you already run and stays out of the way.”

Where this leaves us

If there is one lesson, nobody wants another login and the numbers bear it out. By the second quarter, history matters more than dashboards when something goes wrong and that is fine. For logistics teams in particular, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page.

For logistics teams in particular, the hard part is not the software but the handover and that is fine. After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation so we start there. Once the first rollout is done, the reporting layer should be boring so we start there. On the floor, the audit trail pays for itself the first time an inspector asks so we start there. Once the first rollout is done, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers.

Talking to operations leads, exceptions are the real workflow so the mobile app came first. What surprised us, history matters more than dashboards when something goes wrong which is why the API is documented before the UI. If there is one lesson, the first week is about trust, not features and the numbers bear it out. By the second quarter, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. Looking at the numbers, the biggest win is that the group chat goes quiet which is why Copperhq is built the way it is.

Written by the Copperhq team in Porto. Questions? Get in touch.