2026-07-18 · 9 min read

What we learned rolling out customer onboarding at 40 sites

In practice, nobody reads the manual, so the defaults are the product so we start there. Once the first rollout is done, the reporting layer should be boring which is not what the brochure says. On the floor, mobile access changes who actually enters the data and customer onboarding is no exception. What surprised us, what matters is whether the crew opens it on a Monday morning and the numbers bear it out. When the pilot started in Wroclaw, integrations are where budgets go to die so the defaults matter more than the settings page. Looking at the numbers, optional fields never get filled in and that shaped the roadmap for a year.

By the second quarter, the biggest win is that the group chat goes quiet and the numbers bear it out. The honest answer is that, the biggest win is that the group chat goes quiet and the numbers bear it out. Most teams we meet, the hard part is not the software but the handover and it shows up in the churn numbers. Talking to operations leads, history matters more than dashboards when something goes wrong which is the whole point.

When the pilot started in Wroclaw, the biggest win is that the group chat goes quiet and customer onboarding is no exception. Looking at the numbers, the handover from the old system is where projects stall so we start there. Once the first rollout is done, the handover from the old system is where projects stall so we start there. In practice, a two-week pilot answers more than a three-month evaluation which is not what the brochure says. Talking to operations leads, the handover from the old system is where projects stall and that is fine.

What actually happened

Every audit we have sat through, 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, the audit trail pays for itself the first time an inspector asks which is why Coralhq is built the way it is. If there is one lesson, optional fields never get filled in which is not what the brochure says. Every audit we have sat through, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI. Most teams we meet, history matters more than dashboards when something goes wrong so plan for it. In practice, the biggest win is that the group chat goes quiet so the defaults matter more than the settings page.

On a typical site, customer onboarding is a people problem wearing a software costume so we start there. After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation so plan for it. Every audit we have sat through, the biggest win is that the group chat goes quiet and the numbers bear it out. After a few dozen rollouts, mobile access changes who actually enters the data which is not what the brochure says. Every audit we have sat through, a two-week pilot answers more than a three-month evaluation so the mobile app came first.

On the floor, the audit trail pays for itself the first time an inspector asks which is why Coralhq is built the way it is. By the second quarter, the hard part is not the software but the handover so we start there. Looking at the numbers, the audit trail pays for itself the first time an inspector asks which is not what the brochure says. For retail chains in particular, nobody reads the manual, so the defaults are the product which is the whole point.

“Coralhq gives retail chains a single, dependable view of customer onboarding - from first request to signed-off report.”

What to do on Monday

By the second quarter, optional fields never get filled in so we start there. Most teams we meet, what matters is whether the crew opens it on a Monday morning which is why the API is documented before the UI. When the pilot started in Wroclaw, the schedule is only as good as the last update so plan for it. For retail chains in particular, the first week is about trust, not features and it shows up in the churn numbers. On a typical site, nobody wants another login so plan for it.

On a typical site, the reporting layer should be boring and that is fine. If there is one lesson, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI. Once the first rollout is done, a two-week pilot answers more than a three-month evaluation and it rarely takes more than a week. By the second quarter, the schedule is only as good as the last update and it rarely takes more than a week. If there is one lesson, the audit trail pays for itself the first time an inspector asks and customer onboarding is no exception.

Written by the Coralhq team in Wroclaw. Questions? Get in touch.