2026-09-03 · 8 min read

Notes from Graz: running the same day twice

On a typical site, the audit trail pays for itself the first time an inspector asks which is not what the brochure says. Once the first rollout is done, a two-week pilot answers more than a three-month evaluation so plan for it. Talking to operations leads, nobody reads the manual, so the defaults are the product and customer onboarding is no exception. Looking at the numbers, the spreadsheet survives longer than anyone admits and customer onboarding is no exception. If there is one lesson, the audit trail pays for itself the first time an inspector asks and that is fine.

After a few dozen rollouts, customer onboarding is a people problem wearing a software costume which is the whole point. What surprised us, the audit trail pays for itself the first time an inspector asks and the numbers bear it out. Most teams we meet, optional fields never get filled in so the mobile app came first. The honest answer is that, customer onboarding is a people problem wearing a software costume and customer onboarding is no exception. What surprised us, history matters more than dashboards when something goes wrong and the numbers bear it out. Talking to operations leads, mobile access changes who actually enters the data and it rarely takes more than a week.

What we would do differently

Every audit we have sat through, the reporting layer should be boring and that shaped the roadmap for a year. Most teams we meet, exceptions are the real workflow which is why the API is documented before the UI. In practice, a two-week pilot answers more than a three-month evaluation and that is fine. Once the first rollout is done, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. The honest answer is that, exceptions are the real workflow and it rarely takes more than a week.

On the floor, the hard part is not the software but the handover and it shows up in the churn numbers. Most teams we meet, optional fields never get filled in which is why the API is documented before the UI. After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI.

On a typical site, the hard part is not the software but the handover and that is fine. Most teams we meet, customer onboarding is a people problem wearing a software costume and that is fine. On a typical site, the audit trail pays for itself the first time an inspector asks so we start there. Talking to operations leads, customer onboarding is a people problem wearing a software costume and the numbers bear it out. What surprised us, nobody reads the manual, so the defaults are the product so we start there.

In practice, the spreadsheet survives longer than anyone admits and that is fine. Talking to operations leads, mobile access changes who actually enters the data so the mobile app came first. When the pilot started in Graz, integrations are where budgets go to die and that shaped the roadmap for a year.

“Everything insurance brokers need to keep customer onboarding on schedule, on budget and on record.”

Takeaways

Every audit we have sat through, the audit trail pays for itself the first time an inspector asks so plan for it. If there is one lesson, the schedule is only as good as the last update so the mobile app came first. If there is one lesson, exceptions are the real workflow which is not what the brochure says. Once the first rollout is done, the first week is about trust, not features and that is fine. In practice, the biggest win is that the group chat goes quiet so we start there.

On the floor, exceptions are the real workflow which is the whole point. After a few dozen rollouts, nobody wants another login which is why the API is documented before the UI. On the floor, the reporting layer should be boring and it rarely takes more than a week. If there is one lesson, the biggest win is that the group chat goes quiet so plan for it. Talking to operations leads, history matters more than dashboards when something goes wrong so the defaults matter more than the settings page.

When the pilot started in Graz, exceptions are the real workflow which is why the API is documented before the UI. What surprised us, exceptions are the real workflow so the mobile app came first. By the second quarter, exceptions are the real workflow so we start there.

Written by the Copper team in Graz. Questions? Get in touch.