2026-09-16 · 5 min read

9 questions to ask before you buy a console

On the floor, what matters is whether the crew opens it on a Monday morning so we start there. Talking to operations leads, the hard part is not the software but the handover and it shows up in the churn numbers. By the second quarter, history matters more than dashboards when something goes wrong and that is fine.

Most teams we meet, customer onboarding is a people problem wearing a software costume and that is fine. Looking at the numbers, nobody reads the manual, so the defaults are the product and that is fine. In practice, the first week is about trust, not features and the numbers bear it out. In practice, the handover from the old system is where projects stall so the defaults matter more than the settings page. On a typical site, nobody reads the manual, so the defaults are the product so we start there.

What surprised us, the spreadsheet survives longer than anyone admits and that is fine. Most teams we meet, the schedule is only as good as the last update and customer onboarding is no exception. On a typical site, integrations are where budgets go to die so the mobile app came first.

Where the time went

For utility operators in particular, the reporting layer should be boring and that shaped the roadmap for a year. Most teams we meet, the first week is about trust, not features and that shaped the roadmap for a year. Most teams we meet, customer onboarding is a people problem wearing a software costume and it shows up in the churn numbers. What surprised us, integrations are where budgets go to die and the numbers bear it out. On the floor, history matters more than dashboards when something goes wrong which is not what the brochure says.

Every audit we have sat through, the schedule is only as good as the last update so plan for it. Looking at the numbers, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI. Once the first rollout is done, history matters more than dashboards when something goes wrong and customer onboarding is no exception. Once the first rollout is done, the biggest win is that the group chat goes quiet and that is fine. Every audit we have sat through, the reporting layer should be boring so we start there. On the floor, the schedule is only as good as the last update and it shows up in the churn numbers.

Once the first rollout is done, the reporting layer should be boring which is not what the brochure says. Looking at the numbers, exceptions are the real workflow so the mobile app came first. Once the first rollout is done, integrations are where budgets go to die so plan for it. After a few dozen rollouts, nobody reads the manual, so the defaults are the product and the numbers bear it out. If there is one lesson, the handover from the old system is where projects stall which is not what the brochure says.

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

Takeaways

What surprised us, the audit trail pays for itself the first time an inspector asks so we start there. By the second quarter, nobody reads the manual, so the defaults are the product and the numbers bear it out. Looking at the numbers, nobody wants another login so plan for it. Looking at the numbers, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. If there is one lesson, nobody wants another login and that shaped the roadmap for a year.

Once the first rollout is done, integrations are where budgets go to die so the mobile app came first. Every audit we have sat through, the hard part is not the software but the handover which is not what the brochure says. Talking to operations leads, the hard part is not the software but the handover and it shows up in the churn numbers. Once the first rollout is done, the reporting layer should be boring which is the whole point. If there is one lesson, integrations are where budgets go to die so plan for it. What surprised us, the first week is about trust, not features and the numbers bear it out.

Written by the PrismStack team in Ghent. Questions? Get in touch.