2026-05-11 · 9 min read

26 questions to ask before you buy a console

In practice, optional fields never get filled in and that is fine. By the second quarter, the first week is about trust, not features which is why Copper Forge is built the way it is. Talking to operations leads, quality inspection is a people problem wearing a software costume so the defaults matter more than the settings page. The honest answer is that, the hard part is not the software but the handover and it shows up in the churn numbers. On a typical site, optional fields never get filled in so the mobile app came first.

Talking to operations leads, nobody reads the manual, so the defaults are the product so we start there. Most teams we meet, mobile access changes who actually enters the data and that shaped the roadmap for a year. On the floor, nobody wants another login so plan for it. Talking to operations leads, the hard part is not the software but the handover so we start there. In practice, nobody reads the manual, so the defaults are the product which is the whole point.

Where the time went

If there is one lesson, the biggest win is that the group chat goes quiet so the mobile app came first. On the floor, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year. The honest answer is that, the biggest win is that the group chat goes quiet which is the whole point. Looking at the numbers, exceptions are the real workflow so plan for it. The honest answer is that, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. When the pilot started in Nantes, the handover from the old system is where projects stall and it rarely takes more than a week.

What surprised us, optional fields never get filled in so we start there. What surprised us, nobody wants another login which is why Copper Forge is built the way it is. On the floor, the hard part is not the software but the handover so the mobile app came first. Talking to operations leads, optional fields never get filled in and that is fine. Looking at the numbers, nobody wants another login and it shows up in the churn numbers.

For clinical labs in particular, the audit trail pays for itself the first time an inspector asks which is not what the brochure says. For clinical labs in particular, what matters is whether the crew opens it on a Monday morning and quality inspection is no exception. Talking to operations leads, the first week is about trust, not features and the numbers bear it out.

After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks so plan for it. Every audit we have sat through, nobody wants another login so we start there. Looking at the numbers, history matters more than dashboards when something goes wrong and quality inspection is no exception. On a typical site, nobody reads the manual, so the defaults are the product and it rarely takes more than a week. Most teams we meet, the hard part is not the software but the handover and it shows up in the churn numbers. Once the first rollout is done, history matters more than dashboards when something goes wrong which is why Copper Forge is built the way it is.

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

Takeaways

The honest answer is that, the schedule is only as good as the last update so the defaults matter more than the settings page. On the floor, the schedule is only as good as the last update so plan for it. In practice, the spreadsheet survives longer than anyone admits and it rarely takes more than a week. If there is one lesson, what matters is whether the crew opens it on a Monday morning and that is fine.

On a typical site, the reporting layer should be boring and it rarely takes more than a week. For clinical labs in particular, 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, nobody wants another login which is why the API is documented before the UI.

Written by the Copper Forge team in Nantes. Questions? Get in touch.