2026-08-11 · 5 min read

16 questions to ask before you buy a console

Every audit we have sat through, exceptions are the real workflow and that is fine. The honest answer is that, nobody reads the manual, so the defaults are the product so we start there. In practice, the schedule is only as good as the last update and that shaped the roadmap for a year. On a typical site, nobody reads the manual, so the defaults are the product which is not what the brochure says. Once the first rollout is done, nobody reads the manual, so the defaults are the product so the mobile app came first. By the second quarter, exceptions are the real workflow and that shaped the roadmap for a year.

Every audit we have sat through, integrations are where budgets go to die which is the whole point. Talking to operations leads, field service scheduling is a people problem wearing a software costume and that is fine. For utility operators in particular, the schedule is only as good as the last update and it shows up in the churn numbers. For utility operators in particular, the first week is about trust, not features so the mobile app came first.

What actually happened

What surprised us, the hard part is not the software but the handover and that shaped the roadmap for a year. For utility operators in particular, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. By the second quarter, the audit trail pays for itself the first time an inspector asks and field service scheduling is no exception. Talking to operations leads, integrations are where budgets go to die which is not what the brochure says. On a typical site, integrations are where budgets go to die which is why the API is documented before the UI. Talking to operations leads, the audit trail pays for itself the first time an inspector asks so we start there.

Talking to operations leads, the first week is about trust, not features so we start there. In practice, optional fields never get filled in and field service scheduling is no exception. Looking at the numbers, field service scheduling is a people problem wearing a software costume and field service scheduling is no exception. On a typical site, the handover from the old system is where projects stall which is the whole point.

After a few dozen rollouts, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. For utility operators in particular, exceptions are the real workflow which is why Copper Core is built the way it is. Every audit we have sat through, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers. If there is one lesson, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. Every audit we have sat through, the hard part is not the software but the handover and it shows up in the churn numbers. Talking to operations leads, the biggest win is that the group chat goes quiet which is why Copper Core is built the way it is.

Talking to operations leads, nobody wants another login and that shaped the roadmap for a year. On a typical site, mobile access changes who actually enters the data so the defaults matter more than the settings page. If there is one lesson, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page. By the second quarter, the spreadsheet survives longer than anyone admits which is the whole point. Talking to operations leads, what matters is whether the crew opens it on a Monday morning so we start there.

“Copper Core gives utility operators a single, dependable view of field service scheduling - from first request to signed-off report.”

Takeaways

Every audit we have sat through, integrations are where budgets go to die and it rarely takes more than a week. In practice, field service scheduling is a people problem wearing a software costume so we start there. By the second quarter, the reporting layer should be boring so the mobile app came first. Every audit we have sat through, mobile access changes who actually enters the data and that shaped the roadmap for a year. On a typical site, the schedule is only as good as the last update so we start there.

On the floor, mobile access changes who actually enters the data and the numbers bear it out. Once the first rollout is done, history matters more than dashboards when something goes wrong which is not what the brochure says. Most teams we meet, nobody reads the manual, so the defaults are the product so the mobile app came first.

On a typical site, the handover from the old system is where projects stall and the numbers bear it out. Looking at the numbers, exceptions are the real workflow which is not what the brochure says. When the pilot started in Rotterdam, the schedule is only as good as the last update which is not what the brochure says.

Written by the Copper Core team in Rotterdam. Questions? Get in touch.