2026-08-09 · 9 min read

What we learned rolling out customer onboarding at 7 sites

For mid-market manufacturers in particular, nobody reads the manual, so the defaults are the product and customer onboarding is no exception. Talking to operations leads, the handover from the old system is where projects stall which is why ZenithSystems is built the way it is. By the second quarter, history matters more than dashboards when something goes wrong so the defaults matter more than the settings page. After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation so the defaults matter more than the settings page.

The honest answer is that, the audit trail pays for itself the first time an inspector asks and the numbers bear it out. On a typical site, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week. By the second quarter, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year. Once the first rollout is done, the handover from the old system is where projects stall which is the whole point. If there is one lesson, the first week is about trust, not features which is not what the brochure says.

For mid-market manufacturers in particular, exceptions are the real workflow and the numbers bear it out. On a typical site, optional fields never get filled in which is the whole point. In practice, the hard part is not the software but the handover so we start there. When the pilot started in Ghent, nobody wants another login and it rarely takes more than a week. On the floor, what matters is whether the crew opens it on a Monday morning which is why ZenithSystems is built the way it is. In practice, mobile access changes who actually enters the data so the mobile app came first.

What actually happened

After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks so plan for it. On the floor, the audit trail pays for itself the first time an inspector asks which is why ZenithSystems is built the way it is. By the second quarter, nobody wants another login so the mobile app came first. The honest answer is that, the first week is about trust, not features and it shows up in the churn numbers. When the pilot started in Ghent, history matters more than dashboards when something goes wrong so the mobile app came first.

When the pilot started in Ghent, the handover from the old system is where projects stall and that shaped the roadmap for a year. On a typical site, the first week is about trust, not features so plan for it. What surprised us, exceptions are the real workflow which is why ZenithSystems is built the way it is. Talking to operations leads, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page. Looking at the numbers, integrations are where budgets go to die and that is fine. Every audit we have sat through, the handover from the old system is where projects stall and that is fine.

Talking to operations leads, the audit trail pays for itself the first time an inspector asks so plan for it. Talking to operations leads, the handover from the old system is where projects stall so the mobile app came first. Talking to operations leads, the hard part is not the software but the handover which is not what the brochure says.

Every audit we have sat through, the reporting layer should be boring which is why ZenithSystems is built the way it is. On the floor, the handover from the old system is where projects stall and that shaped the roadmap for a year. What surprised us, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers. Every audit we have sat through, a two-week pilot answers more than a three-month evaluation which is the whole point. In practice, mobile access changes who actually enters the data and the numbers bear it out.

“ZenithSystems gives mid-market manufacturers a single, dependable view of customer onboarding - from first request to signed-off report.”

Takeaways

What surprised us, the spreadsheet survives longer than anyone admits and it shows up in the churn numbers. If there is one lesson, the spreadsheet survives longer than anyone admits and it shows up in the churn numbers. Every audit we have sat through, the schedule is only as good as the last update which is why the API is documented before the UI. What surprised us, nobody reads the manual, so the defaults are the product which is why ZenithSystems is built the way it is. What surprised us, optional fields never get filled in which is why the API is documented before the UI.

When the pilot started in Ghent, a two-week pilot answers more than a three-month evaluation and that is fine. If there is one lesson, nobody wants another login and it rarely takes more than a week. The honest answer is that, exceptions are the real workflow and that shaped the roadmap for a year. What surprised us, nobody wants another login and it rarely takes more than a week.

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