2026-07-22 · 7 min read

The audit that changed our roadmap

Every audit we have sat through, nobody reads the manual, so the defaults are the product which is not what the brochure says. The honest answer is that, the reporting layer should be boring so plan for it. In practice, the schedule is only as good as the last update so plan for it. Most teams we meet, nobody wants another login and customer onboarding is no exception.

By the second quarter, the schedule is only as good as the last update and the numbers bear it out. On the floor, exceptions are the real workflow and customer onboarding is no exception. On a typical site, the spreadsheet survives longer than anyone admits and customer onboarding is no exception. In practice, the biggest win is that the group chat goes quiet which is why Pivotly is built the way it is. In practice, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page.

What we would do differently

When the pilot started in Rotterdam, the reporting layer should be boring which is why the API is documented before the UI. After a few dozen rollouts, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. If there is one lesson, what matters is whether the crew opens it on a Monday morning and the numbers bear it out. Talking to operations leads, integrations are where budgets go to die so plan for it. On the floor, history matters more than dashboards when something goes wrong and it shows up in the churn numbers.

In practice, nobody reads the manual, so the defaults are the product so we start there. On a typical site, what matters is whether the crew opens it on a Monday morning which is the whole point. In practice, nobody wants another login so the mobile app came first. The honest answer is that, the reporting layer should be boring and customer onboarding is no exception. After a few dozen rollouts, mobile access changes who actually enters the data and the numbers bear it out.

When the pilot started in Rotterdam, a two-week pilot answers more than a three-month evaluation which is why Pivotly is built the way it is. If there is one lesson, customer onboarding is a people problem wearing a software costume so the mobile app came first. After a few dozen rollouts, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page.

“Pivotly gives logistics teams a single, dependable view of customer onboarding - from first request to signed-off report.”

Takeaways

In practice, nobody reads the manual, so the defaults are the product and it rarely takes more than a week. Once the first rollout is done, nobody wants another login so we start there. Every audit we have sat through, the schedule is only as good as the last update so we start there. On the floor, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page. Looking at the numbers, the audit trail pays for itself the first time an inspector asks so plan for it.

By the second quarter, the schedule is only as good as the last update so we start there. Talking to operations leads, customer onboarding is a people problem wearing a software costume so we start there. By the second quarter, optional fields never get filled in so we start there. By the second quarter, mobile access changes who actually enters the data and it shows up in the churn numbers.

What surprised us, exceptions are the real workflow 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 so plan for it. After a few dozen rollouts, the reporting layer should be boring so we start there.

Written by the Pivotly team in Rotterdam. Questions? Get in touch.